- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add LilMGenius/paperthin --skill re0-memo -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add LilMGenius/paperthin --skill re0-memo -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add LilMGenius/paperthin --skill re0-memo -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add LilMGenius/paperthin --skill re0-memo -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/LilMGenius/paperthin/tree/HEAD/skills/coil/re0-memoFrom the publisher
Pull a work cycle's durable lessons into the docs the next pass starts from.
re0-memo pulls durable lessons out of a work cycle without defending what the cycle built. A cycle can run and pass its tests while still building the wrong thing, so the tests are not the verdict. Record three things, each with local evidence: what worked, what misled the build, and which gate the next pass must clear. The output is neither a changelog nor a therapy note.
Use it when an artifact is done, failed, disappointing, or ambiguous enough that the next agent needs the cycle's lessons more than its momentum: after a build, a QA pass, a demo, a user complaint or correction, a request the user had to repeat, a user asking why something was not done, a choice the user had to make that a written default should have made, or an abandoned attempt. Each of these means the user supplied what the work should have supplied itself, so run it in the turn the sign arrives, before the interrupted task resumes and buries it.
A restart from v0 always runs it first. The memo is the restart's map: what the old cycle got wrong and how far it actually stands from its objective, so the restart aims at the measured gap rather than at the old plan's picture of itself.
A lesson fails in two ways besides being wrong. It stays too narrow, so the same failure returns through another tool, surface or actor and nothing fires; or its fix is itself a member of the failure's class, so landing it causes the next failure. The workflow climbs each lesson to the widest class that still holds, searches that class's siblings, and tries to break each prescription before it lands.
It calls four other skills: detool to strip tool, product and person names from a lesson, crossthink when every drafted prescription takes one route, elon to question the drafted prescriptions, and scopechk to place each lesson. It carries two moves of user-invoked skills inline, since no skill can call those: the larger-scale re-read of one decision from macrothink (input: the decision and its boundary; output: what changes once the boundary moves), used to find siblings and the actor rung, and the first nail of hate (input: a plan; output: its load-bearing assumption and the cheapest experiment that would break it), used on each prescription. A step's fallback for a missing skill applies too when the host has no Skill tool, and the memo records each fallback that ran as manual: <skill>. Its field-coverage check follows the failure taxonomies reference. Its output feeds the next cycle, read by a fresh agent who never saw this one.
Run the steps in order.
none observed; never invent a counterexample. A rung so general that it no longer names something the next agent can check is past the top.re0-memo and plan docs hold it; shipped artifacts do not narrate their scars.Before finishing, confirm:
elon row or its manual: elon record, its assumption, its experiment and that experiment's result or an unverified mark, and none is a member of its own lesson's class.crossthink call ran, ran as manual: crossthink, or carries a skip reason, the field check ran or carries one, and every class a field check added or kept cites a saved source.Report the lessons written with the rung each reached, the gates added, the prescriptions dropped or broken before landing, and each owner a lesson landed in.
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary, and measure how far the work stands from its objective. Use after a
---name: re0-memodescription: Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and…---# skills/coil/re0-memo/SKILL.mdOverview
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary, and measure how far the work stands from its objective. Use after a build, QA pass, demo, user complaint or correction, a request the user had to repeat, a user asking why something was not done, a lesson whose own fix caused a new failure, or an abandoned attempt, and always before a restart from v0, when the useful output is what the next pass must learn rather than the code itself.
FAQ
Download skills/coil/re0-memo/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/LilMGenius/paperthin.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
crossthink is not installed, list the drafts' own options and map working mechanisms from at least two distant domains yourself, each with where it breaks. Skip it when the drafts already take two or more routes or the prescription only adds a missing trigger to a rule that exists, and write the skip and its reason in the memo.elon is not installed, ask of each draft what it buys and whether the lesson holds without it, and drop the ones that buy nothing. Then, for each surviving prescription, write the one assumption it rests on about its reader, receiver or trigger (that the receiver can do what it is asked, that the trigger fires, that the reader opens the owner) and the cheapest experiment that would break it: one call, one read of a permission, one counter-case put through it. Run the experiment when it is cheap and reversible, and put the prescription through the siblings of step 6 and through one case where it must not fire. A prescription the experiment breaks, or one that is itself a member of its lesson's class, is redrafted and put through its experiment again. A result is written only from what ran in this pass or what the records show was done; an option the cycle only asked someone for, or only proposed, is unrun. An experiment that cannot run marks the prescription unverified in the memo, and it lands with that experiment written into the plan as the next cycle's first check.re0-memo holding the measured standing and, per lesson, its class at the rung it reached with the ladder beneath, its evidence, its siblings, its prescription with the options and the falsification record (assumption, experiment, result), and its owner, with the field check's table and its field candidates in their own section; and a plan holding the next cycle's contracts, gates, and vocabulary.scopechk is not installed, check the pick against that scope yourself. A rule every project of one author needs lives in that author's shared guide, a fact a teammate or another machine needs lives in the repository they clone, and a procedure lives in the skill or tool that carries it out. When that scope excludes the lesson, pick another place the same reader opens whose scope includes it; a rule placed where its reader never looks has not landed.re0-memo entry as the evidence pointing to it, so the rule lives in one place. Rewrite that passage as though the lesson had always been there: a new idea gets its own step or sentence, and the neighboring sentence keeps its wording instead of gaining an appended clause.