← 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 content-gap-to-article

Full description — Now says: the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to...

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

content gaps hurting a brand's AI search visibility, then create, generate, and publish SEO/AEO-optimized articles to fill them — end to end, from gap analysis through CMS publishing. Use when the user wants to improve AI visibility with...

After

Nov 18, 2026 · 06:12 UTC

the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use ...

Skill instructions

Before

Sep 30, 2026 · 23:10 UTC

Find content gaps hurting a brand's AI search visibility, then create, generate, and publish SEO/AEO-optimized articles to fill them — end to end, from gap analysis through CMS publishing. Use when the user wants to improve AI visibility...

After

Nov 18, 2026 · 06:12 UTC

"Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,25 +1,32 @@
 ---
 name: content-gap-to-article
-description: Find content gaps hurting a brand's AI search visibility, then create, generate, and publish SEO/AEO-optimized articles to fill them — end to end, from gap analysis through CMS publishing. Use when the user wants to improve AI visibility with content, write articles, fill citation gaps, or publish to WordPress, Ghost, Webflow, Framer, or the ChatFeatured CMS. Not for analytics-only questions (use the visibility report).
+description: "Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use when the user wants content that improves AI visibility, asks what to write next, wants to fill citation gaps, or wants to write, edit or publish an article. Not for analytics-only questions (use aeo-visibility-report)."
 ---
 
-# Content Gap → Published Article
+# Content gap to published article
 
-Run ChatFeatured's content pipeline: identify what content is missing, create targeted article ideas, generate them, and publish.
+## Find the gaps
 
-## Steps
-
-1. **Resolve the brand** via `list_organizations` → `list_brands`; confirm with the user if they have several brands.
-2. **Find the gaps.** Use `query_analytics` (`source_mentions`, `cited_urls`) to see which topics and sources AI answers cite where the brand is absent, and `get_existing_opportunities` for gaps ChatFeatured has already identified. `list_articles` with `status: "published"` shows what the brand has already covered — don't propose duplicates.
-3. **Create ideas** with `create_article_ideas`, targeting the specific gaps found. Show the user the ideas before going further.
-4. **Approve with consent.** `approve_articles` consumes the plan's monthly article quota — tell the user how many articles this will use, and check the `articleLimits` (used/limit/remaining) in the response. If the quota is exhausted, stop and say so.
-5. **Generate** with `generate_articles`. Generation is asynchronous: poll `list_articles` with `status: "review"` to see when drafts are ready (typically minutes). Tell the user they can come back later rather than blocking on it.
-6. **Review pass.** When a draft is ready, fetch it with `get_article` and summarize it for the user. Apply requested edits with `update_article_content`.
-7. **Optional featured image.** `search_pexels_images` for a relevant photo, then `set_article_featured_image` with the photo's attribution fields.
-8. **Publish — only with explicit user confirmation.** `list_integrations` shows connected CMS platforms; if there are several, ask which one and pass its `integrationId`. Use `publish_article` for immediate publishing or `schedule_article` for a future date, then confirm success with `get_publish_status`.
+1. **Find the project.** `get_context`.
+2. **Find the gaps.** `query_visibility` for 30 days, `groupBy: ["prompt"]`, then `["prompt", "competitor"]`. A gap is a prompt where the brand has 0% visibility and competitors are mentioned often. `get_recommendations` lists the content gaps ChatFeatured has already found; use those first.
+3. **Check what's already covered.** `articles_read` (operation `articles.list`) for published and in-progress articles, so you don't propose a duplicate.
+4. **See what wins.** For each top gap, `get_answers` with its `promptId` lists the answers; `get_answers` with an `answerId` shows one answer with the pages it cites. Read two or three. The idea should beat those pages.
+5. **Propose ideas.** For the top three: a title, the angle, the prompt it targets, and the pages it has to beat. Show them to the user.
+6. **Save the ones they pick** with `save_articles` as ideas. Don't set `write` unless the user asks to start writing: writing uses the plan's monthly article allowance.
+
+## Write, edit and publish
+
+1. **Start writing.** `write_articles` with the idea ids. Each article uses one from the plan's monthly allowance, so say how many it will use and get a yes first. It returns a job per article.
+2. **Wait.** `wait_for_job` with the job ids; each call waits up to 50 seconds, so call it again while they run. Writing takes 2 to 5 minutes. If the user doesn't want to wait, tell them to come back later; the drafts stay in review.
+3. **Review.** `get_article` returns the outline; read only the sections you need with `sectionId`. Summarize or quote it for the user.
+4. **Edit.** `edit_article` with the `revision` you read: replace exact text, insert, or rewrite whole sections. Leave the rest alone. If it answers `revision_conflict`, someone changed the article; its details have the changed sections, so re-target your edit and send the new revision.
+5. **Images.** `generate_images` makes images into the project's library; follow the job with `wait_for_job`.
+6. **Publish, only when the user confirms.** `integrations_read` (operation `integrations.list`) shows the connected sites; if there are several, ask which. `publish_article` publishes now, or later with `publishAt`. If they published it themselves, `publish_article` can record the URL instead.
 
 ## Boundaries
 
-- Never call `approve_articles`, `publish_article`, or `schedule_article` without the user explicitly agreeing in this conversation — approval spends quota and publishing writes to their public website.
-- If no CMS integration is connected, complete the draft and tell the user how to connect one instead of failing.
-- One pipeline run per request; don't loop generating more articles than the user asked for.
+- Ask before saving, and never start writing without the user saying so.
+- Gaps on a platform with a thin sample may be noise; prefer gaps that show up on several platforms.
+- Writing spends the allowance and publishing changes their public site: both need the user's explicit yes in this conversation.
+- A published article is locked; the error says to reopen it before editing. Reopening keeps the live copy up until it's published again.
+- If no site is connected, finish the draft and tell the user to connect their CMS under **Integrations** in the ChatFeatured dashboard; the credentials go in there, not in the chat.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Find content gaps hurting a brand's AI search visibility, then create, generate, and publish SEO/AEO-optimized articles to fill them — end to end, from gap analysis through CMS publishing. Use when the user wants to improve AI visibility with content, write articles, fill citation gaps, or publish to WordPress, Ghost, Webflow, Framer, or the ChatFeatured CMS. Not for analytics-only questions (use the visibility report)."
AFTER
"Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use when the user wants content that improves AI visibility, asks what to write next, wants to fill citation gaps, or wants to write, edit or publish an article. Not for analytics-only questions (use aeo-visibility-report)."

changed /skill_md_contents

BEFORE
"---\nname: content-gap-to-article\ndescription: Find content gaps hurting a brand's AI search visibility, then create, generate, and publish SEO/AEO-optimized articles to fill them — end to end, from gap analysis through CMS publishing. Use when the user wants to improve AI visibility with content, write articles, fill citation gaps, or publish to WordPress, Ghost, Webflow, Framer, or the ChatFeatured CMS. Not for analytics-only questions (use the visibility report).\n---\n\n# Content Gap → Published Article\n\nRun ChatFeatured's content pipeline: identify what content is missing, create targeted article ideas, generate them, and publish.\n\n## Steps\n\n1. **Resolve the brand** via `list_organizations` → `list_brands`; confirm with the user if they have several brands.\n2. **Find the gaps.** Use `query_analytics` (`source_mentions`, `cited_urls`) to see which topics and sources AI answers cite where the brand is absent, and `get_existing_opportunities` for gaps ChatFeatured has already identified. `list_articles` with `status: \"published\"` shows what the brand has already covered — don't propose duplicates.\n3. **Create ideas** with `create_article_ideas`, targeting the specific gaps found. Show the user the ideas before going further.\n4. **Approve with consent.** `approve_articles` consumes the plan's monthly article quota — tell the user how many articles this will use, and check the `articleLimits` (used/limit/remaining) in the response. If the quota is exhausted, stop and say so.\n5. **Generate** with `generate_articles`. Generation is asynchronous: poll `list_articles` with `status: \"review\"` to see when drafts are ready (typically minutes). Tell the user they can come back later rather than blocking on it.\n6. **Review pass.** When a draft is ready, fetch it with `get_article` and summarize it for the user. Apply requested edits with `update_article_content`.\n7. **Optional featured image.** `search_pexels_images` for a relevant photo, then `set_article_featured_image` with the photo's attribution fields.\n8. **Publish — only with explicit user confirmation.** `list_integrations` shows connected CMS platforms; if there are several, ask which one and pass its `integrationId`. Use `publish_article` for immediate publishing or `schedule_article` for a future date, then confirm success with `get_publish_status`.\n\n## Boundaries\n\n- Never call `approve_articles`, `publish_article`, or `schedule_article` without the user explicitly agreeing in this conversation — approval spends quota and publishing writes to their public website.\n- If no CMS integration is connected, complete the draft and tell the user how to connect one instead of failing.\n- One pipeline run per request; don't loop generating more articles than the user asked for.\n"
AFTER
"---\nname: content-gap-to-article\ndescription: \"Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use when the user wants content that improves AI visibility, asks what to write next, wants to fill citation gaps, or wants to write, edit or publish an article. Not for analytics-only questions (use aeo-visibility-report).\"\n---\n\n# Content gap to published article\n\n## Find the gaps\n\n1. **Find the project.** `get_context`.\n2. **Find the gaps.** `query_visibility` for 30 days, `groupBy: [\"prompt\"]`, then `[\"prompt\", \"competitor\"]`. A gap is a prompt where the brand has 0% visibility and competitors are mentioned often. `get_recommendations` lists the content gaps ChatFeatured has already found; use those first.\n3. **Check what's already covered.** `articles_read` (operation `articles.list`) for published and in-progress articles, so you don't propose a duplicate.\n4. **See what wins.** For each top gap, `get_answers` with its `promptId` lists the answers; `get_answers` with an `answerId` shows one answer with the pages it cites. Read two or three. The idea should beat those pages.\n5. **Propose ideas.** For the top three: a title, the angle, the prompt it targets, and the pages it has to beat. Show them to the user.\n6. **Save the ones they pick** with `save_articles` as ideas. Don't set `write` unless the user asks to start writing: writing uses the plan's monthly article allowance.\n\n## Write, edit and publish\n\n1. **Start writing.** `write_articles` with the idea ids. Each article uses one from the plan's monthly allowance, so say how many it will use and get a yes first. It returns a job per article.\n2. **Wait.** `wait_for_job` with the job ids; each call waits up to 50 seconds, so call it again while they run. Writing takes 2 to 5 minutes. If the user doesn't want to wait, tell them to come back later; the drafts stay in review.\n3. **Review.** `get_article` returns the outline; read only the sections you need with `sectionId`. Summarize or quote it for the user.\n4. **Edit.** `edit_article` with the `revision` you read: replace exact text, insert, or rewrite whole sections. Leave the rest alone. If it answers `revision_conflict`, someone changed the article; its details have the changed sections, so re-target your edit and send the new revision.\n5. **Images.** `generate_images` makes images into the project's library; follow the job with `wait_for_job`.\n6. **Publish, only when the user confirms.** `integrations_read` (operation `integrations.list`) shows the connected sites; if there are several, ask which. `publish_article` publishes now, or later with `publishAt`. If they published it themselves, `publish_article` can record the URL instead.\n\n## Boundaries\n\n- Ask before saving, and never start writing without the user saying so.\n- Gaps on a platform with a thin sample may be noise; prefer gaps that show up on several platforms.\n- Writing spends the allowance and publishing changes their public site: both need the user's explicit yes in this conversation.\n- A published article is locked; the error says to reopen it before editing. Reopening keeps the live copy up until it's published again.\n- If no site is connected, finish the draft and tell the user to connect their CMS under **Integrations** in the ChatFeatured dashboard; the credentials go in there, not in the chat.\n"
Full snapshot data
{
  "description": "Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use when the user wants content that improves AI visibility, asks what to write next, wants to fill citation gaps, or wants to write, edit or publish an article. Not for analytics-only questions (use aeo-visibility-report).",
  "included_files": [],
  "name": "content-gap-to-article",
  "skill_md_contents": "---\nname: content-gap-to-article\ndescription: \"Find the prompts where competitors get mentioned in AI answers and the brand doesn't, turn the best into article ideas, then write, edit and publish them to WordPress, Webflow, Ghost, Framer, HubSpot, Sanity, Wix or the ChatFeatured CMS. Use when the user wants content that improves AI visibility, asks what to write next, wants to fill citation gaps, or wants to write, edit or publish an article. Not for analytics-only questions (use aeo-visibility-report).\"\n---\n\n# Content gap to published article\n\n## Find the gaps\n\n1. **Find the project.** `get_context`.\n2. **Find the gaps.** `query_visibility` for 30 days, `groupBy: [\"prompt\"]`, then `[\"prompt\", \"competitor\"]`. A gap is a prompt where the brand has 0% visibility and competitors are mentioned often. `get_recommendations` lists the content gaps ChatFeatured has already found; use those first.\n3. **Check what's already covered.** `articles_read` (operation `articles.list`) for published and in-progress articles, so you don't propose a duplicate.\n4. **See what wins.** For each top gap, `get_answers` with its `promptId` lists the answers; `get_answers` with an `answerId` shows one answer with the pages it cites. Read two or three. The idea should beat those pages.\n5. **Propose ideas.** For the top three: a title, the angle, the prompt it targets, and the pages it has to beat. Show them to the user.\n6. **Save the ones they pick** with `save_articles` as ideas. Don't set `write` unless the user asks to start writing: writing uses the plan's monthly article allowance.\n\n## Write, edit and publish\n\n1. **Start writing.** `write_articles` with the idea ids. Each article uses one from the plan's monthly allowance, so say how many it will use and get a yes first. It returns a job per article.\n2. **Wait.** `wait_for_job` with the job ids; each call waits up to 50 seconds, so call it again while they run. Writing takes 2 to 5 minutes. If the user doesn't want to wait, tell them to come back later; the drafts stay in review.\n3. **Review.** `get_article` returns the outline; read only the sections you need with `sectionId`. Summarize or quote it for the user.\n4. **Edit.** `edit_article` with the `revision` you read: replace exact text, insert, or rewrite whole sections. Leave the rest alone. If it answers `revision_conflict`, someone changed the article; its details have the changed sections, so re-target your edit and send the new revision.\n5. **Images.** `generate_images` makes images into the project's library; follow the job with `wait_for_job`.\n6. **Publish, only when the user confirms.** `integrations_read` (operation `integrations.list`) shows the connected sites; if there are several, ask which. `publish_article` publishes now, or later with `publishAt`. If they published it themselves, `publish_article` can record the URL instead.\n\n## Boundaries\n\n- Ask before saving, and never start writing without the user saying so.\n- Gaps on a platform with a thin sample may be noise; prefer gaps that show up on several platforms.\n- Writing spends the allowance and publishing changes their public site: both need the user's explicit yes in this conversation.\n- A published article is locked; the error says to reopen it before editing. Reopening keeps the live copy up until it's published again.\n- If no site is connected, finish the draft and tell the user to connect their CMS under **Integrations** in the ChatFeatured dashboard; the credentials go in there, not in the chat.\n"
}

SHA-256 of public snapshot: 390b0998c7ac8f15c67b360e6aad8549fc1fc9f79091cb26bd867d5951d12c48