agentleFS
ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/opportunities/SKILL.md

opportunities

Skill432 starsChanged 12 days agoMITView on GitHub

Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only these, for the chat's brand and the topic the person names:

    line 17
  2. Very specific:

    Use list_brands only when no brand is selected, and open_page to link Content Opportunities.

    line 26
  3. Distinctive:

    When the request doesn't say, ask whether to look at the brand's own site, off-site sources, or both.

    line 32
  4. Distinctive:

    Never add prompts without the tool that does it, and the app asks the person first.

    line 50
  5. Distinctive:

    Never promise rankings or citations.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Find opportunities

The playbook of the /opportunities shortcut ("Find content opportunities for …"): where the brand could be cited and isn't yet, on its own site and off it.

Data plan

Read only these, for the chat's brand and the topic the person names:

  1. list_content_opportunities: the prompts where the brand loses visibility, and the page that would win them.
  2. list_citations: the domains and pages AI cites, and which of them cite competitors but not the brand.
  3. get_competitor_comparison: who wins the prompts the brand loses.
  4. get_fanouts: searches the engines run that no tracked prompt covers.
  5. list_prompt_suggestions and get_prompt_insights: prompts worth tracking, with their demand.
  6. get_gsc_summary, when Search Console is connected.

Use list_brands only when no brand is selected, and open_page to link Content Opportunities.

Scope: the last 30 days, every platform the plan tracks.

Questions

  • When the request doesn't say, ask whether to look at the brand's own site, off-site sources, or both.

Steps

  1. On the site: the opportunities with the highest score, each with the page to write or update.
  2. Off the site: the domains AI cites for competitors and not for the brand (Reddit, directories, publishers), with what each would need.
  3. Prompts to track: the fan-outs and suggestions with the most demand that aren't tracked yet.

Output

A table: Opportunity, Where (site or off-site), Why (the prompts and engines), Next step.

Next moves

Two or three, such as "Create content for #1" or "Track these prompts".

Don't

  • Never add prompts without the tool that does it, and the app asks the person first.
  • Never promise rankings or citations.

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.