Content
67%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 thorough, well-structured instruction skill with a clear workflow, concrete frameworks, and good reference navigation. Its chief weakness is conciseness: time-sensitive platform statistics and a redundant capabilities block are inlined in SKILL.md rather than pushed into the reference files it already points to.
Suggestions
Move the inline LinkedIn engagement statistics and source citations out of the Core Contract bullet into reference/metrics-guide.md or reference/amplification-playbook.md, leaving only the operative rule (e.g. 'keep 80%+ within Topic DNA pillars; saves/comments outweigh likes') in SKILL.md.
Remove or shrink the top HTML CAPABILITIES/COLLABORATION comment block, which duplicates the Trigger Guidance, Recipes, and Collaboration sections already in the body.
Make the workflow's verification loop explicit (e.g. AP audit fails -> revise -> re-audit before delivery) so the validation checkpoint reads as a feedback loop rather than a single deliverable checklist item.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly well-organized with terse tables and principles, but the Core Contract bullet is a large inline dump of time-sensitive LinkedIn statistics (e.g. '~6.6% baseline', '5.72% B2B median', '14% YoY') with cited sources that the Reference Map indicates belongs in metrics-guide.md/amplification-playbook.md, and the top HTML CAPABILITIES comment duplicates body content. | 3 / 5 |
Actionability | Provides concrete, specific guidance for an instruction-only skill: named frameworks (Tech x Domain x Perspective), exact rules (pin 4-6 repos, <=275-char About, 80% pillar rule), a recipes/subcommand table, and an anti-pattern table with detection and fix columns; minor gaps keep it below fully copy-paste-ready. | 4 / 5 |
Workflow Clarity | The DISCOVER -> POSITION -> CRAFT -> AMPLIFY -> MEASURE workflow is clearly sequenced with per-phase actions and key rules, plus subcommand dispatch, output routing, and verification baked into deliverables (AP audit, consistency check); recovery/error loops are not fully explicit, so not a 5. | 4 / 5 |
Progressive Disclosure | A Reference Map table and a 'Read First' column give well-signaled one-level-deep navigation to reference/*.md and _common/*.md files; however no bundle files are present in the review and some inlined statistics should live in those references, leaving minor organization gaps. | 4 / 5 |
Total | 15 / 20 Passed |