Writing Fragments Skill for Muse
A relentless ideation interview that mines your fragments before you ever structure.
- What
- A relentless ideation interview that mines your fragments before you ever structure.
- Cost
- Free
- Needs
- None — just paste the prompt into a Muse conversation.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
This is the explore phase before any structure: Muse interviews you relentlessly about what you want to write, mining "fragments" — sharp sentences, claims with one-line justifications, vignettes, half-thoughts, quotes, complaints, confessions — into a single running document with no outline imposed. It even pushes you to coin a "leading word": one compact metaphor the whole piece can hang on. Discovered via skills.sh. Beta note: this skill lives in the author's experimental in-progress folder, so treat it as a promising beta. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @mattpocock.
Version:
Install
Prerequisites: None — just paste the prompt into a Muse conversation. Install "Writing Fragments Skill for Muse" for me. Muse runs a relentless ideation interview and captures every usable fragment — claims, vignettes, half-thoughts, quotes — into one running document, imposing no structure at all. Repository: https://github.com/mattpocock/skills/blob/main/skills/in-progress/writing-fragments/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "writing-fragments". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.