Content
22%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a table of contents or project brief than actionable guidance. It lacks any concrete code, data models, specific commands, or executable examples for billing automation. The instructions are entirely abstract ('Define plans...', 'Implement invoicing...') and delegate all substance to a referenced file that doesn't exist in the bundle, leaving Claude with no real guidance to act on.
Suggestions
Add concrete, executable code examples for at least one core workflow (e.g., a subscription billing cycle with invoice generation, including data models and API patterns).
Include an explicit multi-step workflow with validation checkpoints, especially for payment processing and dunning retry logic (e.g., 'Step 1: Create invoice → Step 2: Attempt charge → Step 3: If failed, schedule retry with exponential backoff → Step 4: After N failures, flag for dunning').
Provide a concrete proration calculation example with input/output to make the guidance actionable rather than descriptive.
Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the most critical patterns and checklists directly in the SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes sections like 'Use this skill when' / 'Do not use this skill when' / 'Limitations' that are somewhat boilerplate and don't add much actionable value. The instructions themselves are high-level bullet points without unnecessary verbosity, but the overall structure has padding. | 2 / 3 |
Actionability | The instructions are entirely abstract and descriptive ('Define plans, pricing...', 'Map subscription lifecycle states...', 'Implement invoicing...'). There are no concrete code examples, specific commands, data models, API calls, or executable guidance. Claude is told to do things but not shown how. | 1 / 3 |
Workflow Clarity | While the instructions list steps in a rough sequence, there are no explicit validation checkpoints, no feedback loops for error recovery, and no concrete sequencing. For a domain involving financial transactions and destructive billing operations, the absence of validation steps and concrete workflow is a significant gap. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files are provided, so the referenced file doesn't exist, and the SKILL.md itself provides almost no substantive content — it's essentially just a pointer with vague bullets, making the disclosure structure hollow. | 2 / 3 |
Total | 6 / 12 Passed |