tdg-personal/customer-billing-ops
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
84
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific billing capabilities, names the tooling (Stripe), and provides an explicit 'Use when' clause with natural trigger terms. It covers both the 'what' and 'when' comprehensively while maintaining a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis. Also names a specific tool (Stripe) and the domain (customer billing workflows). | 3 / 3 |
Completeness | Clearly answers both 'what' (operate billing workflows like subscriptions, refunds, churn triage, billing-portal recovery, plan analysis) and 'when' (explicit 'Use when' clause covering helping a customer, inspecting subscription state, or managing revenue-impacting billing operations). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'subscriptions', 'refunds', 'billing', 'Stripe', 'churn', 'customer', 'plan', 'revenue', 'subscription state'. These cover a wide range of terms a user would naturally use when dealing with billing issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around customer billing operations and Stripe. The combination of billing-specific terms (subscriptions, refunds, churn, billing-portal, Stripe) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid operational skill with a well-structured workflow, clear classification framework, and good guardrails for safe billing operations. Its main weakness is the lack of concrete, executable tool invocations (e.g., specific Stripe MCP tool calls or API commands), which limits actionability. The content is reasonably concise but could be tightened in a few areas.
Suggestions
Add concrete tool invocation examples (e.g., specific Stripe MCP tool calls for looking up a customer, listing subscriptions, issuing a refund) to make the workflow steps directly executable.
Trim the 'When to Use' section to fewer, more distinct triggers since several items overlap with each other and with the skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections are slightly verbose—e.g., the 'When to Use' list overlaps with the description, and the 'Examples of Good Recommendations' section adds marginal value. The guardrails classification list could be tighter. | 2 / 3 |
Actionability | The skill provides concrete workflow steps and a useful classification table, but lacks executable code or specific tool commands (e.g., actual Stripe API calls or MCP tool invocations). Guidance is specific in intent but not copy-paste ready for tool usage. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit ordering (identify → classify → act → check gaps → handoff). The 'safest reversible action first' principle and the classification table serve as validation checkpoints, and the separation of customer remediation from product backlog items is a good feedback mechanism. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but everything is inline in a single file. For a skill of this length (~120 lines), some content like the classification table or output format template could be referenced externally. However, no references to external files are made, and the content doesn't quite warrant splitting either—borderline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents