New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Re0 Memo

by LilMGenius in LilMGenius/paperthin

Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary.

MITAuto-check passedTesting & QA

Install Re0 Memo

skills CLI
$ npx skills add LilMGenius/paperthin --skill re0-memo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LilMGenius/paperthin re0-memo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LilMGenius/paperthin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/coil/re0-memo .claude/skills/re0-memo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
re0-memo
GitHub stars
1.1k
Token cost
~815 tokens
SKILL.md length
469 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary.

  • Works in 8 steps: Read the original objective, final… → Separate working assets from misleading… → Generalize before recording: when… → …
  • Tasks that involve Quality gates
  • SKILL.md covers Goal, Workflow, Rules and Verification
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Re0 Memo is an agent skill from LilMGenius/paperthin. Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Use after a build, QA pass, demo, user complaint, or abandoned attempt when the useful output is what the next pass must learn rather than the code itself.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Quality gates. The repository describes itself as: Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent. The licence is MIT.

When your agent uses it

  • Tasks that involve Quality gates

Example prompts

  • “/re0-memo”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the original objective, final artifact, QA evidence, user complaints, and any local planning notes.
  2. Separate working assets from misleading progress: contracts, schemas, tests, services, vocabulary, and examples that earned reuse vs. UI…
  3. Generalize before recording: when feedback arrives as many specific complaints, cluster them upward into the shared pattern before writing…
  4. Name each failure as an anti-pattern, not a mood.
  5. Convert repeated or high-impact failures into quality gates for the next pass.
  6. Convert vague user direction into architecture vocabulary a fresh agent can use.
  7. Write or refresh local docs for the cycle: a re0-memo for lessons and a plan for next-cycle contracts, gates, and vocabulary.
  8. Verify that a from-scratch agent could avoid the same failure from those docs alone.

What it can do on your machine

Read from SKILL.md and the folder at commit 7d5dc62. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Re0 Memo loads about 815 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 469 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~815

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LilMGenius/paperthin at commit 7d5dc62, republished under its MIT licence (© LilMGenius). 469 words, ~815 tokens.

Download SKILL.mdSave it as .claude/skills/re0-memo/SKILL.md (or your agent's skills folder).
name
re0-memo
description
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Use after a build, QA pass, demo, user complaint, or abandoned attempt when the useful output is what the next pass must learn rather than the code itself.

Turn a completed cycle into lessons the next cycle can actually use.

Goal

re0-memo extracts durable learning from a work cycle without defending the artifact that produced it. A cycle can run, pass tests, and still be the wrong thing. The output is not a changelog or therapy note: it is a local, evidence-backed record of what worked, what misled the build, and what gate the next pass must clear.

Use re0-memo when the artifact is done, failed, disappointing, or ambiguous enough that the next agent needs the cycle's lessons more than its momentum.

Workflow

  1. Read the original objective, final artifact, QA evidence, user complaints, and any local planning notes.
  2. Separate working assets from misleading progress: contracts, schemas, tests, services, vocabulary, and examples that earned reuse vs. UI, panels, scaffolds, or abstractions that only looked productive.
  3. Generalize before recording: when feedback arrives as many specific complaints, cluster them upward into the shared pattern before writing anything down — many specifics against many items usually share one root gap. Record the root and its pattern family as the lesson; keep the specifics under it as evidence, not as lessons themselves.
  4. Name each failure as an anti-pattern, not a mood.
  5. Convert repeated or high-impact failures into quality gates for the next pass.
  6. Convert vague user direction into architecture vocabulary a fresh agent can use.
  7. Write or refresh local docs for the cycle: a re0-memo for lessons and a plan for next-cycle contracts, gates, and vocabulary.
  8. Verify that a from-scratch agent could avoid the same failure from those docs alone.
Show full SKILL.md (205 more words)Show less

Rules

  • Do not defend the artifact. If it missed the product, say what missed.
  • Do not write a changelog. File lists and effort summaries are not lessons.
  • Do not transcribe a specific complaint as a lesson. A lesson that only fixes the reported case keeps the system human-in-the-loop: the same class of failure returns anywhere a person didn't point. Escalate every specific to the pattern that catches its whole class — the reporter's exact words are evidence, not the gate.
  • Preserve negative corpus. Failed paths are training data.
  • Prefer hard gates over advice.
  • Cite evidence from the cycle: objective, file facts, QA output, screenshots, transcripts, diffs, or user feedback.
  • If the next agent cannot act on it, it is not a lesson yet.
  • Keep provenance local; shipped artifacts should not narrate their scars.

Verification

Before finishing:

  1. Every lesson traces to observed cycle evidence.
  2. Every anti-pattern names a concrete failure mode and the gate that catches it.
  3. No lesson is a single reported case in disguise: each covers a class, with the specifics that raised it sitting under it as evidence.
  4. A fresh agent can tell what to preserve, what to discard, and what to test first without reading the whole old session.

© LilMGenius, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/coil/re0-memo of LilMGenius/paperthin.

Open the folder on GitHubat commit 7d5dc62

Compare with similar skills

Re0 Memo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Re0 Memo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Re0 Memo this skillLilMGenius/paperthin1.1k—~815Automated safety check: PassMIT
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT
Triage Sonarqubenetdata/netdata81k—~2.8kAutomated safety check: NotesGPL-3.0
Sonarqube Analysishbmartin/graphviz2drawio275—~508Automated safety check: NotesGPL-3.0
Code SolvingHoangTheQuyen/think-better122—~3.7kAutomated safety check: PassMIT
Trellis Finish WorkOrtonY/smart-resume122—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed

  • Triage Sonarqube

    netdata/netdata

    Inspect, review, or apply authorized triage decisions to SonarCloud issues and security hotspots; also review the Sonar helpers.

    81k GitHub stars~2.8k tokensUpdated today
    Testing & QAAuto-check: notes

  • Sonarqube Analysis

    hbmartin/graphviz2drawio

    Inspect SonarQube Cloud/SonarCloud findings for this repository using local .env credentials.

    275 GitHub stars~508 tokensUpdated 2 mo ago
    Testing & QAAuto-check: notes

  • Code Solving

    HoangTheQuyen/think-better

    Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through 7 steps with evidence-based quality gates.

    122 GitHub stars~3.7k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Trellis Finish Work

    OrtonY/smart-resume

    Wrap up the current session: verify quality gate passed, archive completed tasks, record session progress, push branch, and create PR.

    122 GitHub stars~1.3k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • lo2cin4bt Acceptance Review

    lo2cin4/lo2cin4bt

    Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.

    289 GitHub stars~1.4k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

More from LilMGenius/paperthin

All 28 skills in this repo

  • Modelchk

    LilMGenius/paperthin

    Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the…

    1.1k GitHub stars~1.6k tokensUpdated 9 days ago
    Auto-check passed

  • Re0 Loop

    LilMGenius/paperthin

    Run repeated build - QA - re0-memo - re0-work cycles while preserving learning and letting code die.

    1.1k GitHub stars~579 tokensUpdated 9 days ago
    Auto-check passed

  • Autobahn

    LilMGenius/paperthin

    Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved…

    1.1k GitHub stars~2.1k tokensUpdated 9 days ago
    Auto-check passed

  • Catchup

    LilMGenius/paperthin

    Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean.

    1.1k GitHub stars~785 tokensUpdated 9 days ago
    Auto-check passed

  • Debloat

    LilMGenius/paperthin

    Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved.

    1.1k GitHub stars~813 tokensUpdated 9 days ago
    Auto-check passed

  • Factchk

    LilMGenius/paperthin

    Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established?

    1.1k GitHub stars~717 tokensUpdated 9 days ago
    Auto-check passed

Categories

Questions about Re0 Memo

What does Re0 Memo do?

Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Re0 Memo is an agent skill from LilMGenius/paperthin. Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary.

When should I use Re0 Memo?

Re0 Memo fits situations like: tasks that involve Quality gates.

How do I install Re0 Memo in Claude Code?

Run `npx skills add LilMGenius/paperthin --skill re0-memo -a claude-code`. Or copy the skill folder (skills/coil/re0-memo in LilMGenius/paperthin) into .claude/skills/re0-memo in your project. Claude Code loads it when a task matches its description.

How do I install Re0 Memo in Codex?

Run `npx skills add LilMGenius/paperthin --skill re0-memo -a codex`. Or copy the skill folder (skills/coil/re0-memo in LilMGenius/paperthin) into .agents/skills/re0-memo in your project. Codex loads it when a task matches its description.

Can I use Re0 Memo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LilMGenius/paperthin --skill re0-memo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/re0-memo, .gemini/skills/re0-memo, .github/skills/re0-memo and .opencode/skills/re0-memo in your project.

What does Re0 Memo need to run?

SKILL.md names no scripts, command-line tools or credentials: Re0 Memo is instructions for the agent only.

Does Re0 Memo access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Re0 Memo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Re0 Memo use?

Re0 Memo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Re0 Memo use?

About 815 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Re0 Memo?

Skills that share tags, products or a category with Re0 Memo: Test Guard (amElnagdy/guard-skills, 1.3k stars), Triage Sonarqube (netdata/netdata, 81k stars), Sonarqube Analysis (hbmartin/graphviz2drawio, 275 stars) and Code Solving (HoangTheQuyen/think-better, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Re0 Memo?

LilMGenius (a GitHub user) maintains it in LilMGenius/paperthin, which has 1,130 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 1, 2026.

Source: LilMGenius/paperthin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.