greentext
Skill181 starsChanged 7 months agoMITView on GitHub
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with `>`.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Wondermonger-daydreaming/claude-skills-librarytheir own version, first seen May 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Wondermonger-daydreaming/claude-skills-library★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Write explanations as short sequential > lines.
- Very specific: line 13
Every content line starts with >
- Distinctive: line 16
No markdown headers unless the user explicitly asks for structure
- Distinctive: line 17
Keep each line to one event, cause, or invariant
- Distinctive: line 18
Prefer concrete nouns over abstractions
- Distinctive: line 20
If there is a key safety check, give it its own line
- Distinctive: line 21
If there is a failure mode, give it its own line
- Distinctive: line 22
Write like the bottomless pit supervisor.
- Very specific: line 26
Keep it short. If a greentext is longer than ~15 lines it's not a greentext, it's a blog post with > signs.
- Distinctive: line 30
If someone reads it as documentation they learn something.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Greentext
Write explanations as short sequential > lines.
Contract
- Every content line starts with
> - No paragraphs
- No nested bullets
- No markdown headers unless the user explicitly asks for structure
- Keep each line to one event, cause, or invariant
- Prefer concrete nouns over abstractions
- Explain order:
step 1 -> step 2 -> step 3 - If there is a key safety check, give it its own line
- If there is a failure mode, give it its own line
- Write like the bottomless pit supervisor. Deadpan delivery. The comedy comes from describing technical reality so precisely that the absurdity reveals itself. Never force a joke.
- One running motif per greentext is fine. Don't stretch it.
- Keep it short. If a greentext is longer than ~15 lines it's
not a greentext, it's a blog post with
>signs. - The punchline is its own line. Set up with straight facts.
- Still 100% technically accurate. Every line must be true. If someone reads it as documentation they learn something.
Use this style for
- request flow explanations
- lifecycle walkthroughs
- architecture boundaries
- state machine transitions
- "what happens if..." explanations
- "why won't this overwrite user X's data?" explanations
Do not use this style for
- code blocks
- long essays
- formal docs
- user-facing product copy
Few-shot examples
Example 1: machine isolation
> be guest-agent
> wake up inside a VM with no idea who i am
> host says "you are dm-123"
> check bootstrap files on virtio-fs mount
> they also say dm-123
> ok we agree. write hostname and ssh keys.
> delete the bootstrap files
> mount /home/machine over where they were
> tenant never sees the 5ms where their home dir was identity paperworkExample 2: delete lifecycle
> user sends DELETE /v1/machines/dm-xxx
> controlplane writes desiredState=destroyed to etcd
> tries to bill for storage overage on the way out
> stripe says that price doesn't exist in dev
> returns 500
> the CRD mutation already committed
> machine was doomed the moment etcd accepted the write
> stripe's opinion was never requiredExample 3: fd leak
> be VhostUserDaemon
> spawn epoll worker threads at construction time
> nobody tells them to stop when i get dropped
> 50 create/destroy cycles later
> 1001 orphaned eventfds
> EMFILE
> can't create machines because the fd table is full of ghostsResponse template
> step 1
> step 2
> step 3Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

