Content
25%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is largely a high-level description of what a legal document drafting assistant should do, rather than actionable instructions for how to do it. It lacks concrete templates, example clauses, specific language patterns, or executable guidance. The content reads more like a job description than a skill file, with significant verbosity in listing regulations and focus areas that Claude already knows about.
Suggestions
Add concrete template snippets for at least the most common documents (e.g., a GDPR privacy policy skeleton with placeholder sections and example clauses)
Replace the generic 'Approach' section with a specific workflow that includes validation steps, such as a compliance checklist to verify against after drafting each document type
Remove the tautological 'Use/Do not use' boilerplate and the role description ('You are a legal advisor...') — these waste tokens without adding value
Either provide the referenced `resources/implementation-playbook.md` bundle file with detailed examples and templates, or inline the most critical actionable content directly in the skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant padding: generic boilerplate sections ('Use this skill when' / 'Do not use this skill when' are tautological), explains Claude's role unnecessarily ('You are a legal advisor...'), and lists regulations/focus areas without adding actionable value beyond what Claude already knows. | 2 / 5 |
Actionability | The content is almost entirely abstract and descriptive. There are no concrete templates, no example clauses, no executable code snippets, and no specific language to use. The 'Approach' section lists high-level steps like 'Identify applicable jurisdictions' without showing how. The instructions are vague directives like 'Apply relevant best practices.' | 2 / 5 |
Workflow Clarity | The 'Approach' section provides a rough 6-step sequence but steps are poorly defined and lack any validation checkpoints. There's no feedback loop for verifying compliance, no checklist to validate completeness of generated documents, and no error recovery guidance. For a skill involving legal document generation (where errors have real consequences), this is insufficient. | 2 / 5 |
Progressive Disclosure | References `resources/implementation-playbook.md` but no bundle files are provided, making this a dead reference. The skill inlines lists of regulations and focus areas that could be in a reference file, while the actual actionable content (templates, examples, clauses) that should be referenced is entirely absent. | 2 / 5 |
Total | 8 / 20 Passed |