Writing Beats Co-writing Skill for Muse
Turn your pile of raw notes into a finished article, one beat at a time.
- What
- Turn your pile of raw notes into a finished article, one beat at a time.
- 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.
Hand Muse a pile of raw material — notes, transcripts, half-formed ideas — and it turns it into a finished article one beat at a time, like a choose-your-own-adventure: it offers you two or three candidate opening beats, you pick the one that lands, and the journey grows from there. Each new beat can only build on concepts the reader has already met, so the article never leans on an idea it hasn't introduced first. 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 Beats Co-writing Skill for Muse" for me. Give Muse a pile of raw notes or transcripts and it co-writes an article with you beat by beat, offering candidate directions for you to pick at every step. Repository: https://github.com/mattpocock/skills/blob/main/skills/in-progress/writing-beats/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-beats". 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.