agentleFS
Sign inStart free
MegapromptingMegaprompting/torque-loop/skills/mechanism/SKILL.md

mechanism

Skill10 starsChanged 4 months agoMITView on GitHub

Name the mechanism when a situation feels confusing. Use to cut through a tangle to the one causal handle. Separates surface symptoms from the underlying mechanism, the constraint causing it, the feedback loop keeping it alive, and the highest-leverage intervention point — then the action that changes the mechanism rather than describing it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. DiegoLopez0208/mechanism★ 11same 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    Use one precise causal model.

    line 33
  2. Distinctive:

    Do not over-explain. The output is a handle, not an essay.

    line 34
  3. Distinctive:

    If the mechanism reframes the objective or reveals the true bottleneck, update state:

    line 50

≈ “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

/ratchet:mechanism — the mechanism knife

Confusion is usually surface noise hiding a single mechanism. This command finds it. It does not produce a taxonomy of possible causes; it names the one causal handle you can actually pull.

Step 0 — Load state

ratchet status

Procedure

Given the confusing situation, separate cleanly — do not blur the layers:

  1. Surface symptoms — what you observe. The complaints, the errors, the friction.
  2. Underlying mechanism — the single process producing those symptoms. One precise model, not a list of possibilities.
  3. The constraint causing the mechanism — the limit or rule that forces this behavior.
  4. The feedback loop keeping it alive — why it persists instead of self-correcting.
  5. Highest-leverage intervention point — where a small push changes the most.
  6. The action that changes the mechanism — a move that alters the system, not one that merely re-describes it.

Rules

  • Use one precise causal model. Resist the urge to enumerate five frameworks.
  • Do not over-explain. The output is a handle, not an essay.
  • Make the next move obvious — a mechanism you can't act on isn't named yet.

Output contract

SYMPTOMS: <what shows on the surface>
MECHANISM: <the one process underneath>
CONSTRAINT: <what forces it>
FEEDBACK LOOP: <what keeps it alive>
LEVERAGE POINT: <where to push>
CHANGING MOVE: <the action that alters the mechanism>

Serialize

If the mechanism reframes the objective or reveals the true bottleneck, update state:

ratchet state set bottleneck "<mechanism-level blocker>"
ratchet state set phase cut

Next: /ratchet:cut to test the mechanism's assumptions, or /ratchet:build the changing move directly.

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.

Check your setup, free