fix(core): include skill base directory in /skill-name command template#29602
fix(core): include skill base directory in /skill-name command template#29602imtiazNDMA wants to merge 1 commit into
Conversation
When invoking a skill via /skill-name, the command system only injected the raw SKILL.md content as the prompt template. This meant the agent had no knowledge of the skill's base directory or its reference files. Now the template includes the skill's base directory in the same format as the SkillTool output, so the agent can use Glob/Grep/Read to find and inspect reference files. Fixes anomalyco#24831
github-actions
Bot
added
the
needs:compliance
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Potential Duplicates Found:
Both of these PRs appear to be addressing the same underlying issue (issue #24831) regarding insufficient context when invoking skills via /skill-name commands. Check if these are already merged or if they represent alternative approaches to the same problem. |
1 participant
Fixes #24831
When invoking a skill via /skill-name, the command system only injected the raw SKILL.md content as the prompt template. This meant the agent had no knowledge of the skill's base directory or its reference files.
Now the template includes the skill's base directory in the same format as the SkillTool output, so the agent can use Glob/Grep/Read to find and inspect reference files.