luigidemasi opened a new issue, #40: URL: https://github.com/apache/camel-kit/issues/40
> Imported from [luigidemasi/camel-kit#72](https://github.com/luigidemasi/camel-kit/issues/72), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-13. > Closed by commit [3cd083a](https://github.com/luigidemasi/camel-kit/commit/3cd083a1b258655a029be8721737c091622b6101). --- ## Context **Source pattern:** Every skill in [agent-skills](https://github.com/addyosmani/agent-skills) has explicit negative triggers — specific scenarios where the skill should NOT be invoked. ## Problem Camel-kit skills have positive trigger phrases in frontmatter descriptions but no exclusion lists. The `camel-start` meta-router has a "When NOT to Use Each Skill" table in its decision tree, but individual skills lack their own negative trigger sections. When the meta-router is bypassed (power users typing `/camel-brainstorm` directly), the skill itself has no guard against misuse. The agent must infer non-applicability from positive triggers alone. ## Proposed Solution Add a `## When NOT to use this skill` section to each Tier 1 and Tier 2 skill's SKILL.md: | Skill | Do NOT use for | |-------|---------------| | `camel-brainstorm` | Quick property changes, adding a single component, version bumps, questions about Camel | | `camel-migrate` | Greenfield projects, Camel 4.x-to-4.x version bumps | | `camel-plan` | Ad-hoc changes, single-file edits, quick fixes | | `camel-execute` | Without an approved design spec (Iron Law 3) | | `camel-validate` | Fixing issues (use debug), generating routes, design work | | `camel-ship` | Single-file changes, quick fixes, exploratory work | | `camel-knowledge` | Implementation tasks, code generation | ## Acceptance Criteria - [ ] All Tier 1 skills have a `## When NOT to use this skill` section - [ ] All Tier 2 skills have a `## When NOT to use this skill` section - [ ] Negative triggers are specific and actionable (not generic "when it doesn't fit") - [ ] `camel-start` decision tree's negative trigger table stays in sync -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
