Dokimi — Testing skill for Claude Code
Dokimi (Greek δοκιμή, "test, proof") measures whether a skill, MCP doc source, agent profile or repository guidance actually helps a coding agent: paired on/off arm comparisons, novel-vs-known content.
How to install Dokimi
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open intel/dokimi and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Dokimi does
Dokimi (Greek δοκιμή, "test, proof") measures whether a skill, MCP doc source, agent profile or repository guidance actually helps a coding agent: paired on/off arm comparisons, novel-vs-known content analysis, and repository scans with graded agent runs.
Alternatives in Testing
- Loki Spec Status — Check whether the spec has drifted from its lock using Loki's living-spec drift detection, and summarize the r 1.1k ★
- Mda — MDA Open Spec — a Markdown superset for agent-facing documents 615 ★
- Aod.Spec — Create feature specification with automatic PM sign-off - Streamlined v2 89 ★
README
Dokimi — agent measurement framework
[](https://intel.github.io/dokimi/) [](https://codecov.io/gh/intel/dokimi)
**Documentation: ** — guides, plus a [CLI reference](https://intel.github.io/dokimi/reference/cli/) and an [API reference](https://intel.github.io/dokimi/reference/api/dokimi/) generated from the code.
**dokimi** — Greek *δοκιμή*, "test, proof". The name is the method: an artifact does not get trusted because it was written or because it is popular, it gets trusted because it passed a test that could have failed.
Documentation, skills, MCP doc sources and agent persona prompts are cheap to write and easy to over-claim. This repository is the framework that measures whether any of them actually helps a coding agent: change one thing, hold everything else fixed, run the same question or task set, and report the delta together with its p-value.
The measurement is the deliverable. An artifact ships with the scorecard that earned it — a deliberate contrast to popularity-ranked marketplaces, which structurally bury niche HPC and numerical-accuracy tooling.
The framework is vendor-neutral: any model reachable through LiteLLM, any docs, skills or tasks.
What it measures
1. Does it help? Enabled vs disabled arms
An *arm* is one context condition. Every arm runs the same question or task set against the same model, and the report gives the per-arm delta against the baseline with paired statistics. Arms are given as specs (`dokimi arms run --arms …`):
| Arm | What the agent gets |
|---|---|
baseline |
nothing extra |
docs: |
product documentation (local Markdown, URLs, Context7) |
mcp: |
an MCP documentation server it can call |
| `skill:<pa |
Related Skills
Exec Summary Sharpener
Simulates how executives will actually read a document, identifies the 5 weakest points, and provides specific
Claude Interaction Tests
Test whether your CLAUDE.md actually works. A Claude Code skill that restructures agent-facing docs (CLAUDE.md
Testany Agent Skills
Open-source agent skills by Testany: engineering, prompts, content, testing, and SkillDock for visual Codex sk
Publish Skills
publish-skills — pre-publish checklist + sanitizer pipeline for Agent Skills. Spec compliance, README patterns
Specdrive
Spec-driven development, enforced. An MCP server + Mac app that forces AI coding agents through specs, scenari
Test Feature
Intelligently test a feature by automatically detecting whether to use MCP, API, or UI testing, and choosing b
Related Agents
Perf Profiler
Agent-agnostic performance profiler. Measures web, API, bundle, and database performance using reproducible ev
Lean Prover Opus
Escalation-tier Lean 4 + Mathlib prover for the lean-proof-agents repo. Dispatched when a Sonnet lean-prover r
Tp Performance Profiler
PROACTIVELY use this when the user reports slow behaviour, asks to profile/optimize, mentions Core Web Vitals