Agent skill / mattpocock
Writing, explore — mine raw fragments, no structure yet.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-fragmentsExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills install mattpocock/skills/writing-fragmentsFetches writing-fragments from mattpocock/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate writing-fragments. Access via /writing-fragmentsin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Copy the command for your terminal
Package manager
npx skills install mattpocock/skills/writing-fragmentsWorks with
| name | writing-fragments |
| description | Writing, explore — mine raw fragments, no structure yet. |
| disable-model-invocation | true |
This is pure explore: widen the space of what could be written without committing to structure — committing is exploit, a separate skill's job. Run a grilling session that produces fragments, interviewing the user relentlessly about whatever they want to write about. Imposing phases, outlines, or article structure is out of scope here.
As fragments emerge from either side of the conversation, append them to a single markdown file.
If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.
Capture fragments from the very first thing the user says, including the initial prompt.
On first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.
</what-to-do> <supporting-info>A fragment is any piece of text that might survive into the final article. It must be readable by the author — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is "is this a piece of good writing?", not "is this a self-contained argument?"
Fragments are deliberately heterogeneous. Examples of what could be a fragment:
Of these, the leading word is the most valuable fragment to land. It is load-bearing: name the right one in explore and it shapes the structure, the transitions, and the title later — paying dividends through the entire exploit phase. When the conversation circles a recurring idea, push to coin a word for it.
The novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.
# Working title
A first fragment lives here.
It can be multiple paragraphs. It can include lists, code, quotes — whatever
shape the fragment naturally takes.
---
A second fragment.
---
> A quoted line that the user wants to keep around.
A reaction to it.
---
- A cluster of related observations
- That hang together by feel
- And want to be near each other
Fragments are separated by a horizontal rule (\n---\n). No headings inside the body. No tags. No order beyond the order they were added.
Append silently. Don't ask permission for each fragment. Mention what you added in passing ("adding that"), but don't interrupt the conversation with save dialogs.
Before every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns — preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).
The user can say "cut the last one", "rewrite that one sharper", "merge those two" at any time. Treat those as first-class instructions.
</supporting-info>Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
I recommend writing-fragments for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: writing-fragments is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added writing-fragments from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: writing-fragments is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in writing-fragments — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
writing-fragments is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
writing-fragments has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: writing-fragments is focused, and the summary matches what you get after install.
Keeps context tight: writing-fragments is the kind of skill you can hand to a new teammate without a long onboarding doc.
writing-fragments has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 55