agentleFS
aaronreneaaronrene/knowtation/.cursor/skills/check-ok/SKILL.md

check-ok

Skill1 starsChanged 2 months agoMITView on GitHub

Check OK — ad-hoc honesty check for any work (roadmap or side research). Scaffolds a side-check freeze if needed, then runs the same freeze-review and optional build-verification path used by every Overseer consumer. Works in Cursor, Claude Code, and via CLI for Copilot / any assistant.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use when the operator says Check OK, check ok, Check if OK, or

    line 12
  2. Distinctive:

    If the operator names a freeze/spec path → use it.

    line 57
  3. Distinctive:

    Follow the freeze-review skill (or freeze-review-loop for rounds).

    line 72
  4. Distinctive:

    Follow the build-verification-review skill.

    line 83
  5. Very specific:

    Do not claim DONE / “shipped” without pass.

    line 84
  6. Distinctive:

    When the session Model is Thinking (or Thinking → Auto):

    line 91
  7. Very specific:

    Never open a new governance lane for a one-off check.

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Check OK

Use when the operator says Check OK, check ok, Check if OK, or /check-ok — for roadmap phases or side research that is not on the ROADMAP. Does not open a new docs.lanes entry.

Purpose

Same twin honesty gates as roadmap re-review loops:

GateWhenTool
Freeze reviewSpec / Thinking output ready (frozen: true)This skill → /freeze-review / /freeze-review-loop + ok review --freeze / ok check-ok
Build verificationImplementation claims done/build-verification-review

Engine is kit-owned (tools/freeze_reviewer/ + cli/commands/review.py) — identical in Scooling, Knowtation, VideoFactory, and any repo after ok sync.

Where this skill is installed

RuntimePath after ok syncHow to invoke
Cursor.cursor/skills/check-ok/Type Check OK or /check-ok
Claude Code.claude/skills/check-ok/Type Check OK or /check-ok
Copilot / any chatN/A (no native skills)Paste docs/CHECK-OK.md or run CLI below
Any terminalCLI in kitok check-ok …

How the operator runs it

Chat (Cursor or Claude Code): type Check OK or invoke /check-ok.

Terminal (works everywhere — Copilot, ChatGPT paste sessions, no IDE skills):

ok check-ok --topic "my-side-research" --dry-run
ok check-ok --path docs/reviews/2026-07-17-my-side-research.md
ok check-ok --path docs/archive/phases/PHASE-FOO.md   # existing freeze artifact

(ok check-if-ok is a deprecated synonym for the same command.)

Chat does the semantic thinking-model review. Terminal runs the mechanical checklist gate (same as ok review --freeze).

Workflow (execute in this session)

  1. Identify the artifact
    • If the operator names a freeze/spec path → use it.
    • Else if a PHASE / side-check doc already exists for the work → use it.
    • Else scaffold under docs/reviews/<YYYY-MM-DD>-<slug>.md via:

      ok check-ok --topic "<short-slug>" --scaffold-only

      Or create the file by hand using the template in this skill directory (SIDE-CHECK-TEMPLATE.md).

  2. Fill scope — intent, interfaces, fail-closed rules, seven-tier test matrix, what must not change. Commit on a feature branch (Tier 1).
  3. Freeze review (beginning gate) — Model: thinking-high
    • Follow the freeze-review skill (or freeze-review-loop for rounds).
    • Run mechanical gate:

      ok check-ok --path <artifact> --dry-run
      ok check-ok --path <artifact>          # stamps on pass when configured

      (ok review --freeze <artifact> is equivalent — same engine.)

  4. If Auto / code landed — build verification (end gate)
    • Follow the build-verification-review skill.
    • Do not claim DONE / “shipped” without pass.
  5. Report — verdict pass | findings | blocked; every finding needs path:line. Append the Review-record table on the artifact.

Thinking sessions (always-on)

When the session Model is Thinking (or Thinking → Auto):

  • End of Thinking / before Auto: freeze review must reach pass (step 3).
  • After Auto / implementation: build verification must reach pass (step 4).

See the always-on rule check-ok-thinking.mdc (Cursor) and AGENTS.md § Check OK (all tools).

Hard stops

Escalate to human — do not greenwash — for:

  • security · irreversible · real_money · gates_tier3

Never open a new governance lane for a one-off check. Never merge to {{vcs.git.main_branch}} as part of this skill (Tier 3).

Read first

  • docs/CHECK-OK.md — portable paste prompt (any assistant)
  • docs/OVERSEER-KIT-SPEC.md §6
  • freeze-review + build-verification-review skills (same footprint)
  • .overseer/config.yaml → freeze_contract

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.