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

features

Skill432 starsChanged 11 days agoMITView on GitHub

How AI describes you against each competitor, feature by feature, with quotes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Don't decide which product is better: report what AI says.

    line 41
  2. Distinctive:

    Never state what the brand offers from your own knowledge: ask the person.

    line 42
  3. Distinctive:

    Don't disparage a competitor, and claim nothing about them an answer doesn't say.

    line 43

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

How AI compares us

How AI engines describe the brand against each tracked competitor, feature by feature, in the engines' own words.

When to use

  • "Which features does AI name for Northwind but not for us?", "How does ChatGPT compare us with our rivals?"
  • For a page that answers "X or Y?", the Comparison page skill fits better.

What to read

  1. list_competitors, and get_competitor_comparison for the period: who the brand is compared with, and where each leads.
  2. get_mention_competitors: the competitors named beside the brand most often.
  3. list_mentions, then get_mention for answers that name the brand and a competitor together: what each is praised or faulted for.
  4. get_mentions_perception: what AI associates with the brand.

Steps

  1. Take the competitor the person names; with none, the two or three named beside the brand most.
  2. List the features and qualities the answers name, for the brand and for each competitor.
  3. For each one: who AI credits with it, with a short quote and its engine.
  4. Mark the features AI names for a competitor but never for the brand, and anything AI says about the brand that looks wrong.

Output

  1. A table: Feature, the brand, one column per competitor, Quote and engine.
  2. "Gaps": the features AI credits only to competitors, and what to check for each.
  3. Claims about the brand that look wrong, for the person to confirm.

Don't

  • Don't decide which product is better: report what AI says.
  • Never state what the brand offers from your own knowledge: ask the person.
  • Don't disparage a competitor, and claim nothing about them an answer doesn't say.

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.