Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-structured codegen reference with extensive executable examples and clear decision guidance. Its main weaknesses are redundancy of rules across sections and a few verbose/marketing-flavored passages that could be tightened.
Suggestions
De-duplicate rules that recur across 'Use These Defaults', 'Critical Rules', and per-feature 'Rules' blocks (e.g. child agents in functions[...], discover() batching) by stating them once and cross-referencing.
Trim time-sensitive/marketing prose such as the relevanceRanking A/B-gate sentence to a factual one-line description and defer detail to ax-agent-memory-skills.
Consider moving the Core API Reference, Public Surface, and generated-language observer tables into a bundled REFERENCE file to slim the SKILL.md overview, since no bundle currently exists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious API specifics Claude does not already know and avoids tutorial prose, but several rules are repeated across sections (child-agents-in-functions, discover() guidance) and the relevanceRanking paragraph carries marketing-flavored, time-sensitive prose ('after its A/B gate passed on both small and frontier models') that could be trimmed, keeping it below the lean 5. | 4 / 5 |
Actionability | Provides numerous copy-paste-ready, fully executable TypeScript examples (Canonical Pattern, Child Agents, Tool Functions, Clarification/Resume, Bubble Errors, Discovery) that cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | A clear Decision Guide maps user intent to agent shape, reinforced by Critical Rules and a Do Not Generate checklist; as a codegen skill it has no destructive/batch operation requiring validate-fix-retry loops, so it does not reach the explicit-checkpoint 5 but is well above the implicit-gap 3. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly headed sections with one-level-deep, clearly signaled references (external example URLs and sibling-skill routing); no bundle files are provided, and some inline API reference (Core API Reference, Public Surface, language tables) could be split into a separate reference file, which is a minor organization gap rather than a structural problem. | 4 / 5 |
Total | 17 / 20 Passed |