← 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 site-audit-triage

Full description — Now says: Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their...

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

Triage a brand website's AEO health — technical, content, and AI-optimization issues that stop AI engines from crawling, understanding, and citing the site — and produce a prioritized fix plan. Use when the user asks to audit their site,...

After

Nov 18, 2026 · 06:12 UTC

Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structu...

Skill instructions

Before

Sep 30, 2026 · 23:10 UTC

Triage a brand website's AEO health — technical, content, and AI-optimization issues that stop AI engines from crawling, understanding, and citing the site — and produce a prioritized fix plan. Use when the user asks to audit their site,...

After

Nov 18, 2026 · 06:12 UTC

"Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, struct...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,29 +1,19 @@
 ---
 name: site-audit-triage
-description: Triage a brand website's AEO health — technical, content, and AI-optimization issues that stop AI engines from crawling, understanding, and citing the site — and produce a prioritized fix plan. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or wants technical/content/AEO issues found and ranked. Not for visibility analytics (use the visibility report) or for writing articles.
+description: "Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structured data, robots or thin content. Not for visibility analytics (use aeo-visibility-report) or for writing articles (use content-gap-to-article)."
 ---
 
-# Site Audit Triage
-
-Turn ChatFeatured's site audit data into a prioritized, actionable fix plan.
+# Site audit triage
 
 ## Steps
 
-1. **Resolve the brand** via `list_organizations` → `list_brands`.
-2. **Get the lay of the land** with `query_site_audit` `query: "overview"` — audit status, page counts, average scores, and open-issue counts by category. If no audit has run yet (check `run_status` when the overview looks empty), tell the user to start one from the ChatFeatured dashboard and stop.
-3. **Enumerate the problems:**
-   - `open_issues` — open issues grouped by category and check; run it per category (`technical`, `content`, `aeo`) if the user cares about one area.
-   - `pages_needing_improvement` — the lowest-scoring pages with open issues.
-4. **Drill into the worst pages** with `page_detail` for the 3–5 lowest scorers (pass each `pageUrl`) to see exactly which checks fail on them.
-5. **Also check crawler access** with `query_crawler_analytics` (`stats`, then `top_pages`): if AI bots barely crawl the site, access problems outrank on-page fixes.
-6. **Deliver a fix plan** ordered by impact:
-   - Blockers first: anything stopping AI crawlers from reaching or reading pages (robots rules, timeouts, thin/duplicate content on key pages).
-   - Then high-traffic pages with low scores — fixes there pay off fastest.
-   - Then category-wide patterns (e.g. missing structured data across the blog) as a single batch item, not per-page noise.
-   - For each item: what's wrong, which pages, and the concrete fix.
+1. **Find the project.** `get_context`.
+2. **Overview.** `website_read`: operation `sites.list` for the site, then `issues.list` for open issues and `pages.list` for page scores (lowest first).
+3. **Rank the fixes.** Site-wide problems first (llms.txt, robots, structured data), then the lowest-scoring pages that AI answers cite or that target tracked prompts. `get_recommendations` already ranks audit fixes alongside other work.
+4. **Explain each fix** in a sentence: what's wrong, on which pages, and what to change. Quote the check's details rather than guessing.
+5. **Check the fixes.** For site-wide fixes (robots.txt, sitemap, llms.txt, HTTPS), `website_write` (operation `siteAudits.start`) re-runs the site checks and is free. For page fixes, `website_write` (operation `pageAudits.start`) re-audits those pages at one page audit credit each; say how many credits before starting.
 
 ## Boundaries
 
-- This skill reads audit data; it cannot start audits or change the website. Say so when the user asks you to "fix" something — hand them the exact change to make instead.
-- Score numbers and issue counts come from the tool responses verbatim; don't estimate scores for unaudited pages.
-- If the user wants new content to fix content gaps, route them to the content-gap workflow.
+- Report what the audit found; don't invent issues it didn't flag.
+- If the site hasn't been audited, say so and offer to start a site audit (free), then page audits for the pages that matter (one credit each).
Full technical diff · 2 changed fields

changed /description

BEFORE
"Triage a brand website's AEO health — technical, content, and AI-optimization issues that stop AI engines from crawling, understanding, and citing the site — and produce a prioritized fix plan. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or wants technical/content/AEO issues found and ranked. Not for visibility analytics (use the visibility report) or for writing articles."
AFTER
"Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structured data, robots or thin content. Not for visibility analytics (use aeo-visibility-report) or for writing articles (use content-gap-to-article)."

changed /skill_md_contents

BEFORE
"---\nname: site-audit-triage\ndescription: Triage a brand website's AEO health — technical, content, and AI-optimization issues that stop AI engines from crawling, understanding, and citing the site — and produce a prioritized fix plan. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or wants technical/content/AEO issues found and ranked. Not for visibility analytics (use the visibility report) or for writing articles.\n---\n\n# Site Audit Triage\n\nTurn ChatFeatured's site audit data into a prioritized, actionable fix plan.\n\n## Steps\n\n1. **Resolve the brand** via `list_organizations` → `list_brands`.\n2. **Get the lay of the land** with `query_site_audit` `query: \"overview\"` — audit status, page counts, average scores, and open-issue counts by category. If no audit has run yet (check `run_status` when the overview looks empty), tell the user to start one from the ChatFeatured dashboard and stop.\n3. **Enumerate the problems:**\n   - `open_issues` — open issues grouped by category and check; run it per category (`technical`, `content`, `aeo`) if the user cares about one area.\n   - `pages_needing_improvement` — the lowest-scoring pages with open issues.\n4. **Drill into the worst pages** with `page_detail` for the 3–5 lowest scorers (pass each `pageUrl`) to see exactly which checks fail on them.\n5. **Also check crawler access** with `query_crawler_analytics` (`stats`, then `top_pages`): if AI bots barely crawl the site, access problems outrank on-page fixes.\n6. **Deliver a fix plan** ordered by impact:\n   - Blockers first: anything stopping AI crawlers from reaching or reading pages (robots rules, timeouts, thin/duplicate content on key pages).\n   - Then high-traffic pages with low scores — fixes there pay off fastest.\n   - Then category-wide patterns (e.g. missing structured data across the blog) as a single batch item, not per-page noise.\n   - For each item: what's wrong, which pages, and the concrete fix.\n\n## Boundaries\n\n- This skill reads audit data; it cannot start audits or change the website. Say so when the user asks you to \"fix\" something — hand them the exact change to make instead.\n- Score numbers and issue counts come from the tool responses verbatim; don't estimate scores for unaudited pages.\n- If the user wants new content to fix content gaps, route them to the content-gap workflow.\n"
AFTER
"---\nname: site-audit-triage\ndescription: \"Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structured data, robots or thin content. Not for visibility analytics (use aeo-visibility-report) or for writing articles (use content-gap-to-article).\"\n---\n\n# Site audit triage\n\n## Steps\n\n1. **Find the project.** `get_context`.\n2. **Overview.** `website_read`: operation `sites.list` for the site, then `issues.list` for open issues and `pages.list` for page scores (lowest first).\n3. **Rank the fixes.** Site-wide problems first (llms.txt, robots, structured data), then the lowest-scoring pages that AI answers cite or that target tracked prompts. `get_recommendations` already ranks audit fixes alongside other work.\n4. **Explain each fix** in a sentence: what's wrong, on which pages, and what to change. Quote the check's details rather than guessing.\n5. **Check the fixes.** For site-wide fixes (robots.txt, sitemap, llms.txt, HTTPS), `website_write` (operation `siteAudits.start`) re-runs the site checks and is free. For page fixes, `website_write` (operation `pageAudits.start`) re-audits those pages at one page audit credit each; say how many credits before starting.\n\n## Boundaries\n\n- Report what the audit found; don't invent issues it didn't flag.\n- If the site hasn't been audited, say so and offer to start a site audit (free), then page audits for the pages that matter (one credit each).\n"
Full snapshot data
{
  "description": "Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structured data, robots or thin content. Not for visibility analytics (use aeo-visibility-report) or for writing articles (use content-gap-to-article).",
  "included_files": [],
  "name": "site-audit-triage",
  "skill_md_contents": "---\nname: site-audit-triage\ndescription: \"Turn a brand website's audit into a short, ordered list of fixes that help AI assistants crawl, understand and cite it. Use when the user asks to audit their site, asks why AI answers don't cite their pages, or mentions llms.txt, structured data, robots or thin content. Not for visibility analytics (use aeo-visibility-report) or for writing articles (use content-gap-to-article).\"\n---\n\n# Site audit triage\n\n## Steps\n\n1. **Find the project.** `get_context`.\n2. **Overview.** `website_read`: operation `sites.list` for the site, then `issues.list` for open issues and `pages.list` for page scores (lowest first).\n3. **Rank the fixes.** Site-wide problems first (llms.txt, robots, structured data), then the lowest-scoring pages that AI answers cite or that target tracked prompts. `get_recommendations` already ranks audit fixes alongside other work.\n4. **Explain each fix** in a sentence: what's wrong, on which pages, and what to change. Quote the check's details rather than guessing.\n5. **Check the fixes.** For site-wide fixes (robots.txt, sitemap, llms.txt, HTTPS), `website_write` (operation `siteAudits.start`) re-runs the site checks and is free. For page fixes, `website_write` (operation `pageAudits.start`) re-audits those pages at one page audit credit each; say how many credits before starting.\n\n## Boundaries\n\n- Report what the audit found; don't invent issues it didn't flag.\n- If the site hasn't been audited, say so and offer to start a site audit (free), then page audits for the pages that matter (one credit each).\n"
}

SHA-256 of public snapshot: 8fffdae62fcead8c86162cb50c3a696531222961f1466edcf9978c523e67173c