writing-shape
Skill8 starsChanged 2 months agoMITView on GitHub
Shape raw notes, transcript fragments, and research into a structured, coherent article draft. Use when assembling collected fragments into narrative sections, establishing flow, and building a draft block by block — even if the user says \"turn these notes into a draft\". Do NOT use for initial fragment generation.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 67 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Strict Concept Grounding: Every concept must be grounded (either as a predefined reader prerequisite or introduced in an earlier block) …
- Distinctive: line 16
Multi-Opening Selection: Always present 2–3 distinct opening hooks representing different angles/theses before building the body.
- Distinctive: line 40
Action: Read the raw fragment pile end-to-end and establish what foundational knowledge the reader brings to the article.
- Distinctive: line 41
Key Point: Keep a live register of grounded concepts throughout the session.
- Distinctive: line 53
Action: Ask "Given this block, what does the reader need next?", pull material from the pile, and debate the block format.
“Common” is measured: kept by at least 6 in 10 of the 67 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Writing Shape
Mine raw notes, transcript fragments, and research piles into a structured, coherent article draft by enforcing concept grounding, candidate opening hooks, and deliberate block-level formatting.
Core Invariants
- Input Immutability: The raw material file is strictly read-only; shape the article into a new separate document.
- Strict Concept Grounding: Every concept must be grounded (either as a predefined reader prerequisite or introduced in an earlier block) before any subsequent paragraph leans on it.
- Multi-Opening Selection: Always present 2–3 distinct opening hooks representing different angles/theses before building the body.
- Deliberate Block Formatting: Formally justify the format of every block (prose vs. list, callout vs. inline, table vs. text, quote vs. paraphrase).
- Incremental Persistence: Append and refine the article draft file paragraph-by-paragraph with live disk re-reads before every write.
Architecture & Map of Content (MOC)
[ Raw Notes / Fragment Pile (Read-Only) ] ──► [ Establish Reader Prerequisites ] ──► [ Select Opening Hook (2-3 Options) ] ──► [ Block-by-Block Construction ]| Decision Area | Tradeoff Analysis | Rule |
| Prose vs. List | Argumentative flow vs. scannable items | Prose carries thesis; lists carry strictly parallel items |
| Inline vs. Callout | Mainline continuity vs. aside context | Use callouts (> [!NOTE]) only if inline disrupts thesis |
| Table vs. Paragraphs | Repetitive structured schemas | 3+ items with matching keys $\rightarrow$ Table |
| Quote vs. Paraphrase | Historical phrasing vs. core idea | Quote when exact words matter; paraphrase for clarity |
Step-by-Step Procedure (TWI)
Step 1: Ingest Pile & Settle Prerequisites
- Action: Read the raw fragment pile end-to-end and establish what foundational knowledge the reader brings to the article.
- Key Point: Keep a live register of grounded concepts throughout the session.
- Why: Prevents cognitive gaps where articles lean on unintroduced jargon.
Step 2: Draft 2–3 Candidate Openings
- Action: Present 2–3 distinct openings with different angles and force a selection.
- Key Point: The chosen opening sets the explicit contract for the rest of the draft.
- Inline Checklist:
- Raw pile untouched
- Prerequisites recorded
- Opening agreed and written to target draft file
Step 3: Grow Draft Paragraph-by-Paragraph
- Action: Ask "Given this block, what does the reader need next?", pull material from the pile, and debate the block format.
- Key Point: Re-read file before writing and append immediately.
- Why: Step-by-step composition ensures seamless transitions and eliminates fluff.
Anti-Rationalization Guardrails
| Tempting Rationalization | Binding Rule | Engineering Rationale |
| "Generate the entire article all at once in one big turn." | Draft and debate block by block with the user. | Single-shot generation produces generic prose and ignores user tone preferences. |
| "Edit the raw notes file directly during shaping." | Raw material is read-only; write to a separate draft. | Altering the source pile destroys raw fragments needed for future articles. |
| "Use jargon before introducing the underlying concept." | Enforce prerequisite grounding before leaning on terms. | Ungrounded concepts alienate readers and weaken argumentative structure. |
Other versions76 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 76
- mattpocock/skills★ 309ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- devcxl/mattpocock-skills-zh★ 522same name
- InditexTech/weavejs★ 266same name
- loulanyue/skills★ 231same name
- tt-a1i/matt-skills-with-to-goal★ 192same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- WenWuZhiDao/mattpocock-skills-zh★ 27same name
- metrogg/AgentHub★ 19same name
- George-RD/design-studio★ 10same name
66 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.
Used alongsideProjects with it also use loop-me, claude-handoff and 5 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.
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 46 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 36 projects that use this
simo97Skillobsidian-vault
Also in 25 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 4 projects that use this
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
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 32 projects that use this
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-data-remediationSkill
- ai-engineeringSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- engineering-workflow-guideSkill
- git-safety-guardrailsSkill
- goalSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- j-spaceSkill
- migrate-to-shoehornSkill
- ml-best-practicesSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- retroSkill
- scaffold-exercisesSkill
- setup-engineering-workflowsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- skill-conductorSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- workflow-designerSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
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.

