Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-sequenced, highly actionable coaching workflow with clear checkpoints and concrete schemas. Its main weaknesses are verbosity (overlapping report templates across steps) and a monolithic single-file structure that should be split into reference files.
Suggestions
Deduplicate the coaching report template between Step 5 (personalized_playbook) and Step 6 (report structure) — keep one canonical template and reference it from the other.
Extract the large output-contract schemas and per-role skill-dimension tables into reference files under references/ (e.g. SCHEMAS.md, SKILL_DIMENSIONS.md) and link to them from SKILL.md to improve progressive disclosure.
Tighten the placeholder tables (winner_vs_loser, sentiment_trend, winning_vs_losing) which repeat similar column structures across steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is verbose and redundant — the coaching report template is rendered in both Step 5 (personalized_playbook) and Step 6 (report structure) with heavy overlap, and many placeholder tables repeat structure — yet it does not condescend by explaining concepts Claude already knows. Not score 3 because it could be tightened substantially; not score 1 because the content is structured domain-specific guidance rather than padded with basic explanations. | 2 / 3 |
Actionability | For an instruction-only skill the guidance is highly concrete and copy-paste-ready: exact metric formulas ("Word count (you) / word count (prospect)"), numeric thresholds ("10-15 questions", "40-50% talk"), full input/output contracts, letter-grade rubrics, and a complete report template. Matches the anchor for specific, executable guidance. | 3 / 3 |
Workflow Clarity | Steps 0-6 are clearly sequenced, each with a Purpose, Input Contract, Output Contract, and explicit Human Checkpoints acting as validation gates (e.g. "Proceed with analysis? (Y/n)"), plus a data-availability adaptation table. This is an analysis/coaching workflow, not a destructive or batch operation, so the validation cap does not apply. | 3 / 3 |
Progressive Disclosure | The skill is a single ~900-line monolithic file with no bundle files; it is well-sectioned but content that would benefit from being split (the large output-contract schemas, the report template, the per-role skill-dimension tables) is all inline. Not score 3 because it far exceeds the under-50-lines simple-skill allowance; not score 1 because organization is clear, not a wall of text. | 2 / 3 |
Total | 10 / 12 Passed |