ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/compare/SKILL.mdcompare
Skill432 starsChanged 11 days agoMITView on GitHub
Compares cited pages and drafts a balanced comparison with dated facts.
17 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- RemiPelloux/kill-my-ideatheir own version, first seen Nov 15, 2026
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- Hainrixz/claude-seo-aitheir own version, first seen Nov 1, 2026
- ansvisor/ansvisoredited, first seen Nov 1, 2026
- TakaGoto/rag-learning-academytheir own version, first seen Oct 28, 2026
- adeerkhan/vitruviustheir own version, first seen Oct 20, 2026
Used with
Projects with it also use evaluate, triage and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkillevaluate
Scores existing Sports Intelligence AVLM inference outputs with avlm/evals: MCQ accuracy (run_mcq_eval.sh, INFERENCE_DIR), open-ended LLM-as-judge scores (needs CLIENT_API_KEY for the configured judge endpoint), tennis category breakdowns, run comparisons, chance-level sanity checks and triage of mcq_results.json or llm_judge_results.json. Use when the user asks to score, evaluate, benchmark or compare predictions.jsonl from inference runs, or to explain a suspicious accuracy. Not for running inference, training, quantization, data preparation, or third-party API model inference: never open, list or run anything under avlm/evals/inference_3rdparty, including when the user asks for it; it is excluded from the release.
Also in 3 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
- NVIDIASkill
research
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- ansvisor/ansvisor★ 24199% same
Wrote their own version · 16
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
- Hainrixz/claude-seo-ai★ 81same name
- TakaGoto/rag-learning-academy★ 24same name
- n24q02m/wet★ 23same name
- n24q02m/wet-mcp★ 23same name
- adeerkhan/vitruvius★ 10same name
- joyehuang/skills★ 9same name
- yarikleto/claude-teacher-plugin★ 9same name
- synaptiai/agent-capability-standard★ 6same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- analyzeSkill
- answerfirstSkill
- audit-fixSkill
- auditSkill
- beatSkill
- createSkill
- factsSkill
- faqSkill
- featuresSkill
- gapsSkill
- getcito-aeo-coachSkill
- getcito-aeo-coach-standaloneSkill
- listingsSkill
- marketsSkill
- new-reportSkill
- opportunitiesSkill
- optimizeSkill
- publishSkill
- qualitySkill
- questionsSkill
- refreshSkill
- reportSkill
- rivalsSkill
- shoppingSkill
- startSkill
- tasksSkill
- translateSkill
- winbackSkill
- wrongclaimSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 44
Don't disparage the competitor or claim what you can't source.
- Distinctive: line 45
No tracking numbers, share of voice or rankings on the page: it is public content.
- Distinctive: line 46
Don't invent prices, plan limits or feature lists, for either side.
- Distinctive: line 47
Never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its …
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Comparison page
A balanced comparison page that answers "X or Y?" the way AI engines like to quote: plainly, fairly, with dates.
When to use
- "Write an GetCito vs Northwind page", "We lose the 'best alternative to X' prompt: draft a page", "Make an alternatives page."
- To change the brand's existing pages against one competitor instead, the Beat a competitor skill fits better.
What to read
list_competitors: the tracked competitors and their domains.list_ai_answersfor the comparison prompt: how AI frames the choice today, and which pages it cites.list_citationswith the competitor and external filters: the comparison and review pages AI cites.get_fanoutsfor the prompt: the questions people ask around the choice.get_competitor_comparisononly as internal context: it never goes on the page.
Steps
- Pick the prompt and the competitor. If either is unclear, ask, with the tracked competitors as the options.
- Compare the pages AI engines cite for that prompt: what they answer, how they lay out the choice, how old their facts are.
- Draft the comparison page:
- Open with the answer: who should pick which option, in two or three sentences.
- A comparison table: one row per feature or need, a column for each option, and an "as of {date}" line under it.
- A short section for each option's strengths, the competitor's included, and an FAQ from the fan-outs.
- Facts about the competitor come only from pages read in this chat or from the person, each with the date it was true. Facts about the brand come from the person or its own pages; anything else is a [placeholder].
- Save it as a draft when the person wants it kept, with
create_draft(page type comparison or alternatives); the app asks them first when it should. In an agent's run nobody is there to ask: always save it with its tool, and the app holds it for approval where the agent's mode needs it.
Output
The page as HTML, and under it the list of facts the person must check before it goes live.
Don't
- Don't disparage the competitor or claim what you can't source.
- No tracking numbers, share of voice or rankings on the page: it is public content.
- Don't invent prices, plan limits or feature lists, for either side.
- Never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its own.
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
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.