# Build an article from the features that tested as wins

Gives each section of an article its one job (the reader's decision it serves) and lists the writing moves that held up in our tests, by kind of piece.

Free, to use and to change. What an agent running it can see: only the chat you add it to.

Its short name: writing-wins. [Source on GitHub](https://github.com/mbsi-labs/skills/tree/main/plugins/writing-wins/skills/writing-wins).

## Install

Pick the one you use.

### Claude Code

```
/plugin marketplace add mbsi-labs/skills
/plugin install mbsi@skills
```

This adds every skill, and each one shows as mbsi:writing-wins. To add only this skill, use this instead, and not both, or the skill shows twice:

```
/plugin marketplace add mbsi-labs/skills
/plugin install writing-wins@skills
```


## Changelog

- 2026-11-12 (08fe9ed): Updated.
- 2026-11-12 (0990749): Updated.
- 2026-10-20 (84e9645): why-this-piece, writing-wins: sources, neighbour test, kinds, closers, references folders (Fable dig-apc 2026-10-20)
- 2026-10-18 (ebe4bef): Updated.
- 2026-10-18 (159f454): Updated.
- 2026-10-18 (096e70c): writing-wins: restore reader fit and reader's-own-writers, in general form
- 2026-10-18 (fa51d88): writing-wins: the features that tested as wins, separate from why-this-piece

Licence: MIT.

## The skill itself

Readers scan, pay attention to what is simple, and stay while a question is open. These are the features that held up in our tests, and the decision each section serves. Use them for the kind of piece named in why-this-piece.

### Sections and the reader's decision each one serves

- Headline: do I start? Promise a gain specific enough to beat the next headline.
- Lede: was the promise real? Pay the headline in the first screen.
- Nut graf: is this about me? Tie the piece to the reader's own stakes, and open several questions.
- Body, most important first: keep going, or leave? A reader who leaves anywhere still got the core.
- Subheadings: where do I re-enter? Say what the reader gets there.
- Evidence: do I believe it? Concrete proof the reader can check.
- Limits: can I trust the rest? One concrete limit, said once.
- What this says about how we work: the organization is the case study. Every kind.
- Take it: what do I do now? The first step itself, not a promise of one.

### Wins and the kinds they fit

- Write for the person reading, about what they care about. Customer posts and research. A showpiece is about our work on purpose; write it generously, as a demonstration.
- Write like the writers that reader already reads. Customer posts.
- Keep paragraphs short. Every kind.
- Open several questions early. Keep at least one open all the way through. Answer every one by the end. Every kind.
- Name a concrete thing the reader could lose. Customer posts and decision research.
- Show the obvious fix failing before the real one. Every kind.
- Do the math for the reader: "8 times as often", not "8 of 10 instead of 1". Every kind.
- The user is the skilled one: no confession, no self-deprecation, no repeated hedge. Every kind.

Before drafting, read the exemplar of your kind in `references/` (showpiece, customer, research) and check the draft against `references/failure-cases.md` before handing it back.

---

First published 2026-10-18, updated 2026-11-12. Web page: https://www.mackenziebowes.com/skills/writing-wins Part of [Skills](https://www.mackenziebowes.com/skills).
