Content
11%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.
The body is a hollow shell: generic abstract instructions, promotional overview prose, and a reference architecture pointing at 12 files that are absent from the bundle. No concrete, executable guidance is delivered anywhere in the skill as shipped. It reads as an auto-generated stub rather than a usable skill.
Suggestions
Ship the referenced bundle files (sub-skills/*.md, resources/implementation-playbook.md) or replace the dangling links with inline content — currently every file reference in the body points to a nonexistent path.
Replace the abstract Instructions with a concrete, sequenced workflow (e.g., for project resumption: retrieve context via semantic search -> filter and rank by relevance -> rehydrate session state -> validate integrity -> merge and resolve conflicts), with an explicit validation checkpoint before acting on restored context.
Delete the empty '## Core Requirements and Arguments' header and cut the Role Statement and Context Overview filler; redirect those tokens toward executable guidance such as representative commands or a worked resumption example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Several padded sections: the 'Role Statement' is persona fluff, 'Context Overview' is marketing prose ('sophisticated memory management system', 'seamless continuity'), the phrase 'context restoration: advanced semantic memory rehydration' is repeated verbatim three times, and '## Core Requirements and Arguments' is an empty header with no content. Roughly half the body is non-actionable filler, matching 'noticeably verbose; several unnecessary explanations or padded sections'. | 2 / 5 |
Actionability | The Instructions are pure abstraction — 'Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes' — with no code, commands, or specific steps anywhere. The only concrete pointer, 'resources/implementation-playbook.md', does not exist in the bundle, so no executable guidance is actually delivered. | 1 / 5 |
Workflow Clarity | No step sequence exists: the Instructions are unordered generalities, and the two named workflows ('Workflow 1: Project Resumption', 'Workflow 2: Cross-Project Knowledge Transfer') appear only as dangling link titles with no steps or validation checkpoints. This matches 'steps missing or incoherent; no sequence'. | 1 / 5 |
Progressive Disclosure | The body has well-signaled one-level-deep references (a 12-entry module index), but scored against the actual bundle structure: no referenced file exists — all 11 './sub-skills/*.md' links and 'resources/implementation-playbook.md' are dangling — so navigation leads nowhere and no progressive content is delivered. The section/index structure is real (better than a monolithic wall or nested references), but the disclosure path is entirely unbacked. | 2 / 5 |
Total | 6 / 20 Passed |