seo-glossary

Create SEO-optimized educational articles with decision-oriented voice and structured headings.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/dataroaring/skills --skill seo-glossary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seo-glossary
Source: https://github.com/dataroaring/skills/tree/main/plugins/developer-writing/skills/seo-glossary
Command: npx skills add https://github.com/dataroaring/skills --skill seo-glossary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create search-optimized educational content that ranks well without sounding generic, dry, or purely definition-driven. It is designed for topics like X vs Y comparisons, glossary posts, complete guides, and decision-oriented explainers that need both SEO structure and a strong editorial point of view.

Core Features & Use Cases

  • Opinionated SEO structure: Turns conventional explainer topics into engaging articles with hooks, reframes, trade-offs, and decision frameworks.
  • Comparison-friendly formatting: Uses bullet-based comparison blocks, featured-snippet-friendly headings, and clear section flow for Feishu/Notion compatibility.
  • Developer-focused educational content: Supports technical articles with code examples, quantified claims, architecture diagrams, and product mentions handled in a non-markety way.
  • Use case: A writer needs a complete “X vs Y” article for developers, with SEO metadata, practical guidance, and a confident voice that helps readers decide what to use and when.

Quick Start

Ask the AI to write an SEO-optimized, opinionated glossary or comparison article on your chosen topic using the skill’s structure, voice, and metadata guidelines.

Frequently Asked Questions about seo-glossary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an SEO comparison guide for developers that ranks well?

To write an SEO comparison guide for developers, use structured headings, bullet-based comparison blocks, and featured-snippet-friendly formatting to achieve search visibility and clear decision framing.

How do I create opinionated technical content for glossary posts?

Create opinionated technical content for glossary posts by applying a decision-oriented voice that reframes conventional definitions into engaging articles with hooks, trade-offs, and practical guidance.

What is the best way to structure an X vs Y article for search visibility?

The best way to structure an X vs Y article for search visibility is to use SEO metadata, comparison-friendly bullets, and concise conclusions tailored for content discovery while maintaining a strong editorial point of view.

Can I generate SEO metadata and code examples together for developer content?

Yes, you can generate SEO metadata and code examples together for developer content. This approach supports technical articles with quantified claims, architecture diagrams, and non-markety product mentions.

Why does my comparison guide sound generic and how can I fix it?

Your comparison guide sounds generic because it lacks a strong editorial point of view. Fix this by applying an opinionated structure that turns conventional explainers into decision-oriented articles with confident framing.

When do I need an opinionated structure for SEO writing?

You need an opinionated structure for SEO writing when creating decision-oriented explainers, complete technical guides, and X vs Y comparisons that require both search visibility and a strong editorial voice.