Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a meta-skill for skill discovery and invocation. Its core message ('always check for applicable skills before responding') is valid but delivered with extreme verbosity and repetition. The 'Red Flags' table, EXTREMELY-IMPORTANT block, and repeated '1% chance' language all say the same thing in different ways, consuming significant token budget. The workflow is reasonably clear via the dot graph but lacks error handling paths.
Suggestions
Drastically reduce repetition: consolidate the EXTREMELY-IMPORTANT block, the '1% chance' mentions, and the 12-row Red Flags table into a single concise rule with 2-3 key examples of rationalization to avoid.
Add error handling to the workflow: what should Claude do if the Skill tool returns no matching skill, or if an invoked skill doesn't apply after reading it?
Replace the dot graph with a simple numbered list of 4-5 steps — the graph consumes many tokens for a flow that's essentially linear with one branch.
Remove or significantly shorten the Platform Adaptation section — Claude can follow a simple 'check your platform docs for tool equivalents' instruction without listing each platform.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The 'Red Flags' table alone contains 12 rows hammering the same point ('check for skills first'). The EXTREMELY-IMPORTANT block, the repeated '1% chance' language, and extensive rationalization table all explain something Claude should grasp from a single clear instruction. The dot graph adds tokens for a relatively simple flow. | 1 / 3 |
Actionability | Provides some concrete guidance (invoke Skill tool before responding, use TodoWrite for checklists, announce skill usage) but much of the content is motivational/behavioral rather than executable. The platform adaptation section references files but doesn't give concrete tool invocation syntax. The dot graph is descriptive but not directly executable. | 2 / 3 |
Workflow Clarity | The dot graph provides a clear sequence for the skill-checking workflow, and the priority ordering (process skills first, then implementation) is helpful. However, there are no validation checkpoints or error recovery steps — what happens if a skill invocation fails? What if the Skill tool returns nothing? These gaps prevent a score of 3. | 2 / 3 |
Progressive Disclosure | References external files (references/copilot-tools.md, references/codex-tools.md) for platform-specific details, which is good progressive disclosure. However, the main content itself is monolithic — the Red Flags table, Skill Types, and Skill Priority sections could be more concisely organized. No bundle files are provided to verify referenced paths exist. | 2 / 3 |
Total | 7 / 12 Passed |