agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/writing-fragments/SKILL.md

writing-fragments

Skill8 starsChanged 2 months agoMITView on GitHub

Capture and refine raw ideas, quotes, and observations before committing to an article outline. Use when collecting source material, brainstorming essay fragments, or exploring angles without structure pressure — even if the user says \"help me brainstorm notes\". Do NOT use for final draft formatting.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Pure Exploration Mode: Never force premature structuring, outlines, or paragraph grouping.

    line 14
  2. Distinctive:

    Continuous Disk Re-Read: Always re-read the target fragments markdown file from disk before appending to preserve human out-of-band edits.

    line 16
  3. Distinctive:

    No Overhead Metadata: Avoid adding tables of contents, timestamps, author frontmatter, or category tags into raw fragment files.

    line 18
  4. Very specific:

    Action: Ask the user once for the target file path (if omitted) and initialize with # Working Title.

    line 40
  5. Distinctive:

    Key Point: Start capturing immediately from the user's first prompt.

    line 41
  6. Distinctive:

    Key Point: When a powerful recurring theme appears, coin a compact "leading word" (e.g.

    line 46

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

Facilitate low-pressure idea capture and Socratic exploration by continuously extracting raw writing fragments, quotes, analogies, and leading metaphors into a delimiter-separated markdown notes file.

Core Invariants

  1. Pure Exploration Mode: Never force premature structuring, outlines, or paragraph grouping; keep capture friction near zero.
  2. Horizontal Rule Delimiters: Separate every distinct fragment with horizontal rules (---) under a single top-level # Working Title.
  3. Continuous Disk Re-Read: Always re-read the target fragments markdown file from disk before appending to preserve human out-of-band edits.
  4. Leading-Word Extraction: Actively identify and coin compact metaphors ("leading words") that anchor core conceptual points.
  5. No Overhead Metadata: Avoid adding tables of contents, timestamps, author frontmatter, or category tags into raw fragment files.

Architecture & Map of Content (MOC)

[ Freeform Ideation / Grilling Dialogue ] ──► [ Extract Raw Fragment / Leading Word ] ──► [ Append to `notes.md` via `---` ] ──► [ Re-read Before Next Write ]
Fragment TypeStructurePurpose
Sharp SentenceSingle punchy lineReusable hook or thesis anchor
Vignette / AnecdoteShort narrative paragraphConcrete real-world grounding
Quote / DialogueBlockquote with attributionPrimary source evidence
Leading WordCoined metaphor / terminologyLoad-bearing concept for future shaping

Step-by-Step Procedure (TWI)

Step 1: Initialize Working File & Settle Target Path

  • Action: Ask the user once for the target file path (if omitted) and initialize with # Working Title.
  • Key Point: Start capturing immediately from the user's first prompt.
  • Why: Zero upfront bureaucracy maximizes creative momentum.

Step 2: Socratic Exploration & Fragment Extraction

  • Action: Interview the user relentlessly, surfacing non-obvious observations, contrarian takes, and sharp formulations.
  • Key Point: When a powerful recurring theme appears, coin a compact "leading word" (e.g. tracer bullet, fog of war).
  • Inline Checklist:
    • Fragments separated strictly by ---
    • No internal subheadings (H2/H3) inside raw fragment file
    • File re-read from disk prior to every append

Step 3: Incremental Silent Appends

  • Action: Append agreed fragments to disk without interrupting conversational flow.
  • Why: Continuous, non-blocking persistence ensures no fleeting ideas are lost.

Anti-Rationalization Guardrails

Tempting RationalizationBinding RuleEngineering Rationale
"Organize the raw fragments into numbered thematic sections."Forbidden. Keep raw fragments unstructured.Premature organization closes off novel angles and creates cognitive friction.
"Overwrite the file with a newly organized version."Append only; preserve human manual edits.Overwriting destroys out-of-band human phrasing and edits.
"Ask permission before writing every single fragment."Append silently and mention in passing.Constant save confirmation prompts derail productive brainstorming flow.

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.

Check your setup, free