← ChatFeaturedCONTENT HISTORY

Update to ChatFeatured

Snapshot Nov 18, 2026 · 06:12 UTC · version 1.1.1

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for aeo-visibility-report

Full description — Now says: brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it,...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save ChatFeatured and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:10 UTC

brand — how often it appears in ChatGPT, Perplexity, Gemini, and other AI answers, how it compares to competitors, which sources cite it, and where it's losing ground. Use when the user asks about AI visibility, brand mentions in AI answ...

After

Nov 18, 2026 · 06:12 UTC

brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in...

Skill instructions

Before

Sep 30, 2026 · 23:10 UTC

Build an AI search visibility report for a brand — how often it appears in ChatGPT, Perplexity, Gemini, and other AI answers, how it compares to competitors, which sources cite it, and where it's losing ground. Use when the user asks abo...

After

Nov 18, 2026 · 06:12 UTC

"Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,30 +1,22 @@
 ---
 name: aeo-visibility-report
-description: Build an AI search visibility report for a brand — how often it appears in ChatGPT, Perplexity, Gemini, and other AI answers, how it compares to competitors, which sources cite it, and where it's losing ground. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, or citation analysis. Not for website technical health (use the site audit) or for creating content.
+description: "Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, citation analysis, or a weekly or monthly report. Not for website technical health (use site-audit-triage) or for writing content (use content-gap-to-article)."
 ---
 
-# AEO Visibility Report
-
-Produce a decision-ready report on a brand's AI search visibility using ChatFeatured analytics.
+# AI visibility report
 
 ## Steps
 
-1. **Resolve the brand.** Call `list_organizations`, then `list_brands`. If the user has exactly one brand, use it; otherwise ask which brand to analyze. Pass its `brandId` to every call below.
-2. **Pull the core analytics** with `query_analytics`, defaulting to a 30-day window (`filters: { dateRange: "30d" }`) unless the user asks for another period:
-   - `brand_overview` — headline visibility, mention counts, and platform mix.
-   - `time_comparison` — current period vs the previous one; this is where trends come from.
-   - `competitor_comparison` — share of voice against tracked competitors.
-   - `source_analysis` and `cited_urls` — which domains and URLs AI answers cite in this space, and whether the brand's own pages are among them.
-3. **Go deeper only where the data warrants it.** If a preset surfaces something notable (a competitor spike, a platform drop), use `query_analytics` with `source_changes` or `source_mentions`, or `query_analytics_sql` for a custom cut (call it with `explain: true` first to get the schema). Skip this step for a routine report.
-4. **Synthesize.** Structure the report as:
-   - Headline: overall visibility and the single biggest change since the prior period.
-   - Platform breakdown: where the brand is strong/weak (ChatGPT vs Perplexity vs Gemini, etc.).
-   - Competitive position: who leads share of voice and by how much.
-   - Citation gaps: domains AI answers trust in this space where the brand is absent — these are the actionable opportunities.
-   - 2–4 concrete recommendations tied to the gaps found.
-
-## Boundaries
-
-- Report numbers exactly as returned; never extrapolate missing periods.
-- If a preset returns zero rows, say the data window is empty rather than inventing a trend, and suggest the user check that prompt tracking is running.
-- Recommendations that involve creating content should point at the content-gap workflow rather than starting article generation from here.
+1. **Find the project.** `get_context` lists the projects you can reach. Use the only one, or the one the user named; if there are several and they didn't say, ask.
+2. **Read the brief.** `get_brief` with `dateRange` 7d for a weekly report, 30d for a monthly one. One call returns visibility with its `sampleSize`, mentions, citations, each AI platform, the competitor ranking, the prompts that moved, the most cited domains, and prompts added or paused in the period.
+3. **See what changed.** `get_changes` with `since` set to the start of the period: prompts that moved, competitors that gained, citations won and lost.
+4. **Go deeper only where something moved.** `query_visibility` with the ids the brief gave: `groupBy: ["date"]` for when a drop happened, `["prompt", "competitor"]` for where a competitor wins, the `cited_urls` preset for which pages get cited. Use `query_sql` for anything else, after `explain: true` for the schema.
+5. **Pick the next steps.** `get_recommendations` gives one ranked list; take the top two or three.
+
+## Writing the report
+
+- Lead with visibility and its change, then the one change that matters most.
+- Then platforms (where the brand is strong and weak), competitors (who leads and by how much), citations (which sites AI trusts where the brand is missing), and the next steps.
+- Give numbers as returned. When a platform has `thinSample`, or a visibility range (`visibilityLow` to `visibilityHigh`) is wide, say the number rests on few answers instead of calling it a trend.
+- Before explaining a drop, check the brief's tracking section: prompts added or paused move the numbers on their own.
+- If the period has no data, say so and suggest checking that prompts are being tracked.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Build an AI search visibility report for a brand — how often it appears in ChatGPT, Perplexity, Gemini, and other AI answers, how it compares to competitors, which sources cite it, and where it's losing ground. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, or citation analysis. Not for website technical health (use the site audit) or for creating content."
AFTER
"Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, citation analysis, or a weekly or monthly report. Not for website technical health (use site-audit-triage) or for writing content (use content-gap-to-article)."

changed /skill_md_contents

BEFORE
"---\nname: aeo-visibility-report\ndescription: Build an AI search visibility report for a brand — how often it appears in ChatGPT, Perplexity, Gemini, and other AI answers, how it compares to competitors, which sources cite it, and where it's losing ground. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, or citation analysis. Not for website technical health (use the site audit) or for creating content.\n---\n\n# AEO Visibility Report\n\nProduce a decision-ready report on a brand's AI search visibility using ChatFeatured analytics.\n\n## Steps\n\n1. **Resolve the brand.** Call `list_organizations`, then `list_brands`. If the user has exactly one brand, use it; otherwise ask which brand to analyze. Pass its `brandId` to every call below.\n2. **Pull the core analytics** with `query_analytics`, defaulting to a 30-day window (`filters: { dateRange: \"30d\" }`) unless the user asks for another period:\n   - `brand_overview` — headline visibility, mention counts, and platform mix.\n   - `time_comparison` — current period vs the previous one; this is where trends come from.\n   - `competitor_comparison` — share of voice against tracked competitors.\n   - `source_analysis` and `cited_urls` — which domains and URLs AI answers cite in this space, and whether the brand's own pages are among them.\n3. **Go deeper only where the data warrants it.** If a preset surfaces something notable (a competitor spike, a platform drop), use `query_analytics` with `source_changes` or `source_mentions`, or `query_analytics_sql` for a custom cut (call it with `explain: true` first to get the schema). Skip this step for a routine report.\n4. **Synthesize.** Structure the report as:\n   - Headline: overall visibility and the single biggest change since the prior period.\n   - Platform breakdown: where the brand is strong/weak (ChatGPT vs Perplexity vs Gemini, etc.).\n   - Competitive position: who leads share of voice and by how much.\n   - Citation gaps: domains AI answers trust in this space where the brand is absent — these are the actionable opportunities.\n   - 2–4 concrete recommendations tied to the gaps found.\n\n## Boundaries\n\n- Report numbers exactly as returned; never extrapolate missing periods.\n- If a preset returns zero rows, say the data window is empty rather than inventing a trend, and suggest the user check that prompt tracking is running.\n- Recommendations that involve creating content should point at the content-gap workflow rather than starting article generation from here.\n"
AFTER
"---\nname: aeo-visibility-report\ndescription: \"Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, citation analysis, or a weekly or monthly report. Not for website technical health (use site-audit-triage) or for writing content (use content-gap-to-article).\"\n---\n\n# AI visibility report\n\n## Steps\n\n1. **Find the project.** `get_context` lists the projects you can reach. Use the only one, or the one the user named; if there are several and they didn't say, ask.\n2. **Read the brief.** `get_brief` with `dateRange` 7d for a weekly report, 30d for a monthly one. One call returns visibility with its `sampleSize`, mentions, citations, each AI platform, the competitor ranking, the prompts that moved, the most cited domains, and prompts added or paused in the period.\n3. **See what changed.** `get_changes` with `since` set to the start of the period: prompts that moved, competitors that gained, citations won and lost.\n4. **Go deeper only where something moved.** `query_visibility` with the ids the brief gave: `groupBy: [\"date\"]` for when a drop happened, `[\"prompt\", \"competitor\"]` for where a competitor wins, the `cited_urls` preset for which pages get cited. Use `query_sql` for anything else, after `explain: true` for the schema.\n5. **Pick the next steps.** `get_recommendations` gives one ranked list; take the top two or three.\n\n## Writing the report\n\n- Lead with visibility and its change, then the one change that matters most.\n- Then platforms (where the brand is strong and weak), competitors (who leads and by how much), citations (which sites AI trusts where the brand is missing), and the next steps.\n- Give numbers as returned. When a platform has `thinSample`, or a visibility range (`visibilityLow` to `visibilityHigh`) is wide, say the number rests on few answers instead of calling it a trend.\n- Before explaining a drop, check the brief's tracking section: prompts added or paused move the numbers on their own.\n- If the period has no data, say so and suggest checking that prompts are being tracked.\n"
Full snapshot data
{
  "description": "Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, citation analysis, or a weekly or monthly report. Not for website technical health (use site-audit-triage) or for writing content (use content-gap-to-article).",
  "included_files": [],
  "name": "aeo-visibility-report",
  "skill_md_contents": "---\nname: aeo-visibility-report\ndescription: \"Build an AI search visibility report for a brand: how often it appears in ChatGPT, Perplexity, Gemini, Claude, Google AI and other AI answers, how it compares to competitors, which sources cite it, and what to do next. Use when the user asks about AI visibility, brand mentions in AI answers, share of voice, competitor comparison, citation analysis, or a weekly or monthly report. Not for website technical health (use site-audit-triage) or for writing content (use content-gap-to-article).\"\n---\n\n# AI visibility report\n\n## Steps\n\n1. **Find the project.** `get_context` lists the projects you can reach. Use the only one, or the one the user named; if there are several and they didn't say, ask.\n2. **Read the brief.** `get_brief` with `dateRange` 7d for a weekly report, 30d for a monthly one. One call returns visibility with its `sampleSize`, mentions, citations, each AI platform, the competitor ranking, the prompts that moved, the most cited domains, and prompts added or paused in the period.\n3. **See what changed.** `get_changes` with `since` set to the start of the period: prompts that moved, competitors that gained, citations won and lost.\n4. **Go deeper only where something moved.** `query_visibility` with the ids the brief gave: `groupBy: [\"date\"]` for when a drop happened, `[\"prompt\", \"competitor\"]` for where a competitor wins, the `cited_urls` preset for which pages get cited. Use `query_sql` for anything else, after `explain: true` for the schema.\n5. **Pick the next steps.** `get_recommendations` gives one ranked list; take the top two or three.\n\n## Writing the report\n\n- Lead with visibility and its change, then the one change that matters most.\n- Then platforms (where the brand is strong and weak), competitors (who leads and by how much), citations (which sites AI trusts where the brand is missing), and the next steps.\n- Give numbers as returned. When a platform has `thinSample`, or a visibility range (`visibilityLow` to `visibilityHigh`) is wide, say the number rests on few answers instead of calling it a trend.\n- Before explaining a drop, check the brief's tracking section: prompts added or paused move the numbers on their own.\n- If the period has no data, say so and suggest checking that prompts are being tracked.\n"
}

SHA-256 of public snapshot: d2b25ba54a295f1d09f22fbb372475b89775afe25e7aec311399221983340dd6