CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is tdg-personal/customer-billing-ops

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly lean instruction skill with concrete classification and output guidance, but its destructive refund workflow lacks explicit post-action verification and it gives no specific tool-invocation steps.

Suggestions

Add an explicit post-action verification feedback loop for destructive actions: after refunding or canceling, re-check subscription/invoice state to confirm the change took effect, and re-classify if it did not.

Include concrete tool-invocation guidance (specific Stripe API calls or portal actions) for each action in the preferred order so the operator knows exactly how to execute, not just what to do.

Consider moving the output-format template and the examples-of-good-recommendations into a separate reference file so SKILL.md stays a leaner overview and progressive disclosure can score higher.

DimensionReasoningScore

Conciseness

Largely lean and directive with no padding explaining concepts Claude already knows; a few framing sentences ("The goal is to help the operator answer...", "Treat those as ECC or website follow-up items...") could be trimmed but add direction.

4 / 5

Actionability

Concrete, actionable guidance via a classification table, preferred action order, and a copy-paste output template, but it stops short of specific tool/API invocations (e.g., which Stripe calls to make), leaving a minor execution gap.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with a pre-action classify checkpoint, but destructive refund operations lack an explicit post-action verify/feedback loop, which caps this at 3 per the destructive-operations guideline.

3 / 5

Progressive Disclosure

Well-organized into clear sections (When to Use, Guardrails, Workflow, Output Format, Examples) with easy header navigation, but it is a single self-contained ~135-line file with no references, so it falls short of the split-content ideal.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capabilities and trigger conditions with concrete billing-domain actions. The only minor gap is a few common natural trigger terms (cancel, invoice, charge) not present.

DimensionReasoningScore

Specificity

Lists multiple concrete action areas — "subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis" — plus the tool surface, giving comprehensive coverage rather than just naming the domain.

5 / 5

Completeness

Explicitly answers both what (operate billing workflows such as subscriptions/refunds/churn triage) and when ("Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations") with concrete triggers.

5 / 5

Trigger Term Quality

Strong natural keywords (subscriptions, refunds, churn, billing-portal, Stripe, "help a customer") but misses common user phrases like cancel, invoice, and charge, so it falls just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (customer billing operations via Stripe) with distinct triggers (refunds, churn triage, billing-portal recovery) that minimize overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.