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.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/finance-billing-ops/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 operational workflow with concrete inspection targets, a classification taxonomy, and a copy-ready output template. The main gaps are minor Guardrails/Pitfalls redundancy and the absence of an explicit retry feedback loop in verification.

Suggestions

Deduplicate the overlapping prohibitions between Guardrails and Pitfalls (e.g., the 'per seat' and 'marketing language' rules) so each section covers distinct ground.

Add an explicit validate-and-retry loop to the Verification section (e.g., if a product-truth claim cannot be code-backed, return to step 3 and re-inspect before reporting).

Tighten the Workflow step lists so each bullet is a distinct action; a few items overlap with the Output Format template fields.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no padding about what MRR, Stripe, or refunds are), but the Guardrails and Pitfalls sections repeat overlapping prohibitions ('do not say per seat' / 'do not infer team billing from marketing language'), a minor trim opportunity keeping it below 5.

4 / 5

Actionability

Concrete, specific guidance throughout — explicit code paths to inspect (checkout, entitlement calculation, seat/quota handling), a classification taxonomy, and a copy-ready output format template; actionable but instruction-only rather than executable code, so just under 5.

4 / 5

Workflow Clarity

Four numbered workflow steps are clearly sequenced and backed by an explicit Verification checklist (live-data statement, code-backed product truth, separated conclusions); no validate->fix->retry feedback loop is present, though it is a diagnostic skill where that is less critical, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Skill Stack, When to Use, Guardrails, Workflow, Output Format, Pitfalls, Verification) with sibling-skill references signaled in Skill Stack; no bundle files exist to split further, and at ~120 lines the under-50-line auto-5 exception does not apply, so 4.

4 / 5

Total

16

/

20

Passed

Description

83%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 description that clearly states both capability and trigger conditions with concrete, natural operator terminology. Its only weakness is modest synonym coverage and a slight overlap risk with the related customer-billing-ops skill.

DimensionReasoningScore

Specificity

Names concrete deliverables — 'sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality' — alongside the domain list, listing several specific actions with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.

4 / 5

Completeness

Explicitly answers what ('Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC') and when ('Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis...') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural operator phrases like 'sales snapshot', 'pricing comparison', 'duplicate-charge diagnosis', and 'refunds' map well to what a user would say; good coverage but limited synonyms, so just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'code-backed billing reality instead of generic payments advice' framing carves a distinct operator-truth niche, but a sibling customer-billing-ops skill creates minor overlap risk, keeping it just below 5.

4 / 5

Total

17

/

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.