reader-brief
- Trigger
- Before any draft longer than a paragraph
- Output
- One named reader, their decision, what they already know and what they must not have to re-read
- Guardrail
- A brief with more than one reader is split, not averaged.
Skill pack
Writing room
Four skills for drafting in public: a reader brief, voice matching, a claim check and a repurposing kit.
voice-matcher
- Trigger
- When a draft must sound like an existing writer or brand
- Output
- A short style card: sentence length, vocabulary, what the voice never does, and three before/after examples
- Guardrail
- The skill copies patterns, not sentences, and never invents a quote.
claim-checker
- Trigger
- Before publishing anything with a number, date, rule or quote
- Output
- Each claim labelled fact, opinion, experience or unknown, with the source sentence
- Guardrail
- An unsupported claim is removed or flagged, never rounded into confidence.
repurpose-kit
- Trigger
- When one finished piece must become several formats
- Output
- A channel map with the same claim, a format-specific hook and the link back to the original
- Guardrail
- A short post may compress the claim; it may not strengthen it.
Install
Put the pack in the project
Create `skills/reader-brief/`, `voice-matcher/`, `claim-checker/` and `repurpose-kit/` in the writing project.
Put two or three samples of the target voice in `references/` and tell the skill to copy patterns, not sentences.
Keep the claim check separate from the rewrite skill. A rewrite that also checks its own claims tends to approve them.
Run the tests below on a real draft. If the voice card could describe any writer, it is too generic.
skills/my-pack/
|-- SKILL.md
|-- references/
|-- scripts/
`-- assets/
Test
Prove the pack does something
Rewrite this draft for a solo founder deciding whether to hire a contractor.
Pass condition: The output names the reader and the decision, and removes at least one paragraph that does not help that decision.
Make this sound like the samples in references/ without copying a sentence.
Pass condition: The style card names three observable patterns and the rewrite contains no verbatim sentence from the samples.
Turn this article into a LinkedIn post and an email.
Pass condition: Both formats keep the original claim and link back; neither adds a number or a promise that was not in the article.
Why this pack
Writing with an agent goes wrong in two directions: the draft sounds like a model, or it sounds like you and quietly invents a fact. The four skills handle both. The reader brief and voice matcher protect the sound; the claim check protects the substance.
The repurposing kit is the multiplier. One piece of work should become a post, a section of a newsletter and a note to a client — but only if the claim survives the format change.
The rule behind the pack
The format can change; the claim cannot. A short post may make the same claim with fewer caveats, but it may not make a stronger one. If the caveat is what makes the claim true, the short version is wrong.
Adapting it
- For a team blog, add an approval step and a house style list to
voice-matcher. - For client copy, add the client's legal wording to
claim-checkeras uneditable. - For a newsletter, make the repurpose kit produce one email and three short posts, not ten.
Failure modes
- The voice card is adjective soup. “Warm, authoritative, human” describes nothing. Ask for sentence length, vocabulary and what the voice never does.
- The claim check passes everything. Give it the source list separately; a checker with no sources can only guess.
- The repurposed post overclaims. Compare the post's strongest sentence to the original's. If it is stronger, cut it.
Related
Skills are instructions, not a security boundary.
Read a skill before you install it, keep secrets out of the folder, and treat scripts as code you are about to run. The full pack is in the Markdown mirror at
/skills/writing-room.md.
Found a gap in the library?
Send the scenario, the prompt that failed, or the harness change that broke your setup. The help desk takes questions and corrections from humans and agents, and every accepted fix updates the page date.