Content
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents with no substantive content. It defers all concrete guidance to referenced files that aren't provided in the bundle, leaving the SKILL.md itself with only vague, abstract bullet points. For a complex domain like billing automation involving financial operations, the lack of any concrete examples, executable code, validation steps, or specific patterns is a significant weakness.
Suggestions
Add at least one concrete, executable code example in the SKILL.md itself — e.g., a subscription state machine model, an invoice generation snippet, or a dunning retry schedule configuration.
Include explicit workflow steps with validation checkpoints for critical paths like 'charging a customer' or 'handling a plan change with proration' — these involve financial operations and need feedback loops.
Replace the vague instruction bullets with specific, actionable guidance — e.g., instead of 'Define plans, pricing, billing intervals', provide a concrete plan schema or data model that Claude can use directly.
Provide the referenced bundle files (implementation-playbook.md) or inline the most critical patterns so the skill is useful even without the sub-resources.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' lists that are somewhat obvious and don't add much value for Claude. The 'Instructions' section is high-level but not padded with explanations of known concepts. | 2 / 3 |
Actionability | The instructions are entirely abstract and vague — 'Define plans, pricing, billing intervals' and 'Implement invoicing, payments, retries' provide no concrete code, commands, schemas, or executable examples. Everything describes rather than instructs, with all concrete guidance deferred to a referenced playbook that isn't provided. | 1 / 3 |
Workflow Clarity | The instructions list high-level steps but lack any clear sequencing, validation checkpoints, or feedback loops. For a complex domain involving payments, tax compliance, and dunning — all of which involve destructive/financial operations — there are no verification steps, error recovery patterns, or explicit ordering beyond a loose bullet list. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` and a sub-skill, which is appropriate progressive disclosure structure. However, no bundle files are provided to verify these references exist, and the SKILL.md itself contains almost no substantive content — it's essentially an empty shell pointing elsewhere, making the overview too thin to be useful on its own. | 2 / 3 |
Total | 6 / 12 Passed |