Content
35%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.
The body has a sensible section layout and enumerates relevant regulations and output expectations, but it is undermined by circular boilerplate sections, generic instruction bullets, no concrete drafting guidance, and a dangling reference to a nonexistent playbook file. It reads as an auto-generated template rather than an operational legal-drafting skill.
Suggestions
Delete the circular 'Use this skill when / Do not use this skill when' sections and replace the generic Instructions bullets with concrete guidance: a document skeleton (e.g., mandatory GDPR policy sections under Art. 13) and a per-regulation compliance checklist.
Fix or remove the dangling `resources/implementation-playbook.md` reference — either ship the playbook in the bundle or inline the key drafting patterns it should contain.
Add an explicit validation checkpoint in the Approach workflow, e.g. 'Before delivering, verify every mandatory clause for the identified jurisdictions is present and the disclaimer is included.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Multiple padded sections add no information: 'Use this skill when - Working on legal advisor tasks or workflows', 'Do not use this skill when - The task is unrelated to legal advisor', and generic instruction bullets like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices and validate outcomes'. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'. Not 3 because these are wholly contentless boilerplate (circular restatements of the skill name), not merely tightenable phrasing; not 1 because the Focus Areas, Key Regulations, and Output sections are reasonably lean lists. | 2 / 5 |
Actionability | Beyond naming regulations and the verbatim disclaimer, the body gives only high-level direction — 'Identify applicable jurisdictions and regulations', 'Include all mandatory disclosures and clauses', 'Structure documents with logical sections and headers' — with no example clauses, document skeletons, per-regulation checklists, or templates. This matches 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'. Not 3 because the promised 'Compliance checklist for each regulation' is never provided and the one pointer to executable detail, `resources/implementation-playbook.md`, references a file that does not exist in the bundle. | 2 / 5 |
Workflow Clarity | The Approach section lists a real sequence ('Identify applicable jurisdictions... Structure documents... Flag areas requiring specific legal review') but checkpoints are implicit at best — no step verifies completeness of mandatory clauses or validates compliance before delivery, matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'. Not 4 because 'flag areas requiring legal review' is a vague gesture rather than a defined checkpoint; not 2 because the six steps are coherent and correctly ordered. | 3 / 5 |
Progressive Disclosure | The body is sectioned (Focus Areas, Approach, Key Regulations, Output) and keeps a reasonable length, but its only external reference — 'If detailed examples are required, open `resources/implementation-playbook.md`' — points to a nonexistent file (no resources/ or other bundle directory exists). This matches 'Some structure but could be better organized; references present but not clearly signaled' in effect: navigation leads to a dead end. Not 4 because a broken reference fails the 'references mostly clear' criterion; not 2 because the inline content itself is appropriately short and well-sectioned rather than a monolithic wall. | 3 / 5 |
Total | 10 / 20 Passed |