Content
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-intentioned with useful before/after examples and a comprehensive checklist, but it is severely over-verbose—explaining concepts Claude inherently understands (what tailoring means, the difference between lying and highlighting). The content would benefit enormously from being cut by 60-70% and split into a concise overview with references to supporting files for scenarios and templates.
Suggestions
Cut the 'Tailoring Philosophy,' 'Truth vs. Tailoring Line,' and 'Common Tailoring Scenarios' sections entirely or move them to a separate SCENARIOS.md file—Claude already understands these concepts and they consume significant tokens.
Add a validation/feedback step after tailoring: e.g., 'Re-compare tailored resume against JD requirements and verify keyword coverage before presenting final output.'
Split the monolithic content into at least 2-3 files: keep SKILL.md as a concise overview (~50 lines) with the core process and output format, then reference separate files for examples (EXAMPLES.md), scenarios (SCENARIOS.md), and templates (TEMPLATES.md).
Remove explanatory framing like 'Think of your full experience as a library' and 'This is your elevator pitch' — these add no value for Claude and waste tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts like 'Think of your full experience as a library of achievements' and 'This is your elevator pitch.' Much of the content (tailoring philosophy, common scenarios, truth vs tailoring line) describes concepts Claude already understands. The skill could be reduced to ~30% of its current size without losing actionable value. | 1 / 3 |
Actionability | Provides concrete before/after examples for summaries, skills reordering, and bullet adjustments, plus a useful output format template. However, this is an instruction-only skill with no executable code or tool usage—it's mostly strategic advice and examples rather than precise, step-by-step executable guidance. The tailoring plan template and output format are helpful but the scenarios section is more advisory than actionable. | 2 / 3 |
Workflow Clarity | The 3-step tailoring process (Analyze → Audit → Adjust) provides a clear sequence, and the checklist at the end is useful. However, there are no validation checkpoints or feedback loops—no step to verify keyword match percentage, no instruction to re-check against the JD after modifications, and the dependency on 'job-description-analyzer' is mentioned but not clearly integrated into the workflow. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files despite the content clearly warranting separation (e.g., common scenarios, keyword rules, version management could each be separate files). References the 'Job Description Analyzer' skill but doesn't link to it. Everything is inlined in one massive document with no bundle files to support it. | 1 / 3 |
Total | 6 / 12 Passed |