score
Skill0 starsChanged 4 months agoMITView on GitHub
Rate how well you prompted Claude in each session (optional, AI-graded). Runs the local prompt-health scorer over your ~/.claude transcripts and writes a 🟢/🟡/🔴 rating, a session type, and a one-line coaching note per session - shown in the dashboard. Needs your own Anthropic API key; runs entirely on your machine, and only the ratings (never your prompts) are ever stored or, if you host it, pushed. Run when the user types /time-tracker:score, or says "rate my prompts", "score my sessions", "how well did I prompt".
- Reads credentials
15 other projects use a version of this.
Adopted by
Most recently taken up by
- akachandan1/video-studiotheir own version, first seen Nov 8, 2026
- Hainrixz/claude-dbtheir own version, first seen Nov 1, 2026
- Hainrixz/claude-seo-aitheir own version, first seen Nov 1, 2026
- maroffo/claude-forgetheir own version, first seen Oct 25, 2026
- askoulwassim/perfect-placementtheir own version, first seen Oct 15, 2026
- gagoar/icebergtheir own version, first seen Oct 10, 2026
Used with
Projects with it also use audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- quantumaikr/quant.cpp★ 403same name
- Hainrixz/claude-seo-ai★ 81same name
- Hainrixz/claude-db★ 22same name
- maroffo/claude-forge★ 17same name
- gagoar/iceberg★ 10same name
- askoulwassim/perfect-placement★ 3same name
- stonegiantstudio/skills★ 3same name
- akachandan1/video-studio★ 2same name
- dcolclazier/skills★ 1same name
- santiment/skills★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- deploy-vercelSkill
- launchSkill
- setupSkill
- snapshotSkill
- stopSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
API key: Ensure ANTHROPIC_API_KEY is available - in the environment or in $APP_DIR/.env.local.
- Very specific: line 29
Use -- --all to score everything, -- --rescore to redo, -- --limit N to cap a run.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Score - grade your prompting (optional)
Adds a prompt-health rating to each session: a 🟢/🟡/🔴 grade, the session type (explore / build / debug / mixed), and a short coaching note. Ratings are calibrated to session type - an exploratory back-and-forth isn't penalised for meandering the way a build session would be. Results are cached locally and surfaced as badges in the dashboard.
Requires an Anthropic API key (the user's own). Scoring runs on this machine against local logs; only the derived rating/type/note are saved - never the prompts or code.
How to run
- App dir:
APP_DIR="${CCTI_APP_DIR:-$HOME/.claude-time-tracker}". If missing, run/time-tracker:setupfirst. - API key. Ensure
ANTHROPIC_API_KEYis available - in the environment or in$APP_DIR/.env.local. If the user doesn't have one, point them to console.anthropic.com → API keys. Never ask them to paste it into the chat; have them put it in.env.localthemselves. - Run the scorer:
Usecd "$APP_DIR" npm run score-sessions -- --new # only sessions not yet scored-- --allto score everything,-- --rescoreto redo,-- --limit Nto cap a run. - Report how many sessions were scored and remind the user the badges appear on next
dashboard reload (
/time-tracker:launchif it isn't running).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.