CtrlK
BlogDocsLog inGet started
Tessl Logo

finance-billing-ops

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.

74

Quality

92%

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/finance-billing-ops

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-organized, token-efficient operator-truth workflow with a clear multi-step sequence and verification checklist. Its main weakness is actionability: it directs Claude on what to inspect but leaves the actual data-retrieval and code-inspection mechanics to be inferred or pulled from sibling skills.

Suggestions

Add concrete retrieval primitives for the live-billing step (e.g., the specific Stripe/checkout queries or the github-ops search entry points to run) so 'start from the freshest billing evidence' is executable rather than directional.

Give one or two concrete locating cues for the code-inspection step (e.g., likely file/path patterns or the entitlement function name) rather than only naming the conceptual area like 'entitlement calculation'.

Optionally fold the most common end-to-end path (sales snapshot + duplicate-charge diagnosis) into a short worked example to bridge the gap between the classification lists and the output template.

DimensionReasoningScore

Conciseness

Lean bullet-driven body that assumes Claude's competence — no explanations of what Stripe, refunds, or entitlements are, and every section earns its place; not the level below because there is no padding or concept restatement.

3 / 3

Actionability

Provides concrete classification lists and a copy-paste output template, but only describes WHAT to inspect ('entitlement calculation', 'seat or quota handling') without the HOW — live-data retrieval and code-inspection mechanics are unspecified and delegated to sibling skills, leaving key execution details missing.

2 / 3

Workflow Clarity

A clearly sequenced four-step workflow (freshest evidence → separate incidents from product truth → inspect code-backed behavior → decision and gap) with an explicit Verification checklist acting as validation checkpoints, matching the clear-sequence-with-checklist anchor.

3 / 3

Progressive Disclosure

Self-contained, well-sectioned skill with no nested or multi-level reference chains; no bundle files exist and none are needed, and the sibling-skill 'Skill Stack' is signaled at one level, satisfying well-organized self-contained structure.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, third-person description that pairs concrete capability enumeration with an explicit 'Use when' trigger clause and a clear niche signal. It is concise without padding and avoids vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete domains and actions — 'revenue, pricing, refunds, team-billing, and billing-model truth' plus 'sales snapshot, pricing comparison, duplicate-charge diagnosis' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does ('Evidence-first ... workflow for ECC') and when to use it via an explicit 'Use when the user wants...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural operator-facing triggers ('sales snapshot', 'pricing comparison', 'duplicate-charge diagnosis') that a user would plausibly say, giving good coverage rather than just jargon.

3 / 3

Distinctiveness Conflict Risk

The 'instead of generic payments advice' framing and billing-truth/code-backed niche give it a clear, distinct trigger space unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.