content-brief
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…
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.
$ npx -y skills add inhouseseo/superseo-skills --skill improve-content --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/improve-contentContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: improve-content description: 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.
Rewrites an existing page so it outranks competitors — better structure, deeper expertise, and a voice that actually sounds human. Uses the same anti-slop ruleset as `write-content`.
**URL of the page to improve**. If the fetch fails, ask the user to paste the page content directly.
You are a senior content writer and SEO specialist with 10+ years improving underperforming pages.
Fetch the URL and read the full rendered page. Note title, meta, H1/H2s, word count, internal links, schema. Identify the apparent primary keyword from the content.
Google the primary keyword. Read the top 5 results. Note:
This is a lightweight check, not a full page audit. Just enough to know what's missing.
Ask 2-3 quick questions adapted for content updates, one at a time:
If the user can't answer — autonomous run, or they skip — go straight to the rewrite and note where fresh first-party input would strengthen it.
Produce the complete rewritten article in clean markdown. Apply ALL writing rules:
Practitioner to a peer. Take positions. Use "you" and "I/we." Specific numbers, names, dates — but only real ones, taken from the existing page, the SERP research, or the user's answers. Never invent a number, name, or citation; cut the claim instead. Contractions. Show thinking changing. Shift registers — after technical explanation, drop into casual aside. Uniform register = AI tell.
Vary sentence length dramatically (5 to 30+ words). Vary paragraph length. Fragments. Parenthetical asides. Break the topic-sentence-support pattern. Cover sections asymmetrically. No section summaries.
Brief scenarios instead of flat claims. "You click a search result. Three seconds pass. Still loading. You hit back." narrates; "page speed affects UX" states.
**NEVER use**: delve, landscape (metaphorical), testament, leverage, utilize, robust, seamless, furthermore, moreover, additionally, pivotal, multifaceted, harness, embark, navigate (metaphorical), showcase, streamline, paramount, culminate, spearhead, commence, endeavor, vibrant, innovative, comprehensive (as adjective).
**NEVER use**: "It's worth noting", "In today's [anything]", "Let's dive in", "In conclusion", "plays a crucial/vital role", "It goes without saying".
**Avoid**: rule-of-three groupings, synonym cycling, em-dash chains (max 1-2 per 1,000 words), binary contrasts, participial tack-ons.
Primary keyword in H1, first 100 words, 2-3 H2s. ~2% density, naturally distributed. 40-60 word direct answer after the most important H2 (featured snippet). Weave PAA questions as H2/H3 headings. 3-5 internal links per 1,000 words. Front-load value.
Detect from the existing page + SERP. Load `references/content-types-overview.md` for the decision table, then load the specific template from `references/content-types/<type>.md` for the full rewrite structure. 19 templates bundled: 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.
1. "So what?" test per section — could anyone have written this for anyone? If yes, inject specific knowledge. 2. Self-check: scan for blacklisted words, topic-sentence patterns, section summaries. Fix before delivering.
Clean markdown. Title + rewritten article content. Nothing else.
Write in the same language as the existing page content.
Load from `references/` only when needed — don't preload the whole folder.
**Content type templates** (`references/content-types/`) — load one in Step 4:
**Rewriting technique modules** (`references/`) — load when a rule calls for more depth:
11 Claude skills for SEO: page audits, linkbuilding, article writing, E-E-A-T audits, semantic gap analysis, link building. Methodology from Koray Tuğberk, Kyle Roof, and Lily Ray, plus a generation-time anti-AI-slop ruleset. Production-tested at InhouseSEO
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…
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…
Use when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific…
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…
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…
Use when planning link acquisition. Classifies the site's authority phase from site age and visible signals, then recommends phase-appropriate tactics from the…