agentleFS
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/writing-shape/SKILL.md

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
  1. Distinctive:

    Strict Concept Grounding: Every concept must be grounded (either as a predefined reader prerequisite or introduced in an earlier block) …

    line 15
  2. Distinctive:

    Multi-Opening Selection: Always present 2–3 distinct opening hooks representing different angles/theses before building the body.

    line 16
  3. Distinctive:

    Action: Read the raw fragment pile end-to-end and establish what foundational knowledge the reader brings to the article.

    line 40
  4. Distinctive:

    Key Point: Keep a live register of grounded concepts throughout the session.

    line 41
  5. Distinctive:

    Action: Ask "Given this block, what does the reader need next?", pull material from the pile, and debate the block format.

    line 53

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

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

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

  1. Input Immutability: The raw material file is strictly read-only; shape the article into a new separate document.
  2. 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.
  3. Multi-Opening Selection: Always present 2–3 distinct opening hooks representing different angles/theses before building the body.
  4. Deliberate Block Formatting: Formally justify the format of every block (prose vs. list, callout vs. inline, table vs. text, quote vs. paraphrase).
  5. 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 AreaTradeoff AnalysisRule
Prose vs. ListArgumentative flow vs. scannable itemsProse carries thesis; lists carry strictly parallel items
Inline vs. CalloutMainline continuity vs. aside contextUse callouts (> [!NOTE]) only if inline disrupts thesis
Table vs. ParagraphsRepetitive structured schemas3+ items with matching keys $\rightarrow$ Table
Quote vs. ParaphraseHistorical phrasing vs. core ideaQuote 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 RationalizationBinding RuleEngineering 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.

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.