agentleFS
MegapromptingMegaprompting/torque-loop/skills/status/SKILL.md

status

Skill10 starsChanged 4 months agoMITView on GitHub

Read the current ratchet state so the loop doesn't rediscover itself. Use to orient at the start of a session or between moves. Returns the current objective, active artifact, last decision, open defects, confidence, next recommended command, and a staleness warning if work changed without a compile.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    If state is empty (no objective), say so and point to /ratchet:lock or /ratchet:ignite.

    line 53
  2. Very specific:

    If stale, the honest next move is /ratchet:compile before anything else.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 146 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.

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

/ratchet:status — read the ratchet

Orientation without re-derivation. This command reads durable state and tells you exactly where the ratchet sits, so you resume instead of restart.

Procedure

Lead with the receipt — one stable read that answers what is true, what changed, what is safe, what is blocked, and what happens next without transcript archaeology:

ratchet receipt

The receipt always shows the same eight sections in the same order — target · delta · proof · seam · verdict · authority · state · next — so a cold human or agent can resume in under a minute. Emptiness is stated, never omitted.

For the detailed state view or a specific read, add:

ratchet status          # the full state summary
ratchet score confidence
ratchet snapshot repo

What you get

  • Current objective — the locked target.
  • Bottleneck — the chosen blocker.
  • Confidence — three scoped layers (artifact · session · ledger health), so a verified patch is never shown as blocked because of unrelated debt.
  • Active / last artifact — what exists now.
  • Last decision — the most recent commitment.
  • Open defects — unresolved failures, by severity.
  • Open loops & untested assumptions — outstanding pressure.
  • Next action + next command — where to go.
  • Staleness warning — ⚠️ if work changed since the last /ratchet:compile.

Output contract

Return the rendered receipt verbatim, then one line of interpretation:

READ: <one sentence — where the ratchet is and the single most useful next move>

If state is empty (no objective), say so and point to /ratchet:lock or /ratchet:ignite. If stale, the honest next move is /ratchet:compile before anything else.

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.