Verify the project's riskiest invariant with TLA+, Lean, or Kani — chosen by property shape — and leave a project-local skill the next agent reruns; assumptions are part of the deliverable. For properties tests cannot reach.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Generate a project-local skill that formally verifies one high-risk property and can be rerun by any later agent. Formal methods pay off only on properties tests cannot reach; this skill exists to find that one property, verify it, and leave the verification behind as structure.
verify and the test suite are the right tools(!) when the code does not actually guarantee it (pid reuse,
atomic filesystem steps, integer widths, an honest clock). The register is
part of the deliverable — an unlisted assumption is an unearned theorem,
and a (!) the code later starts guaranteeing is a model owed an update.apalache/TLC, lake build, cargo kani).
A violated property is a finding: minimize the counterexample, check
whether the code shares the flaw, and report before adjusting the model..claude/skills/verify-formal-<property>/SKILL.md containing: the
property in one sentence, the spec file path, the exact run command, the
pass criteria, the assumption list, and the source lines the model
tracks. The next agent reruns the command; it never re-derives the model.appendLedgerEntry and defaultLedgerPath from the installed package's
dist/features/verification-ledger/index.js (resolve the package root
the figure-it-out way; babysit's ledger step demonstrates the exact
invocation). Never append raw rows to .omc/state/verification-ledger.tsv;
the writer owns header creation, locking, and cell sanitization. Write
formally-verified only after a green rerun with the run command as
evidence; a counterexample records verifier-failed with the
counterexample as evidence, and no positive row is written until the
finding is resolved.When the modeled code changes shape (lines move, protocol steps change),
hand to the maintain-formal-verification-skill skill: it re-checks each
assumption against current code, updates cited lines, and reruns. A spec
that cites lines that no longer exist is stale, and a stale spec's green is
worthless — say so out loud in the session.
Yeachan-Heo/oh-my-claudecode
dec7e41
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.