Run any Skill in Manus with one click

score

Stars0

Forks0

UpdatedJuly 26, 2026 at 14:53

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".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ewebdzine

ewebdzine/claude-code-time-tracker

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

score

description

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:setup first.
API key. Ensure ANTHROPIC_API_KEY is 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.local themselves.
Run the scorer:
```
cd "$APP_DIR"
npm run score-sessions -- --new     # only sessions not yet scored
```
Use -- --all to score everything, -- --rescore to redo, -- --limit N to cap a run.
Report how many sessions were scored and remind the user the badges appear on next dashboard reload (/time-tracker:launch if it isn't running).

More from this repository

same repository

deploy-vercel

ewebdzine/claude-code-time-tracker

Optional wizard to put the Claude Code Time Tracker online as a private, magic-link-gated dashboard on Vercel, fed by your real data. Walks through deploying the app (Vercel CLI or dashboard), turning on passwordless email login (Resend + an email allowlist), wiring private Vercel Blob storage, and scheduling the hourly push that sends your local report up. Run when the user types /time-tracker:deploy-vercel, or says "host the time tracker", "deploy the dashboard to Vercel", "put my time tracker online", "share my dashboard with a login". Local use needs none of this - it's purely for a hosted copy.

2026-07-260

launch

ewebdzine/claude-code-time-tracker

Start the Claude Code Time Tracker dashboard locally and open it in the browser. Boots the Next.js dev server in the background against your ~/.claude logs, waits for it to be ready, prints the URL (http://localhost:3000), and opens it. Run when the user types /time-tracker:launch, or says "open the time tracker", "launch the dashboard", "show me my Claude Code hours", "start the time tracker". If it isn't installed yet, run /time-tracker:setup first.

2026-07-260

setup

ewebdzine/claude-code-time-tracker

One-time local install for the Claude Code Time Tracker dashboard. Copies the app out of the plugin into a stable working directory (~/.claude-time-tracker), installs its dependencies with npm, and verifies it's ready - no API keys, no account, nothing leaves the machine. Run when the user types /time-tracker:setup, or says "install the time tracker", "set up claude code time tracker", "get the time tracker running", "install the dashboard". Re-running is safe and also acts as an update.

2026-07-260

snapshot

ewebdzine/claude-code-time-tracker

Export a static, shareable snapshot of your Claude Code Time Tracker data - a self-contained report file built from your ~/.claude logs, with no server required. Useful for sharing your hours or archiving a point-in-time view without hosting anything. Run when the user types /time-tracker:snapshot, or says "export my time tracker", "snapshot my hours", "save a report of my Claude Code time".

2026-07-260

stop

ewebdzine/claude-code-time-tracker

Stop the locally running Claude Code Time Tracker dashboard. Shuts down the background Next.js dev server that /time-tracker:launch started and cleans up its PID file. Run when the user types /time-tracker:stop, or says "stop the time tracker", "shut down the dashboard", "kill the time tracker server", "close the dashboard".

2026-07-260

name

score

description

Score - grade your prompting (optional)

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:setup first.
API key. Ensure ANTHROPIC_API_KEY is 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.local themselves.
Run the scorer:
```
cd "$APP_DIR"
npm run score-sessions -- --new     # only sessions not yet scored
```
Use -- --all to score everything, -- --rescore to redo, -- --limit N to cap a run.
Report how many sessions were scored and remind the user the badges appear on next dashboard reload (/time-tracker:launch if it isn't running).