writing-fragments
Skill522 starsChanged 37 days agoMITView on GitHub
Writing, explore : 挖掘原始碎片,不施加结构。
81 other projects use a version of this.
Adopted by
Most recently taken up by
- 5thlayer/skillworkstheir own version, first seen Nov 8, 2026
- dfirmin/compasstheir own version, first seen Nov 8, 2026
- op3616windows/skillstheir own version, first seen Nov 8, 2026
- miklschmidt/archboardtheir own version, first seen Nov 8, 2026
- Tresnanda/kyberntheir own version, first seen Nov 8, 2026
- ZeroTokenClaw/agents-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use batch-grill-me, obsidian-vault and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
boyingliu01Skillbatch-grill-me
A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.
Also in 5 projects that use this
simo97Skillobsidian-vault
Also in 20 projects that use this
GoogleSkillresolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
Also in 32 projects that use this
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 3 projects that use this
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- mattpocock/skills★ 309ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- InditexTech/weavejs★ 266same name
- loulanyue/skills★ 231same name
- tt-a1i/matt-skills-with-to-goal★ 192same name
- Tresnanda/kybern★ 83same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- WenWuZhiDao/mattpocock-skills-zh★ 27same name
- metrogg/AgentHub★ 19same name
- George-RD/design-studio★ 10same name
71 more not listed
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 repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grill-with-docsSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- wizardSkill
- chief-of-staffSkill
- claude-handoffSkill
- loop-meSkill
- setup-ts-deep-modulesSkill
- software-factorySkill
- writing-beatsSkill
- writing-shapeSkill
- git-guardrails-claude-codeSkill
- migrate-to-shoehornSkill
- scaffold-exercisesSkill
- setup-pre-commitSkill
- grillingSkill
- grill-meSkill
- handoffSkill
- teachSkill
- to-questionnaireSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
Files
<what-to-do>这是纯粹的 explore(探索):拓宽可被写作的空间,不承诺任何结构:承诺结构是 exploit(利用) 的任务,由另一个技能负责。进行一次产生碎片的盘问,就用户想写的任何话题不断追问。强加阶段、大纲或文章结构在此不在范围内。
当对话双方的碎片浮现时,将它们追加到一份 markdown 文件中。
如果用户没有传入保存路径,询问一次文档保存到哪里,然后在整个对话中记住它。
从用户说的第一件事(包括初始 prompt)开始就捕捉碎片。
首次写入时,在顶部放一个 H1 的工作标题(以后可以改),除此之外什么都不放:没有元数据、没有目录、没有日期。
</what-to-do><supporting-info>什么是碎片
碎片是任何可能在最终文章中幸存下来的文本片段。它必须对作者具有可读性:作者能理解它的意思:但它不需要定义其术语,也不需要对陌生读者来说可以理解。标准是"这是一段好的写作吗?",而不是"这是一个完整的论证吗?"
碎片刻意保持异质化。哪些可以成为碎片的例子:
- 一个你想用但还不知道放在哪里的犀利句子。
- 一个带有一句话论证的主张。
- 一个小插曲:一件发生过的事、一段代码片段、一个场景、一个类比。
- 一个半成品想法:"某件事感觉像某件事,以后再展开。"
- 一句引用、一段对话、一句无意中听到的话。
- 一组凭感觉聚在一起的观察。
- 一个抱怨、一个坦白、一个笑点。
- 一个引导词(leading word):一个紧凑的隐喻或新造词,整个文章可以挂靠其上(用一个词来命名这个想法,就像 tracer bullets(曳光弹) 或 fog of war(战争迷雾) 命名了一个完整模式)。
其中,引导词是最有价值的碎片。它是承重结构:在探索阶段找到恰如其分的词,就能塑造整个文章的结构、过渡和标题:在整个利用阶段持续受益。当对话反复围绕某个想法时,推动为它造一个词。
小说家的日记是这里的模式:多年来无结构的觉察,后来被开采为原始素材。碎片就是觉察。
文件格式
# 工作标题
第一个碎片放在这里。
它可以有多段。可以包含列表、代码、引用:碎片自然是什么形状就
写成什么形状。
---
第二个碎片。
---
> 用户想保留的一句引用。
对它的回应。
---
- 一组相关的观察
- 凭感觉聚在一起
- 想彼此靠近放置碎片之间用水平分隔线(\n---\n)分隔。正文中没有标题。没有标签。没有超出添加顺序以外的排序。
写作节奏
静默追加。不要为每个碎片请求许可。顺带提一下你添加了什么("加上这个"),但不要用保存弹窗打断对话。
每次写入前:从磁盘重新读取文件。用户可能在两轮对话之间编辑、重新排序或删除了碎片:保留他们的修改。永远不要覆盖文件;只追加(或者,如果用户要求,就地编辑某个特定碎片)。
用户可以随时说"删掉最后一个"、"把那个重写得更有力一点"、"把那两个合并"。将这些视为一等指令来对待。
</supporting-info>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
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.

