CtrlK
BlogDocsLog inGet started
Tessl Logo

cost-tracking

Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by model, session, or date.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A concise, highly actionable skill body with executable examples, an explicit validation checkpoint, and a useful anti-patterns checklist. One minor note: the 'Example — summary, by model, last 7 days' header promises a 7-day window, but the script reports today/yesterday/total/by-model without any 7-day filter — the heading should be corrected to match the code.

DimensionReasoningScore

Conciseness

The body is lean: it does not explain what JSONL or tokens are, and every section earns its place — notably the non-obvious cumulative-snapshot gotcha ('summing every row multiply-counts') and the 'prefer estimated_cost_usd' guidance, both of which Claude would not already know.

3 / 3

Actionability

It provides fully executable, copy-paste-ready `node -e` commands for both the log-existence check and a complete summary-by-model report, plus a documented row schema, matching the score-3 anchor.

3 / 3

Workflow Clarity

An explicit validation checkpoint ('First verify the log exists') with a runnable command, an explicit error path ('If the log is missing, do not fabricate usage data'), and an Anti-Patterns checklist give a clear sequence with error recovery; the operation is read-only so the destructive/batch feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files needed and is organized into clearly-headed sections (Where the data lives, When to Use, How It Works, Example, Reporting Guidance, Anti-Patterns, Related) with no nested references, which per the guideline scores 3 for a skill with no need for external references.

3 / 3

Total

12

/

12

Passed

Description

92%

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, well-structured description that clearly states what the skill does and when to use it with natural trigger terms. Its only weakness is that the 'budgets'/'tokens' triggers are not disambiguated from sibling budget-design and token-planning skills, creating mild conflict risk.

Suggestions

Sharpen the 'budgets'/'tokens' triggers to distinguish reporting past usage (this skill) from designing or planning budgets (token-budget-advisor, cost-aware-llm-pipeline) — e.g., 'Use when the user asks about costs already incurred or past spending, not when planning future budgets.'

Lead the 'when' clause with the most distinctive signal — querying the ECC cost-tracker metrics log — so it is less likely to fire for general token-budget or context-compaction requests.

DimensionReasoningScore

Specificity

Concrete verbs 'Track and report' with specific objects ('token usage, spending, and budgets'), a named source ('local ECC cost-tracker metrics log'), and breakdown dimensions ('by model, session, or date') match the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers what ('Track and report... from the... metrics log') and when ('Use when the user asks about...') with an explicit 'Use when' trigger, matching the score-3 anchor.

3 / 3

Trigger Term Quality

'costs, spending, usage, tokens, budgets, or cost breakdowns by model, session, or date' are exactly the natural terms a user would say when they need this skill, matching the score-3 anchor for good coverage.

3 / 3

Distinctiveness Conflict Risk

It is anchored to a distinct data source (reporting recorded usage from a metrics log), but the 'budgets' and 'tokens' triggers overlap with sibling planning skills referenced in the body (token-budget-advisor, cost-aware-llm-pipeline), so it could still trigger the wrong skill — matching the score-2 anchor rather than the clearly-disambiguated score-3 anchor.

2 / 3

Total

11

/

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.