seo-aeo-meta-description-generator
Writes 3 title tag variants and 3 meta description variants per page with SERP preview, OG tags, and Twitter Card tags. Activate when the user wants to write meta tags, title tags, or social sharing tags for any page.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- seo-aeo-meta-description-generator
- risk
- safe
- source
- community
- date_added
- 2026-04-01
- description
- Writes 3 title tag variants and 3 meta description variants per page with SERP preview, OG tags, and Twitter Card tags. Activate when the user wants to write meta tags, title tags, or social sharing tags for any page.
03 SKILL.md 正文
SEO-AEO Meta Description Generator
Overview
Produces 3 title tag variants and 3 meta description variants for any page, each using a different CTR mechanic (benefit lead, question hook, social proof). Also generates Open Graph and Twitter Card tags. Includes a SERP preview block and a variant comparison table with a recommended selection.
Part of the SEO-AEO Engine.
When to Use This Skill
- Use when a page needs a title tag and meta description written or optimised
- Use when preparing social sharing tags for LinkedIn, X, or WhatsApp
- Use when A/B testing CTR on search results
- Use after the landing-page-writer or blog-writer skill completes
How It Works
Step 1: Identify CTR Angle Per Variant
- V1 Benefit Lead — leads with the outcome or benefit
- V2 Question Hook — opens with the question the searcher is asking
- V3 Social Proof / Specificity — leads with a number, stat, or specific claim
Step 2: Apply Character Limits
- Title tag: 50–60 characters (hard limit: 60)
- Meta description: 140–155 characters (hard limit: 160)
- Never end a description mid-sentence near the limit
Step 3: Apply CTR Rules
- Primary keyword in first 3 words of every title variant
- Primary keyword in first half of every description variant
- At least one power word per description
- Every description ends with a CTA verb
- Never use "click here", passive openers, or all-caps
Step 4: Write Social Tags
OG and Twitter tags can be more conversational than SERP tags. Write them as distinct copy — not copy-pastes of the meta description.
Examples
Example 1: Landing Page Variants
Title V1: Remote Project Management Software | Syncro (51 chars) — Keyword first, brand at end Title V2: Manage Remote Teams Without the Chaos | Syncro (54 chars) — Pain-point led with power word Description V1 (Benefit Lead): Ship faster with your distributed team. Syncro centralises tasks, async updates, and sprints in one tool. Start free today. (141 chars) ✅ Description V2 (Question Hook): Struggling to keep your remote team aligned? Syncro replaces scattered tools with one async-first workspace. Try it free. (140 chars) ✅
Best Practices
- ✅ Do: Write 3 variants — always give the user options to test
- ✅ Do: Keep OG and Twitter descriptions more conversational than SERP versions
- ✅ Do: Verify character count on every variant before outputting
- ❌ Don't: Use the same exact-match anchor or keyword more than once per description
- ❌ Don't: Copy-paste the meta description into the OG description
- ❌ Don't: Let any description end mid-sentence near the character limit
Common Pitfalls
-
Problem: Description truncates mid-word in search results Solution: Always trim a clause rather than letting natural truncation cut the sentence.
-
Problem: All 3 variants sound identical Solution: Each variant must use a genuinely different CTR mechanic — not just rearranged words.
Related Skills
@seo-aeo-landing-page-writer— provides the page content this skill writes tags for@seo-aeo-content-quality-auditor— verifies meta elements as part of the full audit
Additional Resources
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.