cost-tracker

Track session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cost-tracker/SKILL.md

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 actionable awareness skill with concrete budgets and optimization strategies, though it reads more as reference material than a sequenced workflow. The self-contained organization is appropriate but the workflow sequencing is the weakest dimension.

Suggestions

Add a short numbered workflow (e.g., 1. check /cost, 2. compare against task-type budget, 3. apply relevant optimization, 4. report via the output template) to raise workflow clarity above the implicit-checkpoint level.

Replace the comment-only "Check Current Costs" bash block with an actual runnable command or remove it, since comments alone dilute actionability.

Move the speculative dollar-amount and tool-call budget tables into a references file (e.g., budgets.md) and link to it, keeping the body as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's knowledge without explaining basic concepts, but the comment-only bash block and speculative dollar-amount tables are minor instances that could be trimmed.	4 / 5
Actionability	Concrete numeric thresholds (50/80/100%), tool-call budgets, ten specific optimization strategies, and an output template give mostly executable guidance; the "Check Current Costs" block is comment-only and is the main gap.	4 / 5
Workflow Clarity	The content is primarily reference tables and tips rather than a tightly sequenced workflow; budget-level checkpoints exist but the overall sequence is implicit and lacks a feedback loop, matching the steps-present-but-checkpoints-implicit anchor.	3 / 5
Progressive Disclosure	Sections are well-organized and the skill is self-contained with no external references needed; at roughly 100 lines it exceeds the under-50 simple-skill threshold that would permit a 5, and some dense reference tables could arguably live in a separate file.	4 / 5
	Total	15 / 20 Passed

Description

75%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 concise, third-person description that clearly states what the skill does and when to use it, with natural trigger terms and a distinct cost-tracking niche. It sits just below the top anchor due to slightly limited action enumeration and trigger exhaustiveness.

Dimension	Reasoning	Score
Specificity	"Track session costs, set budget alerts, and optimize token spend" lists three concrete actions, matching the several-specific-actions anchor; not a 5 because coverage is only three actions and "optimize token spend" is somewhat generic.	4 / 5
Completeness	It gives a clear what (track/alert/optimize) and an explicit when ("Use to check costs mid-session or set spending limits"), but the when is slightly less enumerated than the concrete-trigger anchor-5 example.	4 / 5
Trigger Term Quality	"session costs", "budget alerts", "token spend", and "spending limits" are natural user phrases with some synonyms, but lack the exhaustive synonym/extension coverage of the anchor-5 example.	4 / 5
Distinctiveness Conflict Risk	Cost-tracking is a clear niche with distinct triggers and only minor overlap risk with generic budgeting skills; not a 5 because "budget"/"spending" terms could collide with broader planning skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/pro-workflow
Path: skills/cost-tracker/SKILL.md
Commit: 7f7209d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.