Self Review
verl-project/verl-omni
Review your own verl-omni branch against the project rubric before opening or updating a PR.
A skill your agent uses when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores…
Install Skill Doctor
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills skill-doctor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .claude/skills/skill-doctor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .claude/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills skill-doctor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .agents/skills/skill-doctor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .agents/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills skill-doctor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .cursor/skills/skill-doctor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .cursor/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path engineering/skill-doctor/skills/skill-doctor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills skill-doctor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .gemini/skills/skill-doctor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .gemini/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills skill-doctorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .github/skills/skill-doctor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .github/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill skill-doctor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills skill-doctor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/skill-doctor/skills/skill-doctor .opencode/skills/skill-doctor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-doctor" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering/skill-doctor/skills/skill-doctor into .opencode/skills/skill-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-doctor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-doctor- GitHub stars
- 28k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 587 words
- Files
- 12 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores…
- Works in 7 steps: Never upload transcripts, session files,… → Labels only, from the rubric tables. The… → Every suggestion traces to a scored… → …
- The user wants their agent setup graded from real conversation history
- SKILL.md covers Hard rules, Scripts and References and assets
- Runs Python scripts from its folder; calls python
What it does
Skill Doctor is an agent skill from alirezarezvani/claude-skills. Use when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores recent local Claude Code / Codex sessions against efficiency and code-quality rubrics, then drafts skill changes gated by a deterministic aggregator and renders one local shareable report.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts, reference files and assets (for example `assets/report.example.json`, `assets/session_scores.example.json` and `assets/suggestions.example.json`).
It sits in Education, covering Quizzes and assessments and Code quality. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- The user wants their agent setup graded from real conversation history
- Asks which installed skills are actually working
- Wants evidence-backed skill edits — scores recent local Claude Code / Codex sessions against efficiency and code-quality rubrics
- Then drafts skill changes gated by a deterministic aggregator and renders one local shareable report
Example prompts
- “/skill-doctor”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Never upload transcripts, session files, or any excerpt. Local only.
- Labels only, from the rubric tables. The aggregator owns all arithmetic.
- Every suggestion traces to a scored session — or it is dropped. Generic best practice is not evidence.
- Zero suggestions is a success, not a failure to report around.
- Exit 4 from the aggregator is a stop, not an error to swallow or bypass.
- Never touch the user's real skill files without an explicit per-skill yes; proposed edits live under $RUN/proposed/.
- A proposed skill edit follows write-a-skill discipline — trigger phrase in the description, smallest change that expresses the rule…
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Doctor loads about 1.5k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 587 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 587 words, ~1,547 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-doctor/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- skill-doctor
- description
- Use when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores recent local Claude Code / Codex sessions against efficiency and code-quality rubrics, then drafts skill changes gated by a deterministic aggregator and renders one local shareable report.
- argument-hint
- [optional: --repo PATH, --days N, or a question about the setup]
- license
- MIT
- metadata.version
- 1.0.0
- metadata.build_pattern
- Rebuild of warpdotdev/common-skills skill-doctor (MIT): harvest → LLM-judges-with-rubrics → deterministic aggregation gate → self-contained HTML report
- metadata.distinct_from
- skillopt-sleep (nightly automated replay loop with adopt gate; this is one interactive graded pass); write-a-skill (authors a skill from expertise; this…
skill-doctor — grade the agent setup from real sessions
Privacy is the contract. Everything runs locally. Transcripts are condensed, secret-redacted, chmod-0600, and never uploaded — the only shareable artifact is the report the user chooses to share.
Run from the repo being graded. Every artifact goes to one fresh scratch dir, never into the repo:
RUN="$(mktemp -d "${TMPDIR:-/tmp}/skill-doctor-XXXXXXXX")"
python scripts/collect_sessions.py --out "$RUN" # 1 — harvest + redact1 — Collect. Scans Claude Code project-history JSONL and Codex rollouts,
discovers repo skills (.claude/skills, .agents/skills, .codex/skills, plugin
layouts), detects skill usage (Skill invocations, slash commands, SKILL.md paths), samples
newest-first, and writes redacted transcripts. Read $RUN/inventory.json: if
sessions_sampled is 0, tell the user there is nothing recent to score (suggest
--days 90 or --repo) and stop. skills_found 0 is fine — the report becomes a
case for creating skills.
2 — Score. python scripts/score_aggregator.py --inventory "$RUN/inventory.json" --emit-template > "$RUN/session_scores.json". Read each transcript in
$RUN/transcripts/ and judge it against both rubrics — scorers/efficiency.md
and scorers/code-quality.md. Fill the template with a label from the rubric's
table and a 1–3 sentence reason citing transcript specifics. Never invent numeric
scores — the aggregator derives them from labels. Use insufficient_evidence when
a transcript shows no judgeable diff. Also write 1–5 top_findings: the most
impactful cross-session patterns, concrete and specific.
3 — Draft edits. Follow references/skill_edit_governance.md (the filing bar:
would a competent agent with the current instructions still fail this way?). For
each suggestion that clears it, write the full improved SKILL.md to
$RUN/proposed/<skill>/SKILL.md, produce diff -u <current> <proposed>, and record
it in $RUN/suggestions.json citing the sampled session id(s) that motivated it.
Zero suggestions is a valid success — say why per finding. Never modify the user's
real skill files in this step.
4 — Aggregate (the gate). python scripts/score_aggregator.py --inventory "$RUN/inventory.json" --scores "$RUN/session_scores.json" --suggestions "$RUN/suggestions.json". It validates labels against the rubric tables, refuses
scores for unsampled sessions, requires substantive reasons, rejects suggestions
that cite no scored session, computes overall = 0.5·efficiency + 0.35·code_quality + 0.15·skill_coverage, and writes report.json. Exit 4 is a
stop: fix what it names and re-run; never hand-edit report.json around it.
5 — Render + tell. python scripts/render_report.py --report "$RUN/report.json"
→ one self-contained report.html (no JS, no CDN, dark-mode + print-to-PDF). Then
tell the user the grade and the top findings in text, link
file://$RUN/report.html, and ask whether to apply the proposed diffs to their
real skills — apply only on an explicit yes, skill by skill.
Show full SKILL.md (216 more words)Show less
Hard rules
- Never upload transcripts, session files, or any excerpt. Local only.
- Labels only, from the rubric tables. The aggregator owns all arithmetic.
- Every suggestion traces to a scored session — or it is dropped. Generic best practice is not evidence.
- Zero suggestions is a success, not a failure to report around.
- Exit 4 from the aggregator is a stop, not an error to swallow or bypass.
- Never touch the user's real skill files without an explicit per-skill yes; proposed edits live under
$RUN/proposed/. - A proposed skill edit follows write-a-skill discipline — trigger phrase in the description, smallest change that expresses the rule, replace over append.
Scripts
| Script | Role | Exit codes |
|---|---|---|
scripts/collect_sessions.py | Harvest Claude Code + Codex sessions, redact secrets, sample, inventory | 0 · 3 bad input |
scripts/score_aggregator.py | Validate labels/reasons/suggestions, compute grade, emit report.json | 0 · 2 warnings · 3 bad input · 4 validation failure |
scripts/render_report.py | report.json → single self-contained report.html | 0 · 3 bad input |
All support --help, --output json, and --sample (no real history needed).
References and assets
scorers/efficiency.md·scorers/code-quality.md— the two rubrics, preserved verbatim from upstreamreferences/transcript_scoring_canon.md— why rubric-anchored LLM judging works and where it fails (7 sources)references/session_mining_privacy.md— the local-only contract, redaction pattern canon (7 sources)references/skill_edit_governance.md— the filing bar for proposing skill edits (7 sources)assets/session_scores.example.json·assets/suggestions.example.json·assets/report.example.json— the three handoff shapes
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (scripts, references, assets) in engineering/skill-doctor/skills/skill-doctor of alirezarezvani/claude-skills.
- SKILL.md
- assets/report.example.json
- assets/session_scores.example.json
- assets/suggestions.example.json
- references/session_mining_privacy.md
- references/skill_edit_governance.md
- references/transcript_scoring_canon.md
- scorers/code-quality.md
- scorers/efficiency.md
- scripts/collect_sessions.py
- scripts/render_report.py
- scripts/score_aggregator.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Skill Doctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Doctor this skillalirezarezvani/claude-skills | 28k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Self Reviewverl-project/verl-omni | 1.2k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Codebase to Coursezarazhangrui/codebase-to-course | 5.7k | — | ~4.4k | Automated safety check: Pass | None | |
| Auto Improvecrimeacs/auto-improve | 135 | — | ~651 | Automated safety check: Pass | MIT | |
| Create Skill Testdotnet/skills | 5.6k | 1 repos | ~6.1k | Automated safety check: Pass | MIT | |
| Dhdna ProfilerK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Codebase to Course
zarazhangrui/codebase-to-course
Turns a codebase into an interactive single-page HTML course for non-technical learners, with scroll modules, animated diagrams, quizzes and plain-English code translations.
Auto Improve
crimeacs/auto-improve
GAN-style iterative improvement loop for any text artifact. An agent skill from crimeacs/auto-improve.
- Official
Create Skill Test
dotnet/skills
Scaffolds eval.yaml evaluation specs for skills, custom agents, and redistributable gh-aw workflow packages in the dotnet/skills repository.
Dhdna Profiler
K-Dense-AI/scientific-agent-skills
Applies the DHDNA framework as an exploratory rubric for reasoning and writing patterns in supplied text.
Comment Judge
fmflurry/settings-opencode
LLM-as-a-judge rubric for code comments (forbidden, false, stale, narration, noise, keep).
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Skill Doctor
What does Skill Doctor do?
A skill your agent uses when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores…. Skill Doctor is an agent skill from alirezarezvani/claude-skills. Use when the user wants their agent setup graded from real conversation history, asks which installed skills are actually working, or wants evidence-backed skill edits — scores recent local Claude Code / Codex sessions against efficiency and code-quality rubrics, then drafts skill changes gated by a deterministic aggregator and renders one local shareable report.
When should I use Skill Doctor?
Skill Doctor fits situations like: the user wants their agent setup graded from real conversation history; asks which installed skills are actually working; wants evidence-backed skill edits — scores recent local Claude Code / Codex sessions against efficiency and code-quality rubrics; then drafts skill changes gated by a deterministic aggregator and renders one local shareable report.
How do I install Skill Doctor in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill skill-doctor -a claude-code`. Or copy the skill folder (engineering/skill-doctor/skills/skill-doctor in alirezarezvani/claude-skills) into .claude/skills/skill-doctor in your project. Claude Code loads it when a task matches its description.
How do I install Skill Doctor in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill skill-doctor -a codex`. Or copy the skill folder (engineering/skill-doctor/skills/skill-doctor in alirezarezvani/claude-skills) into .agents/skills/skill-doctor in your project. Codex loads it when a task matches its description.
Can I use Skill Doctor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill skill-doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-doctor, .gemini/skills/skill-doctor, .github/skills/skill-doctor and .opencode/skills/skill-doctor in your project.
What does Skill Doctor need to run?
Going by SKILL.md and its folder, Skill Doctor needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Skill Doctor access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill Doctor safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Skill Doctor use?
Skill Doctor is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Doctor use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Skill Doctor?
Skills that share tags, products or a category with Skill Doctor: Self Review (verl-project/verl-omni, 1.2k stars), Codebase to Course (zarazhangrui/codebase-to-course, 5.7k stars), Auto Improve (crimeacs/auto-improve, 135 stars) and Create Skill Test (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Doctor?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.