From aaron-seo-geo
Optimize title tags, meta descriptions, Open Graph, Twitter cards for maximum CTR with A/B variations. 标题优化/元描述/CTR
How this skill is triggered — by the user, by Claude, or both
Slash command
/aaron-seo-geo:meta-tags-optimizer <page URL or content>When to use
Use when optimizing title tags, meta descriptions, Open Graph tags, or Twitter Cards for a page.
<page URL or content>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Creates title tags, meta descriptions, and social meta tags that improve CTR and sharing quality.
Creates title tags, meta descriptions, and social meta tags that improve CTR and sharing quality.
Create meta tags for a page about [topic] targeting [keyword]
Improve these meta tags for better CTR: [current tags]
Expected output: a ready-to-use metadata package plus the standard handoff summary for memory/content/.
memory/hot-cache.md, memory/decisions.md, and memory/open-loops.md.Emit the standard shape from skill-contract.md §Handoff Summary Format.
Optional search console and SEO tool integrations pull CTR data and competitor patterns automatically; otherwise ask for current tags, keywords, and competitors. See CONNECTORS.md.
When a user requests meta-tag optimization, run these six steps:
Reference: See references/instructions-detail.md for the compact workflow, formulas, alignment matrix, CTR analysis, and example. See references/meta-tag-code-templates.md for HTML blocks.
Sample outcome: a 55-character title, a 150-160 character description, and a complete OG / Twitter / Article tag block. See the full worked sample in references/instructions-detail.md.
Front-load keywords, match intent, be specific, test variations, and refresh tags when the SERP changes.
On user confirmation, save memory/content/YYYY-MM-DD-<topic>.md and promote key conclusions to memory/hot-cache.md.
npx claudepluginhub mobilekunden/seo-geo-claude-skillsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.