fix(uipath-ixp): hard DO-NOT-TRIGGER for flow work in frontmatter description

[andrei-uipath]

Skill selection happens on the frontmatter description alone — the body-level "When NOT to Use This Skill" deferral shipped in #1348 (RE-12440) is only read after uipath-ixp activates, so it never prevents the misfire ACTV-89470 describes: agents picking uipath-ixp during flow discovery. In the description, the deferral was one soft trailing sentence ("For IxP nodes or model listings inside a .flow / Maestro flow→uipath-maestro-flow") that loses to the strong positive triggers ("pull metrics and model versions, publish/tag/roll back model versions").

This replaces it with a hard negative trigger in the same idiom uipath-maestro-flow already uses: "DO NOT TRIGGER during .flow / Maestro Flow work — discovering or listing IxP / document-extraction models, extractors, or nodes available to Maestro Flow, and adding or wiring an IxP node, belong to uipath-maestro-flow even when they sound like IXP model management." (Per review, the earlier "Standalone IXP projects ONLY" qualifier was dropped as ambiguous — the capability list already carries the positive scope and the negative trigger states the exclusion precisely.) Description is 727 chars (cap 1024); body text unchanged.

🤖 Generated with Claude Code

https://claude.ai/code/session_0164ykfgunBCrvhrUMHbaGEQ

[github-actions]

Claude finished @andrei-uipath's task in 2m 19s —— View job

---

PR Review: fix(uipath-ixp): hard DO-NOT-TRIGGER for flow work in frontmatter description

• Read review criteria and project conventions
• Analyze the diff
• Read full SKILL.md for context
• Validate frontmatter (description length, format, redirects)
• Check for cross-skill dependencies and broken links
• Post review

---

Summary

Single-line frontmatter change in skills/uipath-ixp/SKILL.md that replaces a soft trailing redirect (For IxP nodes or model listings inside a .flow / Maestro flow→uipath-maestro-flow.) with a hard negative trigger (Standalone IXP projects ONLY. DO NOT TRIGGER during .flow / Maestro flow work — …). The goal is to prevent agents from picking uipath-ixp during flow-related work that belongs to uipath-maestro-flow (ACTV-89470).

Change-by-Change Review

1. skills/uipath-ixp/SKILL.md (line 3) — description frontmatter

OK

The change is correct and well-motivated:

• Character count: 751 chars (verified) — well under the 1024-char repo cap.
• Identity front-loaded: Still starts with UiPath IXP (Document Understanding) via \uip ixp`` — good signal in the first ~100 chars.
• Hard negative trigger: Uses the DO NOT TRIGGER idiom that uipath-maestro-flow already uses in its own description, creating symmetric bidirectional exclusion. This is stronger than the prior soft → redirect.
• Specificity of the exclusion: Enumerates the exact overlap scenarios (discovering/listing IxP models, extractors, nodes; adding/wiring an IxP node) — this specificity helps the model distinguish between standalone IXP project work (this skill) and flow-embedded IXP node work (maestro-flow).
• → redirect preserved: The exclusion text names uipath-maestro-flow as the target, serving the same routing function as the old compact redirect.
• YAML validity: Frontmatter is well-formed. String is properly double-quoted with no unescaped special characters.
• Body unchanged: The body-level "When NOT to Use This Skill" section (lines 19–27) still provides the detailed deferral explanation for post-activation context. No conflict with the new description.

What's Missing

Nothing identified. The PR is tightly scoped to the frontmatter fix. The body-level deferral section is already comprehensive and doesn't need changes.

Area Ratings

Area	Status	Notes
Frontmatter	OK	Valid YAML, 751 chars, identity front-loaded, hard negative trigger matches repo idiom
E2E Tests	OK	No new capabilities added — existing tests unaffected
Skill Body	OK	Unchanged, body-level deferral already in place
References & Assets	OK	No reference changes needed
Repo Hygiene	OK	Scoped change, no secrets, no cross-skill deps

Issues for Manual Review

• Activation-gate eval: The hard DO NOT TRIGGER is the right fix at the description level, but the actual misfire rate (ACTV-89470) should be validated with an activation eval to confirm the new wording reliably prevents the false trigger. The activation-gate.yml CI workflow should cover this if configured for this skill.

Conclusion

Clean, well-scoped fix. The change correctly escalates a soft trailing redirect to a hard negative trigger in the frontmatter description — the only place where skill selection happens. The idiom is consistent with how uipath-maestro-flow already handles the symmetric exclusion. No issues found. Approve.

---

[richsilv]

I think @rockymadden will want to see this given that it's a change to front-matter.

[richsilv]

Looks good to me. Not sure if you need a coding agents team reviewer to change the front matter.