Lists multiple specific concrete actions: recurring billing, invoice generation, dunning management, proration, and tax calculation. These are distinct, well-defined capabilities.

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.

Includes relevant domain terms like 'billing', 'invoice', 'dunning', 'proration', and 'tax calculation', but misses common user variations like 'subscription billing', 'payment retry', 'failed payments', 'billing cycle', or 'charges'. Some terms like 'dunning' and 'proration' are more technical than what users would naturally say.

The billing domain is fairly specific, but 'automated billing systems' is broad enough to potentially overlap with payment processing, accounting, or subscription management skills. The word 'Master' is vague and doesn't help distinguish it.

The skill is relatively brief but includes several sections that are somewhat generic and don't add much value (e.g., 'Do not use this skill when' lists obvious cases, 'Limitations' section restates common sense). The instructions themselves are high-level bullet points that don't waste many tokens but also don't provide much unique information Claude wouldn't already know.

The instructions are entirely abstract and vague — 'Define plans, pricing, billing intervals' and 'Implement invoicing, payments, retries' are descriptions of what to do, not concrete guidance on how to do it. There are no code examples, no specific commands, no schemas, no concrete patterns. Everything actionable is deferred to a resource file that doesn't exist in the bundle.

The instructions list high-level activities but lack clear sequencing, validation checkpoints, or feedback loops. For a billing system involving financial transactions, tax compliance, and payment processing, the absence of explicit validation steps and error recovery workflows is a significant gap. The mention of 'Validate with sandbox payments' is too vague to constitute a real checkpoint.

The skill references `resources/implementation-playbook.md` for detailed patterns and examples, but no bundle files are provided, meaning the reference leads nowhere. The SKILL.md itself contains almost no substantive content, making it an empty shell that depends entirely on a non-existent resource file.