Content
38%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 marketing-flavored monologue: padded role/overview/roadmap sections, non-executable pseudocode posing as examples, workflows without executable validation loops, and a broken reference to a nonexistent playbook file. It needs trimming to actionable core content split across real reference files.
Suggestions
Delete the 'Role Statement', 'Context Overview', 'Future Roadmap', and 'Use/Do not use this skill when' sections — they restate the description or add no actionable guidance.
Make code executable or explicitly justify the pseudocode: define or link the missing helpers (VectorDatabase, prioritize_components, estimate_tokens), and replace the invented 'context-restore' CLI examples with the real invocation path.
Create the referenced resources/implementation-playbook.md (or fix the path) and move the detailed strategy sections and input-parameter reference into it, keeping SKILL.md as a concise overview; add concrete validation commands and failure-recovery steps to Workflow 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Multiple padded sections add no actionable value: 'Role Statement' ('Expert Context Restoration Specialist focused on...'), 'Context Overview' ('sophisticated memory management system designed to...'), 'Future Roadmap' ('Quantum-inspired vector search algorithms'), and boilerplate 'Use this skill when / Do not use this skill when' sections that restate the frontmatter. Several unnecessary sections matches anchor 2; not anchor 1 because genuine content (parameters, strategies, code) is present. | 2 / 5 |
Actionability | Code blocks are non-executable stubs — VectorDatabase, rank_and_filter_contexts, prioritize_components, estimate_tokens, and load_component are all undefined — and the bash examples invoke a 'context-restore' CLI that does not exist in the bundle. Concrete structure exists but key details are missing, matching anchor 3 ('pseudocode instead of executable code'); not anchor 4 because nothing is copy-paste runnable. | 3 / 5 |
Workflow Clarity | Workflow 1 lists a sequence and a nominal validation step ('Validate context against current codebase'), but validation is a bare phrase with no command, no error-recovery loop, and no checkpoint in Workflow 2. Sequence present with implicit checkpoints matches anchor 3; not anchor 4 because the validation steps lack any executable how or retry path. | 3 / 5 |
Progressive Disclosure | The body inlines 175 lines of strategy material (input parameters, eight retrieval strategies, integration patterns) that belongs in reference files, and its single pointer — 'open resources/implementation-playbook.md' — targets a file that does not exist in the bundle (no resources/, references/, scripts/, or assets/ directories). Content that clearly belongs in separate files is inlined plus a broken reference matches anchor 2. | 2 / 5 |
Total | 10 / 20 Passed |