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 Plan

by LilMGenius in LilMGenius/paperthin

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory.

MITAuto-check passedDevelopment

Install Re0 Plan

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

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

GitHub CLI
$ gh skill install LilMGenius/paperthin re0-plan --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-plan .claude/skills/re0-plan && 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-plan
GitHub stars
1.1k
Token cost
~1.3k tokens
SKILL.md length
725 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory.

  • Works in 6 steps: Classify the cycle's weight: a fix or… → Create .re0/iteration/-/ and, in the… → (full only) Write WORKFLOW.local.md: the… → …
  • Development work in your project
  • SKILL.md covers Goal, Workflow, Rules and Verification
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Re0 Plan is an agent skill from LilMGenius/paperthin. Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.

Its SKILL.md is about 1.3k 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 Development. 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

  • Development work in your project

Example prompts

  • “s casebook before re0-loop”
  • “/re0-plan”

Workflow steps

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

  1. Classify the cycle's weight: a fix or hardening pass with no real design surface is lightweight; a cycle with a direction genuinely worth…
  2. Create .re0/iteration/-/ and, in the same step, write its first file — the weight decides which
  3. (full only) Write WORKFLOW.local.md: the numbered steps this specific cycle runs through re0-loop's turn order — specific to this build…
  4. (full only) Write EVIDENCE.local.md: the gates from DESIGN.local.md, listed as proof surface still to fill — the bar, not results.
  5. Keep reference material flat as REF-.local.md; promote to a refs/ subfolder only once it multiplies past a couple of files.
  6. Hand off to re0-loop. Do not invoke re0-work here — a from-scratch restart is re0-loop's own mid-cycle call, surfaced by nba when…

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 Plan loads about 1.3k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 725 words of instructions outside code blocks.

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

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). 725 words, ~1,320 tokens.

Download SKILL.mdSave it as .claude/skills/re0-plan/SKILL.md (or your agent's skills folder).
name
re0-plan
description
Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.
disable-model-invocation
true

Open .re0/iteration/<version>-<workname>/ and write into it in the same motion, before a single line of re0-loop's cycle runs.

Goal

A cycle without a written thesis, gate list, and step plan drifts to whatever framing comes first — and a folder opened with nothing in it tells a resumed session nothing at all. re0-plan closes both gaps at once: the folder is never empty from the moment it's created, regardless of which weight the cycle turns out to be. It assumes the full paperthin package installed and names its sibling skills directly. It pairs with re0-release, which retires the folder, and re0-memo, which extends whatever this skill seeded instead of restarting fresh. It is not a portable planning method — the shape it writes is this repo's own convention.

Workflow

  1. Classify the cycle's weight: a fix or hardening pass with no real design surface is lightweight; a cycle with a direction genuinely worth arguing through is full.
  2. Create .re0/iteration/<version>-<workname>/ and, in the same step, write its first file — the weight decides which:
    • lightweight → RETRO.local.md: one paragraph naming the task and why it's lightweight. re0-memo extends this same file at the end; it never starts a fresh one. Stop here.
    • full → DESIGN.local.md: thesis, scope, and quality gates — the same content re0-loop's FRAME turn expects, and enough on its own to survive a session break. When the change touches shippable surface, those gates always include an AGENTS.md/README reflection gate (see Rules). Confirm the read with readchk, size the tier with modelchk; reach for macrothink or another judgment skill only when the direction is genuinely contestable.
  3. (full only) Write WORKFLOW.local.md: the numbered steps this specific cycle runs through re0-loop's turn order — specific to this build, not a restatement of re0-loop's generic stages.
  4. (full only) Write EVIDENCE.local.md: the gates from DESIGN.local.md, listed as proof surface still to fill — the bar, not results.
  5. Keep reference material flat as REF-<topic>.local.md; promote to a refs/ subfolder only once it multiplies past a couple of files.
  6. Hand off to re0-loop. Do not invoke re0-work here — a from-scratch restart is re0-loop's own mid-cycle call, surfaced by nba when warranted, never a setup step.
Show full SKILL.md (368 more words)Show less

Rules

  • The folder is never empty at creation. Every path, lightweight or full, writes real content in the same motion the folder is made, so a session break at any point still leaves something to resume from.
  • Not portable, by design. Names other paperthin skills directly and assumes the full package installed — the opposite of the self-contained default every other skill here follows. It exists only to pair with re0-release and re0-memo, not to travel alone.
  • No padding. Lightweight gets no DESIGN/WORKFLOW/EVIDENCE, and its RETRO.local.md seed stays one paragraph — a task note, not a WORKFLOW.local.md in disguise. A judgment skill or re0-work never gets forced in "just in case."
  • The folder's <version> is provisional. Apply the same minor/patch discriminator re0-release uses — kind not size: is the change, against the artifact's own prior spec, a fix (patch) or a new capability a user newly reaches for (minor)? — and keep it contingent on any unresolved fork the cycle opens. Never pre-commit a firm bump the cycle hasn't earned; a fork that could add a skill leaves the bump undecided until it resolves.
  • Docs stay aligned, like re0-release at ship time. When the cycle's change touches shippable surface, its quality gates always include an AGENTS.md/README reflection gate, assigning each reflection to its register per AGENTS.md's docs-role split: internal mechanism/rules/anatomy → AGENTS.md (LLM + human, injected as instructions), user-facing catalog/experience → README (human-only, never injected). Never dump agent-instruction mechanism into README, and never skip README for a user-facing change. This is the plan-time complement to re0-release's ship-time README step.
  • negatives-as-corpus — nothing this skill or the cycle it opens produces gets deleted; a cycle that goes wrong is retired by re0-release, not discarded.
  • Every EVIDENCE.local.md gate traces back to a line in DESIGN.local.md; don't invent proof surface DESIGN never asked for.

Verification

Before finishing:

  1. The folder has real content from the moment it exists — no empty directory, on either path.
  2. Full path: DESIGN.local.md states a thesis, scope, and gates; WORKFLOW.local.md's steps are specific to this cycle; every EVIDENCE.local.md gate traces to DESIGN.local.md.
  3. Lightweight path: RETRO.local.md is seeded with the task and reason, one paragraph.
  4. Reference material stayed flat unless it earned a refs/ subfolder.
  5. Report which path was taken and why.

© 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-plan of LilMGenius/paperthin.

Open the folder on GitHubat commit 7d5dc62

Compare with similar skills

Re0 Plan 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 Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Re0 Plan this skillLilMGenius/paperthin1.1k—~1.3kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-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 Plan

What does Re0 Plan do?

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. Re0 Plan is an agent skill from LilMGenius/paperthin. Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory.

When should I use Re0 Plan?

Re0 Plan fits situations like: development work in your project.

How do I install Re0 Plan in Claude Code?

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

How do I install Re0 Plan in Codex?

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

Can I use Re0 Plan 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-plan -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-plan, .gemini/skills/re0-plan, .github/skills/re0-plan and .opencode/skills/re0-plan in your project.

What does Re0 Plan need to run?

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

Does Re0 Plan 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 Plan 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 Plan use?

Re0 Plan 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 Plan use?

About 1.3k tokens (SKILL.md is roughly 5.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 Plan?

Skills that share tags, products or a category with Re0 Plan: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Re0 Plan?

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.