写作节拍

安全 社区

技能解读

writing-beats 把写作过程拆成「一个 beat 一个 beat」的旅程——你给一份 markdown 原料,技能跟你来回推进,每次只写一个 beat到文章文件里,然后停下,再列 2–3 个 next beat 让你选下一个方向。关键纪律:永远不写下一个 beat 之前的事;永远先 re-read 文件再写。

什么是 beat

一个 beat 是旅程中的一步动作——可能是布景、落点、提问、插入旁白、或翻一个角度,做完就停,让读者落在「下一 beat 可以从这里转弯」的位置。它的大小由它要做的事决定:一句话("And then nothing happened for three weeks.")、一个段落(需要铺设的小动作)、几个自包含段落(一个完整 vignette / 论点 / 例子)。如果一个 "beat" 需要五段 + 三个小标题,那它不是 beat,是两个 beat 粘在一起,要拆。

工作流

① 用户传一份 markdown 原料;没说存哪问一次记下;② 写 2–3 个候选起始 beat——都从原料里来、各代表不同入口,先把候选给用户看再决定;用户选一个,并预览那个 beat 之后可能通向哪些路径;③ 选定后只写那一个 beat 到文章文件,停;④ 从磁盘 re-read 文章文件,再给 2–3 个候选 next beat(不同方向的 pivot);⑤ 循环 ②–④ 直到旅程自然结束。

写作节奏

追加式,一次一个 beat,永不写在前面。每次写之前必须 re-read 文章文件,绝对保留用户的编辑。如果用户大改了前面的 beat,让它影响后面的方向。"rewrite that beat"、"go back and try a different beat 3"——就地改,其他不动。

旅程何时结束

当旅程完整时结束,不是当原料用完。多数原料会有剩余 fragment 没被收纳,这就是有更多原料的意义:你在挑选,不是在搬运。

适合的场景

  • 把已沉淀的 fragment / 笔记长成一篇有节奏的文章
  • 写技术博客 / essay 时想分段推进、每一步都让作者看到方向
  • 多人 / 多 session 接力写作,每次写一个 beat 不污染上下文

不适合

  • 想要一次性出整篇:用 writing-shape 段落式生长更顺
  • 写说明性 doc / API 文档:beat 节奏不适合规约性内容

配套

writing-fragments(前置:先攒一份原料)、writing-shape(把原料按段落而非 beat 长成文章)、writing-skills(语调纪律)、grill-with-docs(按文档锚定术语)。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
安全
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@mattpocock · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

<what-to-do>

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](#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.

</what-to-do>

<supporting-info>

## 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.

</supporting-info>

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。