calibrate
Skill216 starsChanged 17 days agoApache-2.0View on GitHub
Confronts every block, warning, and piece of noise a change raises with the false positives real projects trigger, measured on this tree's build, then gives a verdict and the calibration each case needs.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- ronniepinnell/caspertheir own version, first seen Nov 8, 2026
- mehboobali98/rmine-skillstheir own version, first seen Nov 6, 2026
- sethatwood/belaytheir own version, first seen Sep 23, 2026
- sparkline-ventures/product-evaltheir own version, first seen Jun 29, 2026
- robonuggets/skillstheir own version, first seen May 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- grainulation/grainulator★ 86same name
- robonuggets/skills★ 36same name
- robonuggets/calibrate★ 18same name
- sparkline-ventures/product-eval★ 15same name
- ronniepinnell/casper★ 1same name
- mehboobali98/rmine-skills★ 0same name
- sethatwood/belay★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectureSkill
- blind-reviewSkill
- cdpSkill
- dashboardSkill
- engineeringSkill
- ingestSkill
- mcp-catalogSkill
- playgroundSkill
- refineSkill
- simulateSkill
- specializeSkill
- testingSkill
- uiSkill
- writerSkill
- lagune-charterSkill
- lagune-detectSkill
- lagune-hardenSkill
- lagune-planSkill
- lagune-proveSkill
- lagune-repairSkill
- laguneSkill
- lagune-specializeSkill
- lagune-verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
The true positives stay: Every recommendation names what stops blocking because of it.
- Distinctive: line 32
Read the charter first. Its principle that only a real risk earns friction sets the tier each piece of evidence earns:
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Calibrating against false positives
A false alarm costs more than its own noise. Each one teaches the user, and the model reading the result, that Lagune can be ignored, so the alarm that matters is dismissed with the rest. This skill finds every place a change raises friction without a real risk behind it, proves each case on a running build, and recommends the calibration that keeps the true positives blocking.
User Input
$ARGUMENTSThe User Input selects the scope, read by meaning in whatever language it is written: a branch (against the default branch unless a base is named), the current work, paths, or a checker or surface to confront. Empty means the current branch against the default branch. Reply in the language the user writes in.
Ground rules
- Read-only on the project. The review changes no code, no test, and nothing under
.lagune/. Builds and fixtures live in the scratchpad. - Measured, never imagined. A case counts only once a build has produced it. A case that cannot run, such as friction a skill's instruction raises, is judged by reading and labeled as read, not measured.
- Named, never plausible. A false positive stands on a real convention, tool, or layout that produces it, named as such, never on an input invented to make the rule fail.
- The true positives stay. Every recommendation names what stops blocking because of it.
The yardstick
Read the charter first. Its principle that only a real risk earns friction sets the tier each piece of evidence earns:
| Tier | Earned by |
| A finding, which fails the run | Evidence that proves a real risk, exposed in the project itself |
| A review lead | A plausible risk the evidence cannot confirm |
| An advisory | A real risk not exposed yet |
| Silence | A harmless look-alike |
Three limits bound every recommendation:
- Doubt fails closed. A state the engine cannot read never becomes silence. It becomes unconfirmed, and many unknowns with one cause collapse into one entry that names the cause.
- The engine stays inside the project. A blind spot that only reading outside the root would close calls for a clearer message, never a wider read.
- No path leaves the scan on the engine's own judgment. A look-alike that lives in a folder, such as a test fixture, changes tier and stays scanned, and leaving it out remains the user's choice in the project's configs.
The cost of the remedy counts too. A message whose advice breaks the project when followed, such as untracking a key the test suite loads, is friction even when its evidence is right.
When invoked
- Map the friction. Read the scope's diff and list every point that can stop or warn the user: each verdict a checker emits and the exit code it sets, each warning a skill tells the agent to raise or record, and each remedy those messages advise. For each, write down the evidence it stands on.
- Name the look-alikes. For each point, name the real projects that produce the same evidence without the risk: defaults a framework commits on purpose, templates, test fixtures, files a tool is designed to commit, formats that share an extension, prefixes that make a value public by design, and places where the state cannot be read, such as a Git worktree or a package inside a monorepo. Name the reverse as well: real risks the change misses, since a blanket warning often exists to cover one, and closing the blind spot is what lets the warning go.
- Build the engine from this tree. Bundle its command-line entry with the options the build script uses, into the scratchpad, with the Prism WebAssembly file beside it. Never run the build script itself, which wipes the build folder.
- Build the fixtures. One small project per case in the scratchpad, each its own Git repository, with every file in the state the case needs: tracked, untracked, or ignored. Add a control group of true positives that must keep blocking.
- Measure. Run the engine in each fixture with an empty home folder, so the user's global Git excludes cannot change the result, and record the output and the exit code. Where a rule matches line by line, run each value alone to pin which rule fires. Run the same evidence through the engine's other paths, such as a value in source against the same value in a config file, since one piece of evidence must earn one tier wherever it appears.
- Classify. Set each case's tier against the yardstick, beside the tier it got, and trace each mismatch to the line that decides it. Separate what the change introduced from what it inherited.
Report
Open with the verdict in one line: whether the change is calibrated, and if not, which tier fails the yardstick.
- False positives that block: a table with the real case, the example measured, the cause with a link to the line that decides it, and the calibration it needs.
- Noise that does not block: warnings and leads that fire without a real risk, or repeat on every run with no way to settle them but leaving the file out entirely.
- What holds: the look-alikes it already silences and the true positives it catches, in a few lines.
- Out of scope: what it inherited from before the change, one line each.
Close with the order to fix them in, by how often each case occurs in real projects and what it costs, and where the fixtures live so the user can run them again. Offer to apply the calibration, and change nothing until the user accepts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

