agentleFS
UXMagicaiUXMagicai/seosorted-skills/skills/ai-citation-outreach/SKILL.md

ai-citation-outreach

Skill0 starsChanged 41 days agoMITView on GitHub

Find the websites that AI answer engines (Google AI Overviews, ChatGPT, Claude, Perplexity, Gemini) cite for the user's buyer questions, and build an outreach list with contacts to earn a mention there. Use when the user asks how to get mentioned by ChatGPT or AI Overviews, wants listicle or PR outreach targets, link-building prospects from AI citations, or "who should we pitch".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Read the result: sites ranked by how many prompts cite them (topical authority), the exact passage each engine quoted, and contacts.

    line 14

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI citation outreach

AI engines answer buyer questions by quoting a small set of trusted pages. Getting the brand onto those pages is the most direct way to appear in AI answers.

Steps

  1. Choose up to 10 buyer prompts. Use the gap list from ai-visibility-tracker if available; otherwise let the tool write them from the workspace's business context (omit prompts).
  2. find_backlink_prospects with prompts, surfaces (start with ["google_ai_overview"]; add chat_gpt, perplexity, claude, gemini to compare), country: "auto", max_prospects: 10–25.
  3. Read the result: sites ranked by how many prompts cite them (topical authority), the exact passage each engine quoted, and contacts.
  4. For the top 5–10 sites draft one specific pitch each:
    • Reference the exact cited page and what it is trusted for (the quoted passage).
    • Offer something the page lacks: fresher data, a missing option, an expert quote, a correction.
    • One short email; no mass templates.

Output

The prospect table (site, prompts, cited page, quote, contact), then the drafted pitches. Platforms nobody can pitch (Reddit, YouTube, review sites) are a format signal: engines want a thread, a video or a listing there — say which.

Guardrails

Contacts come from public pages. Do not guess email addresses. Draft emails for the user to send; never send outreach on their behalf without explicit instruction.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.