Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/seo-aeo-blog-writer
Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation.
Passed 11 of 22 test cases with the skill, and 7 of 22 without it.
and 2 more in the full report
4 fixed7 passed either way11 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a comprehensive blog post explaining how to transition an enterprise team from on-premise infrastructure to AWS cloud. Please draft a detailed guide designed to rank on traditional search engines while remaining easy for generative AI tools to cite. Include a brief upfront summary, structured section headers, actionable steps, and a Q&A section at the bottom for common reader queries.
| Checked | Without skill | With skill |
|---|---|---|
| Includes a blockquote formatted summary placed immediately after the main H1 heading. | Missed | Passed |
| Uses 'What Is' as the first H2 heading. | Missed | Passed |
| Contains exactly 5 FAQ entries in the Q&A section. | Passed | Passed |
The instructions your model reads when the skill loads.
Writes structured long-form blog posts (800–3000 words) that satisfy both SEO ranking signals and AEO citation requirements. Every post includes a TL;DR direct-answer block, a definition sentence, structured H2/H3 hierarchy, a comparison table where relevant, and exactly 5 FAQ entries written for AI extraction.
Part of the SEO-AEO Engine.
Write a 2–3 sentence direct answer to the article's core question. Place it immediately after the H1 in a blockquote. This is the first block AI engines attempt to extract.
Set H1, H2s (4–6), and H3s before writing any body content. The first H2 must be a "What Is" section with a clean definition sentence as its opening line.
Follow the section order: What Is → Why It Matters → How It Works (with H3 sub-concepts) → Practical Steps → Common Mistakes → FAQ → Conclusion.
Use long-tail and secondary keywords as questions. Each answer must be under 50 words and self-contained — readable without any surrounding context.
Verify TL;DR presence, definition sentence, FAQ count, keyword placement, and heading structure before outputting.
How to Manage a Remote Engineering Team
TL;DR: Managing a remote engineering team requires async communication tools, clear documentation standards, and timezone-aware sprint planning. Teams that nail these three
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.