Loading...
The playbook Moonrank's Writer Agent uses to write how-to guides that actually finish the job — a clear contract, tested steps, inline fixes, and verification.
Download the methodology, see how the agent structures a procedure, or run it live inside the Writer Agent.
The How-To Guide skill is how Moonrank's Writer Agent turns a task into instructional content readers can finish: the contract stated up front, one tested action per step, screenshots only at the decision points, failures fixed inline, and a verification step that removes all doubt.
It's written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Read it to fix the tutorials your support team keeps apologizing for, or let the Writer Agent draft procedural content from your briefs.
Downloading the playbook is free with a Moonrank account. Drafting how-to content and flagging it for re-testing when the product changes is what the Writer Agent does.
“Our setup tutorial ranks #3 but support still gets 30 tickets a week about that exact process. How?”
The tutorial's step 2 hides four separate actions in one paragraph, three steps have no stated result so readers can't tell if they worked, and the most common failure — the API key scope error behind 19 of your 30 weekly tickets — is answered in an FAQ nobody scrolls to. The rewrite: 11 single-action steps with expected results, that error's symptom and fix inline under step 5, and a final verification step. Ticket volume drops with no ranking change needed.
The job to be done, the reader's starting point, and the verifiable done state.
Audience, prerequisites, done state, and time estimate — before step one.
Each numbered step is one action with a visible result, written by doing, not remembering.
Symptom and fix inline under the steps that fail, and a final step that confirms success.
Who it's for, what they need first, what done looks like, and how long it takes.
One action per number, each with its expected result stated.
Screenshots or output where readers go wrong — not decoration on every step.
The symptom and fix under the step that fails, not in an FAQ graveyard.
An unambiguous way for the reader to confirm the whole thing worked.
The one logical thing a reader who finished should do next.