How do I install the Write The Page skill?

Run npx skillmds@latest add vcxcvii/write-the-page in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write The Page safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write The Page?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write The Page free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write The Page?

vcxcvii (@vcxcvii) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write The Page by vcxcvii — Agent Skill

Name: Write The Page
Author: vcxcvii

Write The Page

Write a draft from a brief, matching the site's real voice samples rather than a description of the voice, covering every standalone claim, and passing the slop check on itself before returning. Use this skill whenever the user asks to: - Write a draft, an article, or a page from a brief - Turn a brief into actual copy Trigger even for casual requests like "write the draft", "write this article", "draft <slug>", "turn this brief into a page".

vcxcvii 2159cf6 3.7 KB Updated Sep 17, 2026

File contents

write-the-page

Context load

Run rainmaker context --check first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing.

Then read, in this order:

context/business.md in full. If absent, stop: "No business context. Run rainmaker audit, then the know-my-buyer skill."
context/voice.md if this skill writes prose. If absent, stop and say so.
context/glossary.md if this skill names products, features or competitors.
data/strategy.json if this skill reads or writes strategy.
Only the data/ files listed in this skill's Consumes table. Never crawl or call an API the core already covers.

If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:

"Business context was edited after the strategy was written. Re-run know-my-buyer, or run rainmaker context --sync to accept the prose as authoritative."

Then stop.

If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run know-my-buyer to replace it."

Consumes

File	Why	If missing
`briefs/<slug>.md`	everything the draft must cover	"No brief for . Run `brief-my-writer` first."
`context/voice.md`	real samples to match	required, see context load
`data/strategy.json`	proof ids to verify against	run `know-my-buyer`

Produces

drafts/<slug>.md.

Refuses when

No brief exists for the requested slug: "No brief for . Run brief-my-writer first. Writing without a brief produces content nobody can defend at review."

Procedure

Read the voice samples in context/voice.md before writing a sentence. Match their sentence-length distribution and paragraph rhythm, not a description of the voice.
Write to the brief's standalone claims first, then build the piece around them, so the extractable sentences are load-bearing rather than bolted on.
Every claim that is not common knowledge carries a proof id from the brief or a link. Unsourced claims get removed, not softened into a vaguer unsourced claim.
Use the quoted buyer language verbatim at least once in the first 200 words.
Include every internal link the brief named, from the source page the brief specified.
Run the slop check from skills/_shared/voice-rules.md against your own draft before returning it. Fix violations, then report what was fixed.

Decision rules

Never invent a number, a statistic, or a customer detail. If the brief did not supply it and it is not common knowledge, the sentence does not survive.
The em-dash rule applies to your own output, not just to review comments about it.
A draft that ignores a standalone claim from the brief is incomplete; go back and include it rather than noting the omission.

Output

The draft itself, in Markdown, plus a short note:

Draft written: <word count> words.
Slop check: <passed / fixed n issues before returning>
Buyer language used: "<quote>" (first 200 words: yes/no)
Brief claims covered: <n> of <n>

Done when

The slop check passes, every brief claim is covered or explicitly flagged as cut and why, the buyer-language quote appears early, and every internal link the brief named is present.

---name: write-the-pagedescription: Write a draft from a brief, matching the site's real voice samples rather than a description of the voice, covering every standalone claim, and passing the slop check on itself before returning. Use this skill whenever the user asks to: - Write a draft, an article, or a page from a brief - Turn a brief into actual copy Trigger even for casual requests like "write the draft", "write this article", "draft <slug>", "turn this brief into a page".---# write-the-page## Context loadRun `rainmaker context --check` first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing.Then read, in this order:1. `context/business.md` in full. If absent, stop: "No business context. Run `rainmaker audit`, then the `know-my-buyer` skill."2. `context/voice.md` if this skill writes prose. If absent, stop and say so.3. `context/glossary.md` if this skill names products, features or competitors.4. `data/strategy.json` if this skill reads or writes strategy.5. Only the `data/` files listed in this skill's Consumes table. Never crawl or call an API the core already covers.If `strategy.json.context_hash` does not match the current hash of `context/business.md`, say exactly:"Business context was edited after the strategy was written. Re-run `know-my-buyer`, or run `rainmaker context --sync` to accept the prose as authoritative."Then stop.If `context/business.md` carries `confidence: stub`, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run `know-my-buyer` to replace it."## Consumes| File | Why | If missing ||---|---|---|| `briefs/<slug>.md` | everything the draft must cover | "No brief for <slug>. Run `brief-my-writer` first." || `context/voice.md` | real samples to match | required, see context load || `data/strategy.json` | proof ids to verify against | run `know-my-buyer` |## Produces`drafts/<slug>.md`.## Refuses whenNo brief exists for the requested slug: "No brief for <slug>. Run `brief-my-writer` first. Writing without a brief produces content nobody can defend at review."## Procedure1. Read the voice samples in `context/voice.md` before writing a sentence. Match their sentence-length distribution and paragraph rhythm, not a description of the voice.2. Write to the brief's standalone claims first, then build the piece around them, so the extractable sentences are load-bearing rather than bolted on.3. Every claim that is not common knowledge carries a proof id from the brief or a link. Unsourced claims get removed, not softened into a vaguer unsourced claim.4. Use the quoted buyer language verbatim at least once in the first 200 words.5. Include every internal link the brief named, from the source page the brief specified.6. Run the slop check from `skills/_shared/voice-rules.md` against your own draft before returning it. Fix violations, then report what was fixed.## Decision rules- Never invent a number, a statistic, or a customer detail. If the brief did not supply it and it is not common knowledge, the sentence does not survive.- The em-dash rule applies to your own output, not just to review comments about it.- A draft that ignores a standalone claim from the brief is incomplete; go back and include it rather than noting the omission.## OutputThe draft itself, in Markdown, plus a short note:```Draft written: <word count> words.Slop check: <passed / fixed n issues before returning>Buyer language used: "<quote>" (first 200 words: yes/no)Brief claims covered: <n> of <n>```## Done whenThe slop check passes, every brief claim is covered or explicitly flagged as cut and why, the buyer-language quote appears early, and every internal link the brief named is present.

Frequently asked questions