Content
60%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a meta-skill that instructs Claude to always check for and invoke relevant skills before responding. Its workflow and structure are solid, with a clear decision graph and priority ordering. However, it suffers significantly from verbosity—the core message ('always invoke skills first') is repeated excessively through the opening block, the 12-row Red Flags table, and redundant phrasing throughout, all of which could be condensed to roughly half the current length without losing any information.
Suggestions
Condense the Red Flags table to 3-4 representative examples with a summary principle, rather than 12 variations of the same message.
Remove the <EXTREMELY-IMPORTANT> block or merge its content into 'The Rule' section—it repeats the same instruction three times before the skill even begins.
Add a concrete example of an actual Skill tool invocation (e.g., showing the tool call syntax and a sample announcement message).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is noticeably verbose with extensive repetition of the same core message ('invoke skills before doing anything'). The 'Red Flags' table contains 12 rows that all say essentially the same thing in different ways. The opening HTML-tagged block repeats the urgency three times. Claude already understands instruction priority—this level of hammering wastes tokens. | 2 / 5 |
Actionability | The skill provides concrete, actionable guidance: use the Skill tool, announce usage, create TodoWrite items for checklists, follow a specific priority order. The dot graph gives a clear decision flow. Minor gap: no concrete example of an actual Skill tool invocation call or what the announcement looks like in practice. | 4 / 5 |
Workflow Clarity | The dot graph provides a clear decision sequence from message receipt through skill invocation to response. The priority ordering (process skills first, then implementation) is well-defined. Minor gap: no explicit validation or error-recovery step for when a skill invocation fails or returns unexpected content. | 4 / 5 |
Progressive Disclosure | The content is well-structured with clear sections (How to Access, The Rule, Red Flags, Skill Priority, Skill Types, User Instructions). For a standalone meta-skill with no bundle files, the organization is appropriate. Minor issue: the 'When to Use' section at the bottom is vague and feels tacked on, and there are no references to supplementary materials that could offload the verbose Red Flags table. | 4 / 5 |
Total | 14 / 20 Passed |