write-content
Use when writing a complete SEO article. Includes the full anti-AI-slop ruleset (banned vocabulary, banned phrases, banned structural patterns) and voice rules. The agent researches the SERP itself if needed — no keyword data exports required.
git clone --depth 1 https://github.com/inhouseseo/superseo-skills /tmp/write-content && cp -r /tmp/write-content/skills/write-content ~/.claude/skills/write-contentSKILL.md
# Write Content Writes a complete SEO-optimized article. Four phases: research → content type decision → knowledge extraction → write. Includes the full anti-AI-slop ruleset and the voice rules that make the output sound like a practitioner, not a press release. ## Input - **Topic or target keyword** (required) - *(Optional)* An existing content brief — skip the research phase if provided - *(Optional)* Expert interview output from the `expert-interview` skill If no topic is given, ask for one before proceeding. ## Business context persistence Business context (audience, tone, language, brand voice, examples) shapes every article. Don't re-ask these questions every session. **First use**: ask 4-5 questions and save the answers somewhere persistent in your agent's environment. Use the safest default first: - **Claude Code**: `~/.claude/projects/<path>/memory/business-context.md` is the recommended default. Do NOT write to `./CLAUDE.md` unless the user explicitly asks for it — `CLAUDE.md` is the user's project instructions file and appending unsolicited content to it can surprise them on every subsequent agent turn. - **Claude Desktop / Claude.ai**: save to a Project's context or a pinned note. - **Cursor**: `.cursor/rules/business-context.md`. - **Any other agent**: `seo-context.md` in the working directory. Always confirm the write location with the user before saving. If any of these are unavailable or the user objects, fall back to re-asking the questions each session. **Every use after that**: load that file first. If missing, ask where the user saved it or re-ask the questions. Questions on first use: - What does the business do, and who is it for? - What's the brand's tone of voice? (Professional / Casual / Technical / Authoritative / Conversational) - What language should content be written in? - What topics should NEVER appear? (compliance, competitor mentions, etc.) - Who are the 2-3 main competitors? ## Phase 1: Research If a content brief wasn't provided, Google the topic and read the top 5 results. Note: what formats are ranking, what angles exist, what gaps you see. 3-5 bullet points, not a full brief. Skip this phase entirely if a brief or prior conversation context already contains SERP analysis. ## Phase 2: Content Type Decision Based on what's ranking, pick a content type: how-to, definition/explainer, comparison (X vs Y), listicle/roundup, product review, case study, pillar/ultimate guide, FAQ, landing page, service page, news/trend analysis. State it plainly: "The top results for [keyword] are all [format]. I'll write a [content type] with [key structural element]. Sound good, or did you have something else in mind?" Wait for confirmation. Load `references/content-types-overview.md` for the decision table covering all 23 content types. Then load the specific template from `references/content-types/<type>.md` (e.g., `references/content-types/how-to.md`) for H1/H2 structure, schema, featured snippet format, CTA placement, word count targets. The 19 content types bundled as full templates: how-to, definition, comparison, listicle, pillar-page, faq-page, landing-page, service-page, case-study, statistics-page, news-article, glossary-page, alternatives-page, buying-guide, product-page, category-page, integration-page, location-page, programmatic-page. For the 4 types covered only by the overview table (thought-leadership, product-reviews, pricing-pages, about-pages), those live under `eeat-audit/references/content-types/` because the E-E-A-T bar for them is the load-bearing factor. ## Phase 3: Knowledge Extraction Ask 2-3 quick questions to extract unique knowledge the user has. Pick from: - "What do most people get wrong about [topic]?" - "Can you give me a specific example — a client, a project, a number?" - "What surprised you when you actually did this?" - "Who should NOT follow this advice, and why?" Ask one at a time. Keep it quick. **Adapt style**: - Newer/smaller site, less SEO-savvy user: conversational, explain why each question matters - Established site, experienced user: fast, direct, no hand-holding ## Phase 4: Write the Article **Length**: Do not target a specific word count. Match the depth of top-ranking content from Phase 1. Length follows intent and competition — never pad to hit a number. Produce the complete article in clean markdown. Follow ALL of these rules: ### Voice and Stance - Write like a practitioner talking to a peer. Not a textbook, not a press release. - Take clear positions. "We tested this and X works better than Y" beats "both X and Y have merits." - Use "you" and "I/we" — write to one person, not an audience. - Include specific numbers, names, dates. Never "many companies" — always "[Company] in [year]." - Weave in interview answers as first-person experience. Preserve phrasing where it sounds natural. - Use contractions: "doesn't" not "does not." - Show thinking changing: "At first I thought this was a branding problem — turns out it was pricing all along." Self-correction is a human signal. - Anchor in real context — reference current events, industry shifts, or cultural touchstones where relevant. ### Rhythm and Structure - Vary sentence length dramatically. Mix 5-word punches with 30-word complexes. Never 3+ consecutive sentences of similar length. - Vary paragraph length. One-sentence paragraphs are fine. So are 6-sentence ones. - Use fragments for emphasis. Start sentences with "And" or "But" when natural. - Include parenthetical asides and brief tangents — humans do this, AI doesn't. - Shift registers. After a technical explanation, drop into a casual aside. Uniform register = AI tell. - Break the topic-sentence-support pattern. Start some paragraphs with an example, a question, or a statement that only makes sense after reading on. - Cover sections asymmetrically. Spend 500 words on the interesting part and 50 on the boring-but-necessary one. - Don't summarize at the end of sections unless genuinely c
Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required.
Use when auditing a page for E-E-A-T signals. The agent reads the page and scores Experience, Expertise, Authoritativeness, and Trustworthiness — then tells you exactly what to add to each dimension.
Use when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific examples, and surprising outcomes that AI can't fabricate.
Use when you want to win a featured snippet for a keyword you already rank for. The agent checks the current snippet format, analyzes your content, and rewrites the relevant section to match what Google wants.
Use when rewriting or refreshing an existing page that's underperforming. The agent fetches the URL, analyzes the current content, researches the SERP, and rewrites using the full anti-AI-slop ruleset — no data exports needed.
Use when planning to rank for a specific keyword. The agent Googles it, reads the top 10, classifies intent, reads the top 3 competitor pages, and produces a 90-day ranking plan with intent, SERP analysis, and content recommendations.
Use when planning link acquisition. Classifies the site's authority phase from site age and visible signals, then recommends phase-appropriate tactics from the bundled tactic playbook library. No backlink tool required.
Use when auditing a specific page's SEO performance, content quality, and competitive position. The agent fetches the URL, Googles the primary keyword, reads the top 3 competitors, and produces a full 7-dimension audit — no exports, no analytics access required.