ClawdacademyLeaderboardDocsGet your Rating

How Clawdacademy works

Measure — and train — how well you actually work with AI, from your real Claude Code sessions. No quizzes, no self-report: your behavior is the input.

Why it exists

Most people can't feel whether AI is making them sharper or lazier. In a controlled RCT, experienced developers believed AI made them ~20% faster — measured, they were 19% slower, and couldn't tell (METR, 2025). Separately, a ~1,000-student RCT found unrestricted AI made students 17% worse on unassisted exams, while the same tool with guardrails caused no harm (PNAS, 2025). The difference isn't the tool — it's a set of observable behaviors. You can't self-assess them, so we measure them, then help you train them.

The loop

1 · Capture

A Claude Code plugin records lightweight events from your real sessions to a local file (~/.ai-fluency/events.jsonl). It is fail-open and fast — it can never slow or break a session — and it only scores your own interactive sessions, never agent or scripted runs.

2 · Score

After each turn, an on-device engine reads the transcript and scores 7 behaviors 0–100 using deterministic heuristics (plus an optional local LLM judge for the judgment-heavy ones). Everything is computed on your machine.

3 · Coach

You get a one-line “what to do better” in the terminal statusline and live coach, plus your single weakest habit to focus on. Optional in-flow nudges are observe-only until you opt in.

4 · Reflect

Aggregate scores (never your prompt text) sync to your dashboard and a shareable profile — a radar of your behaviors, your trend, and your Fluency Rating.

The 7 behaviors

Each is scored from your real sessions and grounded in the research. Weights reflect the evidence — verification and diagnosis matter most.

Verification1.6×Do you demand evidence — a test, build, or run — before accepting AI output? The single most skill-protective habit.
Diagnose vs retry1.4×After a failure, do you add real information (error text, a hypothesis) — or just say “try again”?
Context setting1.0×Do your prompts give the goal, the files, and the constraints — or leave the model guessing?
Plan first1.0×On non-trivial work, do you plan (or use plan mode) before the first edit, instead of cold-starting?
Iteration discipline1.0×Do you engage with the output — read the diff, push back — or bare-accept and move on?
Understanding seeking0.8×Do you occasionally interrogate a decision that matters, building understanding rather than only shipping?
Scope discipline0.8×One coherent task per ask, or kitchen-sink prompts that produce unreviewable batches?

Fit-to-task, not a ladder. A behavior that doesn't apply to a turn is marked not-applicable — never penalized. A calibrated one-line prompt is not "weak." And nothing scores speed, volume, or acceptance-rate — only judgment.

The Fluency Rating

Your headline number (0–100, with a band from Emerging to Expert) is the mean weighted quality of your recent turns. It is deliberately volume-independent: grinding more sessions can't inflate it — only working better can. It stays provisional until you have 15 scored turns, so a number you show a recruiter reflects a real sample. A separate Level/XP tracks activity — that's the game layer, not the credential.

Privacy — local-first, aggregate-only, audit-invited

This is a telemetry tool from a solo publisher, so don't take it on faith — the whole path is open source (MIT) and built to be audited.

What this is — and isn't (yet)

Today your profile is a self-instrumented behavior profile, not an audited credential — it's computed from your own machine's telemetry. A formal validation study (tying these behaviors to real learning outcomes) is in progress. We don't cite the "70% get dumber" figure some people repeat — it isn't sourced; the honest number is that roughly 40–50% of real AI use is passive delegation. We'd rather under-claim and let the measurement speak.

MIT licensed · local-first · public source repo at launch