Featured Snippet Optimizer

What it does

Looks at the current top-ranking snippet format for a target query (paragraph, list, or table) and rewrites the corresponding section of the user's content to match that format and length while keeping the same factual claims. Does not change content elsewhere on the page.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/featured-snippet-optimizer/ (or ~/.claude/skills/featured-snippet-optimizer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/featured-snippet-optimizer/

OpenAI Codex

.codex/skills/featured-snippet-optimizer/

Cursor

.cursor/skills/featured-snippet-optimizer/ (or ~/.cursor/skills/featured-snippet-optimizer/ globally)

Compatibility

Any WordPress site. No special plugin required; benefits from knowing the current SERP snippet format for the target query, which the user may need to supply or check manually.

The complete SKILL.md for this skill:

---
name: featured-snippet-optimizer
description: Use when a user wants a specific section of a post rewritten to target a Google featured snippet for a given query. Triggers on "featured snippet", "position zero", "snippet optimization", or "why don't we have the snippet".
---

# Featured Snippet Optimizer

## When to use
The user has a target query where a featured snippet exists (or could exist) and wants a section of their existing post reformatted to compete for it, without a full rewrite of the page.

## Procedure
1. Confirm the target query and, if known, the current snippet's format: short paragraph, numbered/bulleted list, or table.
2. Find the section of the post that already answers this query, or the closest existing section.
3. Rewrite just that section to match the winning format, e.g. a direct 40-60 word answer for paragraph snippets, a clean numbered list with parallel phrasing for list snippets, or a simple table with clear row/column headers.
4. Keep every factual claim from the original untouched, this is a format change, not a content change.
5. Show a before/after of just the rewritten section so the user can see exactly what moved.

## Guardrails
- Never alter facts, numbers, or claims while reformatting, if the source content is wrong that's a separate conversation with the user.
- If the current snippet format isn't known, say so and offer the paragraph-style answer as the safest default rather than guessing at a table or list.