Make Directory and Project skills compete less - #505
Open
tgalaxystripe wants to merge 1 commit into
Open
Conversation
This Directory description is so broad that it competes with Projects and can trigger from action verbs even when discovery is already complete. The routing contract should be: Directory resolves “who or what should satisfy this need?” Projects executes “create, connect, or manage the selected service.” Broad “build an app” intent alone triggers neither skill.
|
|
1 similar comment
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current stripe-projects description has three problems:
It competes with Directory by claiming vague task and component requests such as “I need a database” and “I need hosting.”
It conflates exploration, vendor selection, provisioning, and ongoing project management.
Its long trigger list obscures the most important distinction: explicit execution or existing-project intent.
This conflicts with the stripe-directory skill, which owns external-service discovery and explicitly prohibits provisioning without a user request. Since agents scan the description to select a skill, the discriminating routing rule should come first, as recommended by the skill-authoring guidance.
(Written with Orbit)