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

aeo-answer-optimizer

Use this skill when you want your brand recommended and cited by AI assistants and answer engines (ChatGPT, Claude, Gemini, Perplexity, AI Overviews): "answer engine optimisation", "get cited by ChatGPT", "AEO audit", "why doesn't AI recommend us", "generative engine optimization". Finds the questions buyers ask assistants in your category, checks how answers describe you today, and rewrites pages so they give extractable, factual, well-structured answers with clear entities, comparisons, schema and third-party corroboration.

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

prosyo-ai/gtm-skill스타 11(GitHub 11 + cccskills 0)
연동 도구Gemini

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

  • SKILL.md4.2 KB
  • references/aeo-checklist.md1.9 KB

SKILL.md(원문)

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

Use this when buyers ask AI assistants which tool to use and your brand is missing or described wrongly. AI answers favour sources that state facts clearly, answer the question directly and are confirmed by other sources.

Inputs

  • The category, product and the facts that define it (who it is for, pricing model, key capabilities, integrations).
  • The pages that should be cited: home, product, pricing, comparisons, docs.
  • The questions buyers ask (from sales calls, search and support).

The play

1. Map the questions

Group buyer questions by type: "what is", "best tools for", "x vs y", "how to", "how much does", "is x good for <use case>". Prioritise commercial questions where a recommendation is made.

2. Audit current answers

Ask several assistants the top questions. Record whether you are mentioned, what is said, which sources are cited and what is wrong or outdated. Repeat monthly; answers change.

3. Rewrite pages for extraction

Read references/aeo-checklist.md for the page-level checklist. The core:

  • Lead each section with a direct, one or two sentence answer, then the detail.
  • State facts plainly and consistently across pages: what it is, who it is for, price, limits.
  • Use comparison tables with clear criteria; assistants reuse tables well.
  • Name entities precisely: product names, categories, integrations, use cases.
  • Keep facts fresh and dated where they change.

4. Make it machine-readable

Organization, Product or SoftwareApplication, FAQPage and Article schema; a clean sitemap; fast, crawlable HTML (key text not hidden behind scripts); an llms.txt summary with links to the most important pages; and no blocking of the AI crawlers you want to be cited by.

5. Build corroboration

Assistants trust facts confirmed elsewhere: review sites, directories, partner pages, community answers, credible articles. Make sure third-party descriptions match your own.

Output format

Question map: <question - type - priority - currently mentioned? - cited sources>
Wrong or missing facts: <...>
Page fixes: <page - change - why>
Schema and technical: <...>
Corroboration targets: <sources to update or earn>
Re-check: <date and questions to re-run>

What good looks like

  • One consistent fact sheet about the product, reused everywhere.
  • Comparison and "best for" pages that are honest about fit; assistants pick up balanced sources.
  • Progress measured by mentions and citations on the priority questions, checked monthly.
  • The common mistake is writing for keywords alone, with answers buried in paragraph four of a long intro.

Rules

  • MUST keep every claim accurate and consistent across pages.
  • MUST measure with repeatable question sets over time, not one-off screenshots.
  • NEVER publish fake reviews, fake third-party pages or hidden text aimed at AI crawlers.
  • NEVER make claims about competitors you cannot support.

Example prompts

  • "Audit how AI assistants describe us for 'best AI SDR tools' and fix our pages."
  • "Rewrite our pricing page so answer engines quote it correctly."
  • "Build a monthly AEO tracking sheet for our 20 most important buyer questions."

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Use this skill when you run account-based marketing or sales on a short list of named accounts: "build an ABM plan", "account plan for our top 20", "how do we break into this enterprise account", "1:1 ABM program". Picks the accounts and the ABM tier (1:1, 1:few, 1:many), maps the buying group, writes the account insight and value hypothesis, plans coordinated sales and marketing plays by stage, and sets the metrics (engagement, meetings, pipeline) that show it is working.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

Use this skill when you need to research a target company before outreach, a first call or an account plan: "research this account", "what should I know about Acme before the call", "find a reason to reach out". Produces a one-page account brief with what the company does, current priorities, recent trigger events, likely pains tied to your offer, the people to contact and three specific outreach angles, each with its source. Built for SDRs, AEs and founders doing B2B sales.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

Use this skill when you need to decide which accounts get the most effort: "tier my account list", "which accounts should get 1:1 research", "prioritise my territory", "score these companies". Scores every account on ICP fit and timing, assigns Tier 1, 2 or 3 with a clear effort level for each tier, and explains the score so reps trust it. Produces a tiered account list and the operating rules for how much research, personalization and channel effort each tier gets.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

Use this skill when you want to close the loop with a prospect who has not replied after several touches, or a deal that went silent: "write a breakup email", "last email in the sequence", "close the loop politely". Writes a short, gracious final email that gives an easy out, invites a one-word reply, leaves the door open for later and often gets more replies than any earlier step. Includes versions for cold sequences, stalled deals and lost champions.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

Use this skill when you need B2B buyer personas that sales and marketing will actually use: before writing outreach to a new title, when messaging feels generic, or when a deal stalls because the wrong person is engaged. Builds a persona per role in the buying committee with goals, pains in their own words, what they are measured on, objections, trusted sources and the message angle that works, plus a do-not-say list. Covers economic buyers, champions, users and blockers.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

Use this skill when a B2B deal or target account needs more than one contact: "who else should I talk to", "map the buying committee", "multi-thread this deal", or a single-threaded deal is at risk. Maps the economic buyer, champion, influencers, users, technical evaluator and blockers, names the likely people and titles, scores coverage and sentiment, and produces a multi-threading plan with what each person needs to hear and who should reach them.

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

prosyo-ai/gtm-skill112026년 10월 23일 업데이트

prosyo-ai의 스킬 모두 보기

이 스킬의 문제 신고