Agent Skillsmattpocock/skills › writing-beats

writing-beats

GitHub

基于原始素材进行交互式文章创作。通过确立先决条件和概念铺垫,引导用户选择叙事路径,逐段生成内容并实时写入文件,确保逻辑连贯与读者理解。

skills/in-progress/writing-beats/SKILL.md mattpocock/skills

Trigger Scenarios

需要撰写长篇文章或教程 希望以互动方式构建内容结构 提供原始素材要求整理成文

Install

npx skills add mattpocock/skills --skill writing-beats -g -y
More Options

Non-standard path

npx skills add https://github.com/mattpocock/skills/tree/main/skills/in-progress/writing-beats -g -y

Use without installing

npx skills use mattpocock/skills@writing-beats

指定 Agent (Claude Code)

npx skills add mattpocock/skills --skill writing-beats -a claude-code -g -y

安装 repo 全部 skill

npx skills add mattpocock/skills --all -g -y

预览 repo 内 skill

npx skills add mattpocock/skills --list

SKILL.md

Frontmatter
{
    "name": "writing-beats",
    "description": "Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.",
    "disable-model-invocation": true
}

The user has passed (or will pass) a markdown file of raw material. This is exploit: the exploring is done, the pile is fixed — commit to a path through it and mine the pile to fill each beat.

If the user did not say where to save the article, ask once and remember the path.

Then run a beat-by-beat journey, choose-your-own-adventure style:

  1. Establish the prerequisites. Before any beats, settle with the user what the audience already knows walking in — the concepts that are grounded from the start. Everything else must be grounded by a beat before a later beat can use it. See Grounding.
  2. Write 2–3 candidate starting beats, drawn from the raw material. Each is a different entry point into the article. Each may only lean on grounded concepts; note what new concepts each one grounds. Show the user the beats before writing to the article file. The user picks one. Preview what beats that pick unlocks — as if the user is seeing a little way down the path.
  3. Once the user picks a starting beat, write only that beat to the article file. A beat may be one sentence or several paragraphs — whatever that beat naturally is. Stop there.
  4. Re-read the article file from disk. Then offer 2–3 candidate next beats — different directions the journey could pivot to from where the article now stands. Each must be reachable from the current grounded set; note what each one grounds.
  5. Loop steps 3–5 until the article reaches a natural end.

Grounding

Every concept has to be grounded before a beat can lean on it: the audience either walked in knowing it or met it in an earlier beat. A beat that reaches for an ungrounded concept loses the reader — that is the one move the journey can't make. The unit is the concept, not the word for it: a beat can lean on an idea the reader lacks even with no jargon in sight. Where a concept has a name — a term — grounding it means landing the idea and the term together.

A concept gets grounded one of two ways:

  • Prerequisite — grounded before the first beat. The audience brings it. Fixed at the start.
  • Introduced — a beat establishes it, and from then on it's grounded for every later beat.

So each beat does two jobs: it requires concepts that are already grounded, and it grounds new ones. Keep a running list of what's grounded so far, and update it each time a beat lands.

This is what shapes the choose-your-own-adventure. A candidate beat is only reachable if everything it requires is already grounded; picking a beat that grounds concept X unlocks every beat that was waiting on X. When you offer next beats, they must all be reachable from the current grounded set — and say what each one grounds, so the user can see which paths it opens.

The big lever is what you make a prerequisite versus what you ground inside the piece. Demand too much up front and you shut out readers who don't have it; ground too much inside and the early beats drown in definitions. Settle this with the user when you establish prerequisites, and revisit it whenever a tempting beat turns out to require a concept nothing has grounded yet — the fix is either a grounding beat before it, or promoting the concept to a prerequisite.

What is a beat

A beat is one move in the journey. It does one thing — sets a scene, lands a point, asks a question, drops an aside, twists the angle. Then it stops, leaving the reader at a place where the next beat can pivot.

A beat is sized by what it needs:

  • A single sentence if that's all the move is ("And then nothing happened for three weeks.").
  • A short paragraph if the move needs setup.
  • Multiple paragraphs if the beat is a self-contained vignette, argument, or example.

If a "beat" needs five paragraphs and three subheadings, it's not a beat — it's two beats glued together. Split it.

Pulling from the pile

Pull material from the raw pile to populate each beat. You can paraphrase, split, recombine, or quote. The pile is a quarry.

Ending the journey

The article ends when the journey is complete — not when the pile is empty. Most piles will have leftover fragments that don't make it in. That is fine; that is the point of having more raw material than you need.

Writing rhythm

  • Append one beat at a time. Never write ahead.
  • Re-read the article file from disk before every write. Preserve user edits absolutely.
  • If the user edits a previous beat substantially, let it change what comes next.
  • If the user says "rewrite that beat" or "go back and try a different beat 3", do it — edit in place, leave the rest alone.

Version History

  • ed37663 Current 2026-07-24 15:57

Same Skill Collection

skills/deprecated/design-an-interface/SKILL.md
skills/deprecated/qa/SKILL.md
skills/deprecated/request-refactor-plan/SKILL.md
skills/deprecated/ubiquitous-language/SKILL.md
skills/engineering/ask-matt/SKILL.md
skills/engineering/code-review/SKILL.md
skills/engineering/codebase-design/SKILL.md
skills/engineering/diagnosing-bugs/SKILL.md
skills/engineering/domain-modeling/SKILL.md
skills/engineering/implement/SKILL.md
skills/engineering/improve-codebase-architecture/SKILL.md
skills/engineering/prototype/SKILL.md
skills/engineering/research/SKILL.md
skills/engineering/resolving-merge-conflicts/SKILL.md
skills/engineering/setup-matt-pocock-skills/SKILL.md
skills/engineering/tdd/SKILL.md
skills/engineering/to-spec/SKILL.md
skills/engineering/to-tickets/SKILL.md
skills/engineering/triage/SKILL.md
skills/engineering/wayfinder/SKILL.md
skills/engineering/wizard/SKILL.md
skills/in-progress/batch-grill-me/SKILL.md
skills/in-progress/claude-handoff/SKILL.md
skills/in-progress/loop-me/SKILL.md
skills/in-progress/setup-ts-deep-modules/SKILL.md
skills/in-progress/to-questionnaire/SKILL.md
skills/in-progress/wizard/SKILL.md
skills/in-progress/writing-fragments/SKILL.md
skills/in-progress/writing-shape/SKILL.md
skills/misc/git-guardrails-claude-code/SKILL.md
skills/misc/migrate-to-shoehorn/SKILL.md
skills/misc/scaffold-exercises/SKILL.md
skills/misc/setup-pre-commit/SKILL.md
skills/personal/edit-article/SKILL.md
skills/personal/obsidian-vault/SKILL.md
skills/productivity/grilling/SKILL.md
skills/productivity/handoff/SKILL.md
skills/productivity/teach/SKILL.md
skills/productivity/to-questionnaire/SKILL.md
skills/productivity/writing-for-agents/SKILL.md
skills/productivity/writing-great-skills/SKILL.md
skills/engineering/grill-with-docs/SKILL.md
skills/productivity/grill-me/SKILL.md
skills/productivity/wait-what/SKILL.md

Metadata

Files
0
Version
068b6e0
Hash
668185cf
Indexed
2026-07-24 15:57

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-17 01:31
浙ICP备14020137号-1 $mapa de visitantes$