fix(skills): force MCP tool usage in all 15 skills#227
Merged
Conversation
Skills described MCP calls in prose/example format but lacked
enforcement directives — agents could bypass MCP entirely and
answer from training data or file browsing. Added to every skill:
- "MCP required" section with YOU MUST directive
- Reasoning preamble (Q-class / Pick / Why) before each call
- Reference to docs/AGENT-GUIDE.md for full operating manual
- "Do not" guardrails against skipping MCP or fabricating ids
- Imperative language in Steps ("Call resolve..." not "resolve(...)")
- Skill structure section in README.md
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Explicitly delineate .agents/skills/ (developers working on this repo) from skills/ (consumers using the MCP on their own codebase) to prevent confusion between the two audiences. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
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.
Summary
Q-class / Pick / Why) before each MCP call (matching AGENT-GUIDE.md convention)docs/AGENT-GUIDE.mdfor the full operating manualresolve(...)")skills/README.mdwith skill structure documentationRoot cause
Skills were written as documentation (worked examples, argument contracts) without any enforcement language. An agent reading a skill understood what to do conceptually but wasn't forced to actually make MCP tool calls. The fix adds three enforcement layers:
Test plan
ruff check .passes (docs-only change)🤖 Generated with Claude Code