paperthin — Claude Code skill: what it does, how to install
A skill for Claude Code and Codex that takes requests entered via /paperthin and forwards them directly to the re0-workflow router.
MIT 120 installs ★ 1,470 updated 2026-10-25
npx skills add LilMGenius/paperthin --skill paperthin -a claude-codeWhat paperthin does
The skill serves as a single front-door command. Typing /paperthin with a prompt or attached files hands the exact text over to re0-workflow without rephrasing, shortening, or pre-planning steps.
It does not execute tasks or invoke other tools on its own. If re0-workflow is absent from the installed skills roster, paperthin halts immediately and instructs to install it.
What it helps with
- forward a user prompt directly into re0-workflow
- trigger workflow orchestration through a single command
- pass attached files and input text to the router verbatim
Example prompts for the agent
- /paperthin update database schema and run pending migrations
- /paperthin inspect the attached error logs and draft a fix
How to install paperthin
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill paperthin -a claude-code2Manually: put the files in place
~/.claude/skills/paperthin/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/paperthin/
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill paperthin -a codex2Manually: put the files in place
.agents/skills/paperthin/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill paperthin -a cursor2Manually: put the files in place
.cursor/skills/paperthin/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install LilMGenius/paperthin skills/coil/paperthin2Manually: put the files in place
.github/skills/paperthin/SKILL.md1Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill paperthin -a gemini-cli2Platform CLI
gemini skills install https://github.com/LilMGenius/paperthin --path skills/coil/paperthinManually: put the files in place
.devin/skills/paperthin/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add LilMGenius/paperthin --skill paperthin -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about paperthin
How to install paperthin in Claude Code?
Run npx skills add LilMGenius/paperthin --skill paperthin -a claude-code. The skill file will be placed at ~/.claude/skills/paperthin/SKILL.md.
What does paperthin do?
It provides the /paperthin command to hand user requests and attachments directly to re0-workflow. It performs no independent planning or execution.
What is required for paperthin to work?
It requires re0-workflow installed in your environment. If that skill is missing, paperthin halts and asks to install it.
Source text
SKILL.md · MIT
---
name: paperthin
disable-model-invocation: true
description: "The one command to remember: type /paperthin, then your dream. It hands the request to re0-workflow, which runs the rest."
---
Hand the person's request to `re0-workflow`, unchanged, and add nothing of its own.
## Goal
Someone who has never read this suite's catalog types `/paperthin` with what they want, and that is enough. This skill is only a name for that door: every behavior (reading the intent, choosing and ordering the skills, showing the order, running it and stopping where a person must act) belongs to `re0-workflow`. It is user-invoked because it exists for a person to type; the model reaches `re0-workflow` directly, so a second model-facing entry with the same triggers would only split them.
## Workflow
1. Call the Skill tool with "re0-workflow", passing the person's request word for word as the stated intent, and pass along whatever they attached (files, pasted text) the way the host passes attachments to a skill. If they typed `/paperthin` with nothing after it, say so in the call ("no request given"); asking for the intent is the router's job.
## Rules
- Forward only: plan, select, order or run nothing here, and call no other skill. Everything after the hand-off is `re0-workflow`'s.
- Never shorten, rephrase, translate or complete the request; the router reads the person's own words.
- Whether `re0-workflow` is installed is read from the installed roster before the call, never tried as a second call; when it is missing, stop and say so, naming it as the skill to install. Never stand in for it with a plan of your own.
- When the forward call fails, report that failure as it came back and run nothing else.
- `re0-workflow` never routes back here, so the hand-off cannot loop.
## Verification
Before finishing:
1. Exactly one Skill tool call ran, to `re0-workflow`, carrying the request as typed; or, when `re0-workflow` was not installed, none ran and the person was told to install it.
2. Nothing else ran from this skill; the report the person sees is the router's.
© LilMGenius · MIT · LilMGenius/paperthin