paperthin
The one command to remember: type /paperthin, then your dream. It hands the request to re0-workflow, which runs the rest.
LilMGenius · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add LilMGenius/paperthin --skill paperthinAbout this skill
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
- 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
/paperthinwith 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-workflowis 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-workflownever routes back here, so the hand-off cannot loop.
Verification
Before finishing:
- Exactly one Skill tool call ran, to
re0-workflow, carrying the request as typed; or, whenre0-workflowwas not installed, none ran and the person was told to install it. - Nothing else ran from this skill; the report the person sees is the router's.
Delegated implementation: re0-workflow
name: re0-workflow description: "Read one stated intent, pick and order the installed skills that serve it, show that order, then run the steps the session may run and stop where a person must act. Use when someone states a goal but does not know which skills serve it or in what order, asks which skills to use, or wants a job that needs several skills run end to end. Typing /paperthin lands here."
Turn one stated intent into an ordered skill graph, show it, and run the steps the session may run.
Goal
Someone who does not know this suite's catalog should be able to say what they want and see it done. Select and order the installed skills that serve the human's stated intent, show the order before anything runs, run each step the session holds authority for, and stop at the first step that needs the human, with a report of what ran.
Workflow
-
Read the human's stated intent and the installed roster from the host catalog or skill directories. If given only live state without a stated intent, ask for the intent rather than infer it. Read each candidate's contract and invocation lane:
disable-model-invocation: truemeans user-only; otherwise it is model-invoked. -
Select only skills whose triggers and outputs serve the intent. A frozen pipeline (a skill whose own contract runs a fixed sequence of other skills) that already serves the intent is one node, never expanded; read its members only to type it, so the node counts as writing when any member writes and is a
user-handoffwhen any member is user-only. If none fits, show zero steps and say so; if one suffices, use exactly one node and say ordering is trivial. A skill the intent or a selected contract calls for that the roster lacks stays as askipstep, and when a selected step needs its output the run ends with the stop condition unmet, never as a silent skip. Do not pad the graph, require an orientation skill, invent a pipeline skill, or substitute another skill for a missing one. -
Order the selected steps by their contracts' prerequisites: a step depends on another when its firing precondition needs that step's output. Detect cycles before showing the graph; if one exists, the whole result is a
rejectnaming the cycle, such asskill-a -> skill-b -> skill-a, with no steps and no partial order. Give the graph one observable stop condition, the state that means the intent was served; zero steps or arejectends at its own report. -
Give every step an identifier, a target (the skill that acts, or the question when the step is a human decision no skill makes), predecessor identifiers, exactly one type, firing precondition, expected output limited to the target's own contract, skippable condition, and cost owner. Assign its type by the first row below that applies, so a missing user-only skill is a
skip. Where a contract does not say whether its skill writes, count it as writing; where its lane cannot be read, count it as user-only. A step whose type depends on a predecessor's output is shown as conditional with the types it can take, and typed once that output exists.Type Meaning and precondition Cost owner skipThe step does not run, and the graph goes on without it: condition not applicable, skill not installed, or no authority that anyone present could grant. A step that depends on it is skipped too, with the same reason. None. user-handoffThe human acts: the target is user-only, the step is destructive or irreversible, a human decision is needed, or the work needs authority the human holds and the session does not. The human's time, at their discretion. invoke-model-skillThe router runs it: none of the rows above applies, so