Content
81%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 well-engineered SOP body: phased workflow with explicit outputs, worked examples, benchmarks, and a validation checklist make it highly actionable and clear. Its weaknesses are token efficiency (defining known concepts like ATS and STAR) and a fully inlined ~280-line structure that offers no reference-file offloading for the detailed standards tables.
Suggestions
Trim or cut the 'ATS Basics' paragraph and the STAR definition table — Claude already knows what an ATS and the STAR method are; keep only the skill-specific checkpoints and the named ATS vendors if useful.
Move the detailed ATS format/content-standard tables and the quantification guiding-question tables into a references/ file (e.g., references/ats-standards.md), keeping SKILL.md as the phased overview with clear pointers.
Delete promotional filler such as 'producing a highly targeted, high-pass-rate optimized resume' and compress the Quick Start dialog to a single example exchange.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight operational guidance, but it spends tokens explaining concepts Claude already knows — an "ATS Basics" paragraph defining what an applicant tracking system is, a full table defining the STAR method, and marketing-fluff like "producing a highly targeted, high-pass-rate optimized resume". This is more than minor over-explanation, so it sits at 'mostly efficient but includes some unnecessary explanation' rather than the 'minor instances' anchor. | 3 / 5 |
Actionability | Guidance is fully executable for an instruction-only skill: a concrete keyword match matrix format with worked example rows, an explicit coverage formula with pass benchmarks ("Required keyword coverage ≥ 80% is passing"), a before/after STAR rewrite example, guiding-question tables for quantification, an ATS deduction scorecard template, and per-phase output specs. Specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | The five phases are clearly sequenced, each with an explicit Goal, numbered steps, and a defined Output; a pre-delivery Quality Checklist provides validation checkpoints, and the Iterative Refinement section gives a feedback loop (re-execute from the affected phase, cascade downstream, maintain consistency). This matches the anchor for explicit validation steps, feedback loops, and checklists. The operation is advisory (no destructive/batch risk), so no cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the single SKILL.md is well-sectioned with a Quick Start, phased SOP, control rules, and principles — good structure and easy in-file navigation. However, at ~280 lines, detail like the ATS format-standards tables and quantification guidance could arguably live in reference files, and there are no pointers to any, which keeps it below the 'appropriately split, easy navigation' top anchor while above the 'could be better organized / content that should be separate is inline' anchor. | 4 / 5 |
Total | 17 / 20 Passed |