본문으로 건너뛰기
cccskills
무료GitHub에 공개

aeo

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Gemini
설치 방법 보기

포함된 파일(2)

  • SKILL.md9.8 KB
  • source.json1.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Answer Engine Optimization (AEO)

Get your content cited by ChatGPT, Perplexity, Claude, Gemini, and Mistral as the authoritative source.

AEO is the practice of optimizing content for citation in LLM-generated responses — distinct from SEO, which optimizes for search rankings. This skill audits, optimizes, and tracks AEO performance.

Distinct From SEO

SEOAEO
Optimizes forClick-through rankingsBeing cited as authoritative source
AudienceHumans browsing search resultsLLMs answering questions
Success metricPosition 1-10, organic trafficCitation count across LLMs
Key signalsBacklinks, keywords, page speedE-E-A-T, structured data, factual density
Update cadenceWeeks-to-monthsDays-to-weeks (LLM training cycles)

Both can coexist — the same content can rank #1 on Google AND get cited by Perplexity. But the techniques differ: SEO rewards keyword density + backlinks; AEO rewards primary-source signals + structured facts.

When To Use

  • Planning a new content piece for an AI-first audience
  • Auditing existing content for E-E-A-T gaps before AI Overview rollout
  • Tracking which pages get cited by which LLM (citation ledger)
  • Researching what queries LLMs cite sources for (vs. what they answer from training)
  • Benchmarking against competitors' citation rates
  • Building a long-term AEO strategy aligned with traditional SEO

When NOT To Use

  • Pure click-through SEO without LLM-citation intent — use marketing-skill/skills/seo-audit instead
  • Brand-voice content with no factual claims — citations require facts to cite
  • Content for a topic where LLMs already have strong training signal (e.g., elementary math) — citation upside is minimal
  • Time-sensitive content (breaking news) — LLM training lag means citations come months later

Core Capabilities

1. Content audit + E-E-A-T scoring

The auditor (aeo_audit.py) scores content across 4 dimensions:

  • Experience: First-person evidence, dated examples, case studies, "We ran X in 2026" claims
  • Expertise: Author bio, credentials, citations to peer-reviewed sources, technical depth
  • Authoritativeness: External backlinks from authority domains, schema.org markup, structured data
  • Trustworthiness: HTTPS, contact info, transparent corrections, factual density (number of verifiable claims per 1000 words)

Composite score 0-100 with per-dimension breakdown. Output: markdown report with specific fix recommendations.

2. Content optimization

The optimizer (aeo_optimizer.py) generates AEO-improved variants:

  • Structure rewrite — H2/H3 hierarchy optimized for LLM parsing
  • Citation density boost — adds [1]-style references with sources
  • Schema injection — generates JSON-LD for FAQ, HowTo, Article schemas
  • Fact-first lede — moves verifiable claims into the first 200 words

Three modes: conservative (touch <10% of words), balanced (touch <30%), aggressive (rewrite for maximum AEO).

3. Citation tracking

The tracker (citation_tracker.py) maintains a local ledger of citations:

  • Manual entry: paste a citation found in ChatGPT/Perplexity/Claude/Gemini output
  • Track which URL, which LLM, which query, what date
  • Compute per-page citation count, citation velocity, LLM coverage
  • Export to CSV for reporting

Stores in ~/.aeo-data/citations.json (local, no telemetry).

Workflow

1. Audit existing content
   $ python3 scripts/aeo_audit.py --url https://example.com/blog/post
   → markdown report with composite score + 4-dimension breakdown

2. Apply optimization recommendations
   $ python3 scripts/aeo_optimizer.py --input post.md --mode balanced --output post-aeo.md
   → optimized variant with citations + schema + structural fixes

3. Publish + monitor
   $ python3 scripts/citation_tracker.py --action add --url https://example.com/blog/post \
       --llm perplexity --query "what is AEO" --date 2026-05-17
   → adds entry to local citations.json ledger

4. Report
   $ python3 scripts/citation_tracker.py --action report --url https://example.com/blog/post
   → per-page citation stats: count, LLMs, queries, velocity

Configuration

The skill is industry-aware via per-run --industry flag. Supported: saas, healthcare, finance, legal, ecommerce, b2b, media, education.

Industry affects:

  • Authority signal requirements — healthcare/finance need stricter source citations
  • Fact-checking rigor — legal/healthcare flag unverifiable claims as critical
  • Citation style — academic vs. trade-journal vs. blog conventions

Example:

python3 scripts/aeo_audit.py --url <url> --industry healthcare
# → stricter E-E-A-T thresholds; flags any health claim without primary citation

Output Format

Markdown audit report (default)

# AEO Audit Report — [Page Title]

**URL:** https://example.com/blog/post
**Date:** 2026-05-17
**Industry:** saas
**Composite Score:** 72/100 (B+)

## Dimension Breakdown

| Dimension | Score | Verdict |
|---|---|---|
| Experience | 80/100 | Strong — first-person case study present |
| Expertise | 65/100 | Author bio missing credentials |
| Authoritativeness | 75/100 | 4 backlinks from authority domains |
| Trustworthiness | 68/100 | No corrections policy linked |

## Top 3 Fixes

1. Add author bio with credentials (Expertise +15)
2. Link to corrections policy from footer (Trustworthiness +12)
3. Inject FAQ schema for the 5 questions implicit in H2s (Authoritativeness +8)

## All Recommendations
[...]

## Audit Trail
[3-count of analysis steps, sources cited, time taken]

JSON for pipelines

python3 scripts/aeo_audit.py --url <url> --output json

Returns full structured data for integration with content management workflows.

Industry-Specific E-E-A-T Thresholds

IndustryMin CompositeCritical Signals
Healthcare85Medical reviewer byline, peer-reviewed citations, FDA disclosure
Finance85Author CFA/CPA credentials, "not investment advice" disclaimer, dated examples
Legal85Jurisdiction disclosed, attorney bio, "not legal advice" disclaimer
SaaS70Product manager byline, case study with metrics, ROI calculator
E-commerce65Product reviews aggregated, return policy, schema.org Product
B2B70Industry analyst quotes, customer logos, ROI data
Media70Editorial policy, fact-check link, original reporting
Education75Instructor bio, learning outcomes, accreditation if applicable

Anti-Patterns Rejected

  • Keyword stuffing for AI — LLMs already extract topic from semantics; keyword density doesn't boost citation likelihood
  • Pure AI-generated content with no human review — generic LLM output gets de-prioritized by RAG retrieval algorithms looking for distinctive signal
  • Citation farms / link wheels — modern LLM RAG penalizes low-authority linked networks
  • Schema spam — false or unverifiable schema.org claims get filtered; only mark up real, verifiable claims
  • Optimizing for one LLM at expense of others — citation distributions are highly correlated across major LLMs because they share training data sources; optimize for the shared signals (E-E-A-T) not per-LLM hacks
  • Ignoring SEO entirely — AEO citations often originate from sources that already rank well organically; AEO and SEO are complements, not substitutes

Dependencies

  • stdlib-only for all 3 scripts — no pip install required
  • Optional: requests + beautifulsoup4 if --url mode used (otherwise pass markdown via --input for file-based audits)
  • Optional: any LLM API key for query_research mode (currently scaffold-only — full LLM-driven query research is roadmap)

Storage

All data is local-first:

  • ~/.aeo-data/citations.json — citation ledger
  • ~/.aeo-data/patterns.json — success patterns library
  • ~/.aeo-data/audits/<hash>.md — saved audit reports

No telemetry. No cloud sync. Export to CSV anytime via citation_tracker.py --action export.

Trigger Phrases

  • "AEO audit", "AEO check"
  • "optimize for ChatGPT / Perplexity / Claude / Gemini"
  • "get cited by [LLM]"
  • "LLM citation strategy"
  • "answer engine optimization"
  • "content for AI search"
  • "E-E-A-T audit"
  • "track AI citations"
  • "schema for AI"

Related Skills

  • marketing-skill/skills/seo-audit — traditional click-through SEO
  • marketing-skill/skills/programmatic-seo — template-driven SEO at scale
  • marketing-skill/skills/content-strategy — broader content planning
  • marketing-skill/skills/copywriting — voice + tone
  • marketing-skill/skills/schema-markup — structured data implementation

Version: 2.7.3 Source: Ported from alirezarezvani/aeo-box (answer-engine-optimization/ skill, 2,464 LOC across 9 modules). This port distills the 9-module Python toolkit into 3 stdlib CLI tools per the claude-skills convention; preserves the E-E-A-T scoring methodology, citation-tracking schema, and industry-aware thresholds verbatim. License: MIT (matches upstream + this repo).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

007

무료

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

10x-team

무료

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

aibot88/sec_skill_store52026년 5월 27일 업데이트

aibot88의 스킬 모두 보기

이 스킬의 문제 신고