\r \r

GEO Template Library\r

\r A template-focused skill that provides ready-to-use, GEO-aware content templates for common\r high-citation formats. It lowers the barrier to using authoring skills like geo-citation-writer by\r providing battle-tested skeletons that teams can fill in quickly and reuse across products, markets,\r and languages.\r \r This skill focuses on:\r \r

• Defining a catalog of template types and when to use each\r
• Providing clear, copy-pasteable scaffolds in markdown\r
• Highlighting GEO-critical fields that should be filled carefully\r
• Making templates consistent across teams while still flexible\r \r The skill does not replace content-writing or optimization skills. It prepares the canvas so\r other skills (like geo-citation-writer, geo-content-optimizer, geo-structured-writer) can work\r on top of a solid structure.\r \r At a glance, the main template families covered are:\r \r
• Definition article – "What is X?" style pages\r
• FAQ page – focused question-and-answer collections\r
• Comparison guide – A vs B vs C style breakdowns\r
• How-to / tutorial – step-based guides and playbooks\r
• Statistics roundup – "X statistics in YEAR" or benchmark collections\r
• Product / feature page – product detail and solution pages\r
• GEO blog / deep-dive – longer-form educational or thought-leadership pieces\r \r ---\r \r

When to use this skill\r

\r Invoke this skill whenever:\r \r

• The user asks for a template, blueprint, or content skeleton for:\r
  • FAQ pages (FAQPage-style content)\r
  • Definition / "What is X?" articles\r
  • Comparison guides (A vs B vs C)\r
  • How-to / step-by-step guides\r
  • Original data / statistics roundups\r
  • Product or feature landing pages\r
  • GEO-ready blog posts or documentation sections\r
• The user wants to standardize how their org writes certain page types:\r
  • Cross-team content playbooks\r
  • Brand-wide GEO templates stored in a knowledge base\r
• The user mentions:\r
  • "We keep rebuilding similar pages; can we standardize?"\r
  • "Give me a template that our team can reuse"\r
  • "We want AI engines to cite our FAQ / guide / comparison page"\r \r Do not restrict triggering only to these phrases. Trigger whenever the intent is:\r “Give me a reusable, GEO-aware content template for this scenario.”\r \r If the user only wants one-off copy (not a template), other skills may be a better fit, but you\r can still output a template and then show how to fill it once.\r \r ---\r \r

Relationship to other GEO skills\r

\r When available, this skill should cooperate with other GEO skills:\r \r

• geo-citation-writer: uses the templates as starting points for high-citation content\r
• geo-content-optimizer: optimizes filled-in templates for GEO performance\r
• geo-structured-writer: enriches templates with additional structure where needed\r
• geo-schema-gen: maps templates to Schema.org types and JSON-LD scaffolds\r
• geo-llms-txt: uses finished pages built from templates in AI-facing index structures\r \r If these skills are not present, still:\r \r
• Provide high-quality templates\r
• Clearly mark which sections are most important for AI citation\r
• Offer suggestions for how a human can fill and refine them manually\r \r ---\r \r

High-level workflow\r

\r Whenever this skill is used, follow this workflow, unless the user explicitly asks for a subset:\r \r

1. Clarify the scenario and constraints\r
2. Select the best-matching template type(s)\r
3. Generate one or more templates with GEO-focused annotations\r
4. Show example filled-in snippets (optional but recommended)\r
5. Provide usage notes and team guidelines\r \r

1. Clarify scenario and constraints\r

\r Briefly capture:\r \r

• Content goal:\r
  • e.g., "FAQ page for B2B SaaS pricing", "What is zero-shot learning?", "Compare our product vs X"\r
• Primary audience and expertise level:\r
  • Beginner, practitioner, executive, technical buyer, etc.\r
• Channel / surface:\r
  • Main website, docs, blog, knowledge base, product page, landing page, etc.\r
• AI / GEO priorities:\r
  • Become default answer for a query\r
  • Clarify entity definition\r
  • Provide trusted statistics or benchmarks\r \r Output a short ## Scenario Summary section (5–8 bullets) so the chosen template is clearly framed.\r \r

2. Select template type(s)\r

\r Map the scenario to one or more template families. Use the catalog from\r references/templates-catalog.md:\r \r

• Definition article (definition-article)\r
• FAQ page (faq-page)\r
• Comparison guide (comparison-guide)\r
• How-to / tutorial (howto-guide)\r
• Statistics roundup (stats-roundup)\r
• Product / feature page (product-page)\r
• GEO blog / deep-dive (geo-blog)\r \r In the answer, output a brief ## Template Selection section that:\r \r
• Names the chosen template type(s)\r
• Explains why they fit this scenario\r
• Mentions any secondary templates that might also be useful later\r \r If the scenario is ambiguous, pick the closest template type and adapt it, explaining your choice.\r When it is clearly helpful, you may also return multiple templates (for example, a product-page\r template plus an embedded faq-page template).\r \r

3. Generate templates with GEO annotations\r

\r For each selected template type:\r \r

• Output a markdown template that:\r
  • Uses clear headings and subheadings\r
  • Includes placeholder fields in square brackets (e.g., [Product Name], [Key Definition])\r
  • Marks GEO-critical sections using inline comments like:\r
    • \x3C!-- GEO: concise definition, 2–3 sentences -->\r
    • \x3C!-- GEO: high-confidence facts AI can quote safely -->\r
  • Is easy to copy into a doc, CMS, or another tool\r
• Keep the template reasonably compact but complete enough to avoid guesswork.\r \r Example structure (for a definition article template):\r \r

# [Primary Topic]: Clear, Entity-Focused Title\r
\x3C!-- GEO: Include the main entity name exactly as you want AI to use it. -->\r
\r
## Summary\r
- [1–3 bullet points summarizing what this topic is and why it matters]\r
\x3C!-- GEO: Make these bullets fact-focused and quoteable. -->\r
\r
## What is [Primary Topic]?\r
[1–3 concise paragraphs with a clear definition]\r
\x3C!-- GEO: This is the core definition models will likely cite. -->\r
\r
## Key Concepts and Components\r
- [Concept 1]: [Short explanation]\r
- [Concept 2]: [Short explanation]\r
\r
## Examples\r
- Example 1: [Short, concrete example]\r
- Example 2: [Short, concrete example]\r
\r
## How [Your Brand / Product] Relates\r
[Explain how your brand/product interacts with or supports this topic]\r
\r
## FAQ\r
Q1: [Common question]\r
A1: [Clear, factual answer]\r
\r
Q2: [Common question]\r
A2: [Clear, factual answer]\r
```\r
\r
When generating templates, **do not pre-fill** brand-specific content unless the user provides it.\r
Instead, use neutral placeholders and short instructions.\r
\r
### 4. Provide sample filled-in snippets (optional but helpful)\r
\r
If the user wants extra guidance or explicitly asks for **examples**, provide:\r
\r
- One or two **short, filled-in snippets** for key sections, such as:\r
  - Definition paragraph\r
  - One FAQ entry\r
  - One row of a comparison table\r
\r
Make these:\r
\r
- Concrete, but clearly labeled as **examples**, not generic boilerplate\r
- Safe to copy as inspiration, but easy to adapt\r
\r
Output these under `## Example Filled Sections` and clearly indicate which template they belong to.\r
\r
### 5. Usage notes and team guidelines\r
\r
Close with a `## Implementation & Team Guidelines` section that gives:\r
\r
- Tips for **keeping templates consistent** across teams:\r
  - Where to store them (docs, wiki, knowledge base)\r
  - How to version and update them\r
- Advice for **using templates with other GEO skills**:\r
  - "After filling this template, run it through `geo-citation-writer` for refinement"\r
  - "Use `geo-schema-gen` to mirror this structure in JSON-LD"\r
- Reminders about **AI-citable content**:\r
  - Prioritize factual, verifiable statements\r
  - Avoid over-claiming or vague marketing language in GEO-critical sections\r
\r
---\r
\r
## Output format\r
\r
Unless the user requests a different format, structure responses as:\r
\r
1. `## Scenario Summary`\r
2. `## Template Selection`\r
3. `## Templates`\r
4. `## Example Filled Sections` (if applicable)\r
5. `## Implementation & Team Guidelines`\r
\r
Within `## Templates`, include one or more clearly labeled subheadings:\r
\r
- `### [Template Type Name] Template`\r
- Under each, output a complete markdown template.\r
\r
Use:\r
\r
- Markdown headings\r
- Bullet lists\r
- Short comments explaining GEO-significant parts\r
\r
If the user only asks for a **single template**, still keep this top-level structure, but it is fine\r
to keep the unused sections very short (e.g., “Not requested for this use case.”).\r
\r
---\r
\r
## Example triggering prompts (for reference)\r
\r
These are **internal examples** to clarify when this skill should trigger:\r
\r
- "Give me a reusable template for a GEO-optimized FAQ page about our B2B SaaS product."\r
- "I want a standard 'What is X?' article template that our content team can reuse across topics."\r
- "We keep writing comparison pages like 'Product A vs Product B'. Can you give us a robust template\r
  that AI models will love to cite?"\r
- "Design a set of templates for stats roundups and data summary posts that are easy for LLMs to\r
  reference."\r
\r
You do **not** need to surface this list directly to the user; it simply refines intent.\r
\r
---\r
\r