diegosouzapw SEO-AEO Meta Description Generator
Overview
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/seo-aeo-meta-description-generator from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
SEO-AEO Meta Description Generator
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Common Pitfalls, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- 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
- Use when the request clearly matches the imported source intent: 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.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Operating Table
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | metadata.json |
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review | ORIGIN.md |
Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | SKILL.md |
Starts with the smallest copied file that materially changes execution |
| Supporting context | SKILL.md |
Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills |
Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
- Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
- Validate the result against the upstream expectations and the evidence you can point to in the copied files.
- Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
- Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: 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.
Imported: 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: Ask for the upstream workflow directly
Use @seo-aeo-meta-description-generator to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @seo-aeo-meta-description-generator against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @seo-aeo-meta-description-generator for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @seo-aeo-meta-description-generator using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: 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
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- ✅ 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
- Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Imported Operating Notes
Imported: 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
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/seo-aeo-meta-description-generator, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant- Use when the work is better handled by that native specialization after this imported skill establishes context.@00-andruia-consultant-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith- Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith-v2- Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|---|---|
references |
copied reference notes, guides, or background material from upstream | references/n/a |
examples |
worked examples or reusable prompts copied from upstream | examples/n/a |
scripts |
upstream helper scripts that change execution or validation | scripts/n/a |
agents |
routing or delegation notes that are genuinely part of the imported package | agents/n/a |
assets |
supporting assets or schemas copied from the source package | assets/n/a |
Imported Reference Notes
Imported: Additional Resources
Imported: 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.
Imported: 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.