How do I install the Checkup skill?

Run npx skillmds@latest add zedarvates/checkup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Checkup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Checkup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Checkup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Checkup?

zedarvates (@zedarvates) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Checkup by zedarvates — Agent Skill

Name: Checkup
Author: zedarvates

Checkup

Run the canonical, already-optimal project checkup in one command — policy presence, directives health, per-component metrics, infra tips, duplication, and drift detection — so you never have to hand-write a good checkup prompt. Use when the user says "do a complete checkup", "botte doctor", after a component update, when onboarding to a project, or when multiple agents/devs may have caused drift.

zedarvates da156c2 4 files · 38.6 KB Updated Sep 17, 2026

File contents

checkup — the canonical project checkup ("botte doctor")

So a "complete checkup" doesn't depend on you writing a good prompt: one command runs the standard sequence in the right order and prints a single verdict, all local / 0 cloud tokens.

python -m skills.checkup.cli            # current dir
python -m skills.checkup.cli <project> --json
python -m skills.checkup.cli . --pr-comment   # Markdown verdict for a PR comment
python -m skills.checkup.cli . --doctor       # + machine scan + ranked top-3 opportunities
python -m skills.checkup.cli . --doctor --fresh   # re-scan for local LLM backends (not cached)

`--doctor` — the one-verb assembly

--doctor is checkup plus two things it doesn't otherwise do:

machine scan — is a local LLM backend reachable (LM Studio/Ollama)? via [[llm_backends]] audit(); reads the cached registry unless --fresh.
ranked top-3 opportunities — fixes from [[fix]] find_fixes(), ranked by estimated token cost (highest first), plus any remaining drift items, capped at 3.

Both feed a one-line verdict: ✅ sain when there's no drift and a local backend is active, or ⚠️ N optimisation(s), ~X tokens d'opportunités otherwise. Pure assembly of existing modules — no new skill, no new report format.

Sequence (cheap → deeper)

policy — is .botte/policy.md committed? (shared rules for devs/agents)
directives — CLAUDE.md/AGENTS.md health + stale path refs
metrics — LOC per component + always-on cost + savings framing
infra — hardware/software/MCP cluster tips (+ ASCII diagram)
duplication — stdlib AST duplicate-function scan
security — taint / data-flow scan ([[fallow_like]] TaintAnalyzer), CWE-tagged; high-severity findings become drift. 0 cloud tokens.
drift — MCP wired? directives stale/oversized? policy missing? security?

Then points at the deep code audit (secrets/dead-code) for when you want it.

Why

A component update or another dev/agent introduces drift — stale directives, unwired MCP, an oversized CLAUDE.md, a missing policy. /checkup catches all of it in one pass, with a fixed optimal procedure, instead of an ad-hoc prompt that may be sub-optimal and may not prioritise local models.

On pull requests

--pr-comment prints a verdict-first Markdown comment (carrying a stable marker so a bot can edit it in place), including the security section — so the taint/data-flow scan rides into CI for free. The 🧦 Botte Checkup (PR) GitHub Action (.github/workflows/botte-pr-checkup.yml) runs this on every PR and posts/updates a single comment via gh — 0 cloud tokens, no extra dependencies. The workflow sets BOTTE_CHECKUP_CONTEXT=github-pr, so machine-local MCP wiring is reported as not applicable instead of impossible CI drift; local checkups still flag missing wiring. Any project that deployed botte-secrète can reuse the same workflow.

Related: [[preflight]] (enforces prefer-local every turn), [[infra_advisor]], [[metrics]], [[directives_audit]], [[bootstrap]].

---name: checkupdescription: Run the canonical, already-optimal project checkup in one command — policy presence, directives health, per-component metrics, infra tips, duplication, and drift detection — so you never have to hand-write a good checkup prompt. Use when the user says "do a complete checkup", "botte doctor", after a component update, when onboarding to a project, or when multiple agents/devs may have caused drift.---# checkup — the canonical project checkup ("botte doctor")So a "complete checkup" doesn't depend on you writing a good prompt: one commandruns the standard sequence in the right order and prints a single verdict, alllocal / 0 cloud tokens.```bashpython -m skills.checkup.cli # current dirpython -m skills.checkup.cli <project> --jsonpython -m skills.checkup.cli . --pr-comment # Markdown verdict for a PR commentpython -m skills.checkup.cli . --doctor # + machine scan + ranked top-3 opportunitiespython -m skills.checkup.cli . --doctor --fresh # re-scan for local LLM backends (not cached)```## `--doctor` — the one-verb assembly`--doctor` is `checkup` plus two things it doesn't otherwise do:- **machine scan** — is a local LLM backend reachable (LM Studio/Ollama)? via [[llm_backends]] `audit()`; reads the cached registry unless `--fresh`.- **ranked top-3 opportunities** — fixes from [[fix]] `find_fixes()`, ranked by estimated token cost (highest first), plus any remaining drift items, capped at 3.Both feed a **one-line verdict**: `✅ sain` when there's no drift and a localbackend is active, or `⚠️ N optimisation(s), ~X tokens d'opportunités`otherwise. Pure assembly of existing modules — no new skill, no new report format.## Sequence (cheap → deeper)1. **policy** — is `.botte/policy.md` committed? (shared rules for devs/agents)2. **directives** — CLAUDE.md/AGENTS.md health + stale path refs3. **metrics** — LOC per component + always-on cost + savings framing4. **infra** — hardware/software/MCP cluster tips (+ ASCII diagram)5. **duplication** — stdlib AST duplicate-function scan6. **security** — taint / data-flow scan ([[fallow_like]] `TaintAnalyzer`), CWE-tagged; high-severity findings become drift. 0 cloud tokens.7. **drift** — MCP wired? directives stale/oversized? policy missing? security?Then points at the deep code audit (secrets/dead-code) for when you want it.## WhyA component update or another dev/agent introduces **drift** — stale directives,unwired MCP, an oversized CLAUDE.md, a missing policy. `/checkup` catches all ofit in one pass, with a fixed optimal procedure, instead of an ad-hoc prompt thatmay be sub-optimal and may not prioritise local models.## On pull requests`--pr-comment` prints a verdict-first Markdown comment (carrying a stable markerso a bot can edit it in place), **including the security section** — so thetaint/data-flow scan rides into CI for free. The `🧦 Botte Checkup (PR)` GitHubAction (`.github/workflows/botte-pr-checkup.yml`) runs this on every PR andposts/updates a single comment via `gh` — 0 cloud tokens, no extra dependencies.The workflow sets `BOTTE_CHECKUP_CONTEXT=github-pr`, so machine-local MCP wiringis reported as **not applicable** instead of impossible CI drift; local checkupsstill flag missing wiring. Any project that deployed botte-secrète can reuse thesame workflow.Related: [[preflight]] (enforces prefer-local every turn), [[infra_advisor]],[[metrics]], [[directives_audit]], [[bootstrap]].

Frequently asked questions