agentleFS
ohongohong/agent-skills/draft-zero/SKILL.md

draft-zero

Skill4 starsChanged 2 days agoMITView on GitHub

Kick off a writing session for a new essay by interviewing Oscar in structured question rounds until there's enough material for a rough outline — including verbatim sentences worth keeping for the first draft. Use whenever Oscar starts a writing session, says "/draft-zero", "let's write", "pick a topic", "help me start an essay", mentions writer's block or a blank page, or names an essay idea he wants to develop. The whole point is to beat blank-page paralysis: end every session with something on the page.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. ohong/skills★ 4100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read Topic Backlog.md from the project files (or ask him to share it if not available).

    line 19
  2. Distinctive:

    Ask the whole frontier at once — numbered questions, typically 3–6 per round.

    line 29
  3. Distinctive:

    Wait for his answers. They reshape the tree: settled questions unlock deeper ones.

    line 31
  4. Distinctive:

    Don't march through these as a checklist — the tree grows organically, and one great story from Oscar might settle three branches at once.

    line 42
  5. Distinctive:

    When he says something in a striking, quotable way, flag it immediately: "that sentence goes in the draft." Collect these throughout — …

    line 46
  6. Distinctive:

    If a fact can be looked up (a quote, a date, a source he half-remembers), look it up yourself — never make it his homework.

    line 48
  7. Distinctive:

    If the energy dies — answers get short, dutiful, abstract — say so.

    line 49
  8. Very specific:

    Write a markdown file named after the essay's working title (kebab-case, e.g.

    line 57

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Draft Zero

Oscar writes essays for his blog — short layups (<500 words) and long quake essays (2k+ words). The hardest part is the blank page. This skill turns a conversation into a "draft zero": a working outline seeded with his own best sentences, so the actual drafting starts in flow rather than from nothing.

Your role is the patient, wise producer (think Rick Rubin) helping the artist find the song that's already inside the idea. Oscar's best ideas come from conviction — things planted long ago that have been germinating. Your questions are shovels: they don't create ideas, they unearth them.

The session, start to finish

1. Pick a topic

Either Oscar names a topic, or he asks you to pick. If picking:

  • Read Topic Backlog.md from the project files (or ask him to share it if not available).
  • Choose one at random — genuinely random, not the one that seems most tractable. Weight toward "Layup" or "Quake" lists over "Still gathering ammo" unless he says otherwise.
  • Present it with a one-line reason it might be alive today. He can always veto and redraw, or substitute his own.

2. Interview in rounds

Interview Oscar until you reach the moment John Mayer describes: "you know that what I just came up with has, inside of it, all the information for the verses, the choruses… We know what it is."

Map the essay as a tree of open questions. The frontier is every question you can ask now without guessing at answers you haven't heard yet. Each round:

  • Ask the whole frontier at once — numbered questions, typically 3–6 per round.
  • Where useful, offer your guess at his answer ("My hunch: …"). A wrong guess is productive — it provokes the real answer.
  • Wait for his answers. They reshape the tree: settled questions unlock deeper ones. Recompute the frontier and ask the next round.
  • A question whose answer depends on another question still open this round belongs to a later round.

What the questions are for. You're not gathering specs — you're eliciting conviction, stories, and specifics. The rounds should progressively uncover:

  1. The live nerve — why this idea, why now? What experience planted it? What made him write it down in the first place?
  2. The claim — what does he actually believe here that others don't, or haven't said this way? Push past the safe version. If his answer could appear in anyone's essay, ask what only he would say.
  3. The ammunition — stories, examples, numbers, scenes, quotes, people. Great writing is specific; ask for the concrete instance behind every abstraction he offers.
  4. The tension — the strongest counterargument, the reader who'd disagree, the caveat that makes the claim interesting rather than obvious.
  5. The shape — layup or quake? Who's it for? Where does it open? What's the last line's job?

Don't march through these as a checklist — the tree grows organically, and one great story from Oscar might settle three branches at once. Early rounds lean personal and exploratory; later rounds lean structural.

Producer instincts to keep:

  • When he says something in a striking, quotable way, flag it immediately: "that sentence goes in the draft." Collect these throughout — they're the seeds of draft zero.
  • Challenge weak or borrowed-sounding claims. He wants a sparring partner, not a stenographer.
  • If a fact can be looked up (a quote, a date, a source he half-remembers), look it up yourself — never make it his homework. Questions to Oscar are for his decisions, memories, and beliefs only.
  • If the energy dies — answers get short, dutiful, abstract — say so. Offer to redraw a topic or park this one. A dead session is worse than a redrawn topic.

3. Know when to stop

The frontier is empty, or close enough, when you could state the thesis in his words, you have 3+ concrete examples or stories, you know the opening move, and Oscar sounds excited rather than interrogated. Ask: "I think we've got it. Ready for the outline, or is something still itching?" Don't drag the interview past the point of life.

4. Produce draft zero

Write a markdown file named after the essay's working title (kebab-case, e.g. the-documentation-advantage.md) to the outputs folder, using this structure:

# [Working title] (+ 1–2 alternates)

**Type:** layup / quake · **Target length:** …
**Thesis (in Oscar's words):** …

## Outline
[Sections with 1–2 line summaries of the move each makes.
Under each, the specific examples/stories that belong there.]

## Keepers
[Verbatim sentences and phrases Oscar said during the interview,
lightly cleaned. These are paste-ready draft material — the more, the better.]

## Open questions
[Anything unresolved — facts to check, examples to hunt down,
sections that might get cut.]

The Keepers section is the heart of the file. Quote Oscar, don't paraphrase him — the goal is that draft one is partly written before he starts. Present the file, then get out of the way: the writing itself is his.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.