answer-engine-content
Skill1 starsChanged 3 months agoMITView on GitHub
Create answer-engine and AI-search friendly content briefs for GEO, LLM citations, ChatGPT visibility, Perplexity visibility, Gemini/Copilot answers, comparison pages, factual guides, landing pages, reports, and FAQ content. Use when the user mentions generative engine optimization, answer engine optimization, AI search content, content that should be cited by AI assistants, competitor comparison pages, source-backed articles, or fact-checking for search visibility. Outputs target query, page type, short answer, source table, outline, FAQ, fact-check notes, and publish-readiness status.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- try-era/geo-skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- try-era/geo-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to create content that is easy for answer engines and AI assistants to parse, verify, and cite.
- Distinctive: line 25
Write the likely user questions the page should answer.
- Distinctive: line 26
Keep each page focused on one search intent.
- Distinctive: line 41
Avoid hype, vague claims, and unsupported superlatives.
- Distinctive: line 42
Do not attack competitors.
- Distinctive: line 43
Use exact definitions and dates when the topic changes over time.
- Distinctive: line 46
Verify every data point before publishing.
- Distinctive: line 47
Check competitor claims against official pages.
- Distinctive: line 79
No vague "best" claims without criteria.
- Distinctive: line 80
No invented competitor details.
- Distinctive: line 81
Every comparison row needs a source or a clear "unknown" label.
- Distinctive: line 82
Update dates when facts are time-sensitive.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Answer Engine Content
Use this skill to create content that is easy for answer engines and AI assistants to parse, verify, and cite.
This skill writes a citation-friendly brief from best-practice structure and your own source material. It does not check what AI engines are actually citing right now for your topic. If you want the brief grounded in real citation data instead of assumptions, run geo-citation-scout first, it queries Perplexity/ChatGPT/Google AI Overview with your real buyer questions, finds out who is winning each one, and can hand you back a content brief for each confirmed gap. Use this skill on its own when you already know the topic and just need a fast, well-structured draft without doing that research first.
Inputs
- Topic
- Target audience
- Page type: factual guide, comparison page, landing page, FAQ, or report
- Source URLs or data files
- Competitors or alternatives, if relevant
Workflow
- Define the query
- Write the likely user questions the page should answer.
- Keep each page focused on one search intent.
- Build a source table
- List each factual claim.
- Attach the source URL, access date, and note.
- Separate first-party claims from third-party facts.
- Structure for citation
- Short answer at the top.
- Clear headings.
- Concise paragraphs.
- Tables for comparisons.
- FAQ at the end.
- Write neutrally
- Avoid hype, vague claims, and unsupported superlatives.
- Do not attack competitors.
- Use exact definitions and dates when the topic changes over time.
- Fact-check
- Verify every data point before publishing.
- Check competitor claims against official pages.
- Mark stale or uncertain facts.
Output Format
Target query:
Page type:
Audience:
Short answer:
Source table:
| Claim | Source | Access date | Notes |
|---|---|---|---|
Outline:
1.
2.
3.
FAQ:
1.
2.
3.
Fact-check notes:
Publish readiness:Quality Gates
- No unsupported statistics.
- No vague "best" claims without criteria.
- No invented competitor details.
- Every comparison row needs a source or a clear "unknown" label.
- Update dates when facts are time-sensitive.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.