Skip to content
Back to skills

Duolog Calibrate

ASecurity

Use only in a project that has .duolog/config.yaml, and only when the person asks for calibration by name; never suggest it. Calibrates duolog routing for this project.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 6, 2026
ai-agentsgo

Security analysis

A100/100

Scanned November 11, 2026

npx -y skills add lorem-dev/duolog --skill duolog-calibrate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Duolog Calibrate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Duolog Calibrate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lorem-dev-duolog-calibrate/badge)](https://www.skillsdirectory.com/skills/lorem-dev-duolog-calibrate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: duolog-calibrate
description: Use only in a project that has .duolog/config.yaml, and only when the person asks for calibration by name; never suggest it. Calibrates duolog routing for this project.
disable-model-invocation: true
metadata:
  duolog-version: "1.8.2"
---

Stop unless this project has `.duolog/config.yaml`.

# Calibrate duolog for this project

Run this only because the person asked for it. Never start calibration on
your own, never mention it unasked, never raise caps
(`calibration.max_weekly_share`, `calibration.max_window_share`), and never
write AGENTS.md or CLAUDE.md. When several leads are active, pass
`--lead <id>` with the lead id from SessionStart to `run`, `resume` and
`judge`.

Run the steps in order. Show each command's output. Where a step says stop,
end your turn and wait for the person; do not go on by yourself.

1. `duolog calibrate survey`. Show the findings.
2. `duolog calibrate classes`. Show the config diff. **Stop:** the person
   approves or edits. Then run `duolog calibrate classes --apply`, with
   `--skip <name>` for each part the person left out.
3. `duolog calibrate mine`. Show the counts per class and the exclusions.
4. `duolog calibrate plan`. Show the plan as printed. **Stop:** ask for one
   approval of the costed run. On approval, run
   `duolog calibrate plan --approve <hash>` with the hash the plan printed.
5. `duolog calibrate run`. On a pause or stop, report the reason and end
   your turn; the person asks later and you run `duolog calibrate resume`.
   When it says `re-approve`, go back to step 4 and run `plan` again. When
   it stops at `approved cap`, the run part is over: go on to step 6.
6. `duolog calibrate judge`. On a pause or stop, report it and end your
   turn; the person asks later and you run `judge` again. **Stop:** show
   each class batch. Record each of
   the person's answers with `duolog verdict <id> confirm` or
   `duolog verdict <id> correct <criterion>=<o>/<p>`. When the person asks to
   drop a rewritten task, run `duolog calibrate drop <task>`.
7. `duolog calibrate propose`. Show the per-class diff and the project-part
   diff. **Stop:** the person applies the order with `duolog learn --apply`
   (run it only when they say so) and approves the project part; on that
   approval, run `duolog calibrate propose --apply-project`.

`duolog calibrate status` shows where the run is.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.