[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9BZBJAM1JPTWYHKNQ0ARP":3,"skill-same:01M6M9BZBJAM1JPTWYHKNQ0ARP":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6M9BZBJAM1JPTWYHKNQ0ARP","suede-programmatic-seo",null,"Suede AI Programmatic SEO Skills: playbook, source model, templates, unique value, internal links, sitemaps, phased rollout, and KPIs. Use when asked \"build location pages at scale\" or to rescue thin templated pages. NOT FOR: site audits (suede-seo-audit), AI-answer measurement (suede-ai-seo), editorial planning (suede-content-strategy), or bulk publishing without approval.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"suede programmatic seo","programmatic seo","seo","programmatic","links","when","editorial","value","source","for","at","measurement","answer","planning","bulk","ai-seo","rescue","rollout","model","playbook","audit","2026-11-10 10:12:30",false,"---\nname: suede-programmatic-seo\ndescription: \"Suede AI Programmatic SEO Skills: playbook, source model, templates, unique value, internal links, sitemaps, phased rollout, and KPIs. Use when asked \\\"build location pages at scale\\\" or to rescue thin templated pages. NOT FOR: site audits (suede-seo-audit), AI-answer measurement (suede-ai-seo), editorial planning (suede-content-strategy), or bulk publishing without approval.\"\nmetadata:\n  display-name: \"Suede AI Programmatic SEO Skills\"\n  version: 3.0.1\n---\n\n# Suede AI Programmatic SEO Skills\n\n## Compatibility\n\nRequires a source dataset with reuse rights, query-pattern evidence, and page\u002Ftemplate access. Current search policies require browsing. Local planning\u002Fbuilding needs no new integration; publication requires authority.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nProgrammatic pages work when each one answers a real query with data the\nsearcher cannot get faster elsewhere. They fail, and can drag the whole site\ndown, when they are one template with a swapped city name. This skill treats\npage count as something a sample earns, never a target.\n\n## Gate policy: advisory, not blocking\n\nEvery gate and verdict here is a recommendation to the user, not a control on\nthe agent. A failed gate changes what you report, never what you do. Single\nexception: an extremely risky finding (data loss, credential exposure, legal or\nrights violations, payment mistakes, irreversible public damage) pauses for the\nuser's choice.\n\n## The policy line you must stay behind\n\nGoogle's spam policies name three patterns programmatic sites trip most:\n\n- **Scaled content abuse**: many pages generated mainly to manipulate rankings\n  or AI answers and not to help people, whatever tool produced them.\n- **Doorway abuse**: sites or pages created to rank for similar queries that\n  funnel users to the same destination (\"[service] in [city]\" pages with\n  nothing local on them).\n- **Site reputation abuse**: third-party pages published on a host site to\n  borrow its ranking signals with little first-party oversight.\n\nGoogle also says AI answers need no special pages; producing variants for AI\nis the same abuse. Every gate below exists to keep a page set on the right\nside of this line. Source: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fessentials\u002Fspam-policies\n\n## Initial assessment\n\nRead `.agents\u002Fproduct-marketing.md` (or `.claude\u002Fproduct-marketing.md`, or the\nlegacy `product-marketing-context.md`) if present. Then establish:\n\n1. **Business**: product, audience, the conversion each page should earn.\n2. **Pattern and demand**: the repeating query pattern, its variables, how many\n   combinations have evidence of demand (Search Console, Keyword Planner, or a\n   dated export; otherwise `unknown`).\n3. **Competition**: who ranks now, what their pages contain, and whether you\n   can offer something they do not.\n4. **Data**: what populates each page, where it comes from, how often it\n   refreshes, and whether you have the rights to publish it.\n5. **Delivery**: CMS or framework, and whether it can template, split sitemaps,\n   and set `noindex` and canonicals per page.\n\n## Data defensibility\n\nThe data decides whether the set is worth building. Rank it:\n\n1. Proprietary (you created it: usage stats, tests, benchmarks)\n2. Product-derived (aggregated from your users, with consent)\n3. User-generated (reviews, submissions, community)\n4. Licensed (exclusive or contracted)\n5. Public (anyone can publish it; weakest, needs real added analysis)\n\nA set built only on tier-5 data needs an original layer (scoring, comparison,\ncalculation, local verification) or it is a doorway set.\n\n## Playbooks\n\n| Playbook | Pattern | Example |\n|---|---|---|\n| Templates | \"[type] template\" | \"invoice template\" |\n| Curation | \"best [category] for [segment]\" | \"best CRM for agencies\" |\n| Conversions | \"[X] to [Y]\" | \"kg to lbs\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [place]\" | \"coworking in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[A] [B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is churn rate\" |\n| Translations | localized versions | \"\u002Fes\u002F\", \"\u002Fde\u002F\" |\n| Directory | \"[category] tools\" | \"ai writing tools\" |\n| Profiles | \"[entity]\" or \"[entity] [attribute]\" | \"stripe pricing history\" |\n\nRead `references\u002Fplaybooks.md` when choosing, layering, or implementing one. It\nholds per-playbook value requirements, URL patterns, and the asset-to-playbook\ntable.\n\n## Implementation\n\n### 1. Pattern and demand\n\nName the pattern, the variables, and the candidate list. Keep only\ncombinations with demand evidence or a clear reader need. Combinations with no\nevidence wait for phase 2 or never ship.\n\n### 2. Data model\n\nOne row per page. Columns for every page-unique field, its source, its\nlast-verified date, and a `publish` flag computed from the gates below. Rows\nthat fail stay in the table with `publish = false`.\n\n### 3. Template\n\n- H1 and title that carry the page's variables naturally.\n- A direct answer in the opening that uses the row's own data (\"Median [metric]\n  in [city] was [value] in [month year], per [source]\"), never generic copy.\n- Data sections that render only when the row has the data (conditional\n  blocks, not empty placeholders).\n- An original layer: a calculation, ranking, comparison, or note that exists\n  only because you combined the data.\n- Related-page links and a CTA matched to intent.\n- Schema only where a supported feature fits; `BreadcrumbList` and\n  `Organization` via a shared `@id` are usually safe.\n\n### 4. Internal linking\n\n- Hub pages per category and per parent (city, industry, integration category)\n  that link to every published child.\n- Children link to the hub, to siblings that share a real relationship (nearby\n  cities, adjacent integrations), and to the main product page.\n- No orphans: every published page reachable within three or four clicks from\n  the home page through crawlable `\u003Ca href>` links.\n- Breadcrumbs, visible and marked up.\n\n### 5. Indexation\n\n- One sitemap per page type so indexation can be read per set.\n- Rows below the gates are not generated, or are generated with `noindex` and\n  left out of the sitemap until they pass.\n- Self-referencing canonicals; no canonicalizing many thin pages to one hub as\n  a substitute for not publishing them.\n- Use subfolders under the main domain unless there is a technical or\n  organizational reason for a subdomain; Google treats both as crawlable, but a\n  subdomain is managed and measured as a separate property.\n- Crawl budget matters only for very large sets (tens of thousands of URLs or\n  more); below that, quality gates are the constraint.\n\n## Quality gates\n\nRun on a **sample of 10 pages or 5% of the planned set, whichever is larger**,\ndrawn across the data range (best-populated, median, thinnest rows), never\nonly showcase pages. **At least 90% of the sample must pass every gate** before\ngenerating, publishing, or submitting anything beyond the sample. A failing\nsample means fix the template or shrink the set.\n\n**Index-worthiness (content)**\n- [ ] At least **5 page-unique data fields** differ from every sibling, and at\n      least one is not on any competing page you checked\n- [ ] **Template-shared text is 40% or less** of rendered body words, measured\n      on the thinnest row\n- [ ] The opening answers the query with this row's data, not generic copy\n- [ ] An original layer exists (calculation, ranking, comparison, verified\n      local detail)\n- [ ] A reader who never buys the product still leaves with something useful\n- [ ] Facts carry a source and a last-verified date\n\n**Doorway test**\n- [ ] Swap the variable (city, persona, tool) with a sibling's: if the page\n      still reads as true, it fails\n- [ ] Pages do not all funnel to one destination with nothing in between\n- [ ] No near-duplicate pages for synonyms of the same query (\"CRM for\n      realtors\" and \"CRM for real estate agents\" is one page)\n\n**Technical**\n- [ ] Unique title, meta description, and H1 per page\n- [ ] Schema validates and matches visible content\n- [ ] Core Web Vitals measured on a real sample page (field data where\n      available), not assumed\n- [ ] Mobile render checked\n\n**Linking and indexation**\n- [ ] Linked from a hub and from at least one sibling\n- [ ] In the right per-type sitemap, crawlable, no conflicting `noindex`\n\n## Rollout and KPIs\n\nShip in phases: sample, then phase 1 (the strongest rows), then expansion only\nwhen phase 1 earns it. Read these at 30 and 60 days after each phase:\n\n| KPI | Source | Expand when | Stop and fix when |\n|---|---|---|---|\n| Indexation rate (indexed \u002F submitted per sitemap) | Search Console Pages | 70% or more | Below 60% |\n| Pages with impressions \u002F pages indexed | Search Console Performance | Rising | Flat after 60 days |\n| CTR on the set vs site average | Search Console | At or above | Well below |\n| Engaged sessions per page | GA4 | Comparable to hand-built pages | Near zero |\n| Conversions from the set | GA4 | Positive and growing | None after 60 days |\n| \"Crawled, currently not indexed\" count | Search Console | Falling | Rising |\n| Manual actions | Search Console | None | Any: halt and remove |\n\nThese thresholds are Suede defaults; adjust them to the user's baseline and\nrecord the change. Hand ongoing reporting to `suede-analytics`.\n\n## Common mistakes\n\n- City or persona swapped into identical copy (doorway).\n- Pages for combinations nobody searches.\n- Stale or unverified data presented as current.\n- Canonicalizing hundreds of thin pages instead of not publishing them.\n- Generating AI-written filler to hit a word count.\n- Publishing the full set before the sample passes.\n\n## Output Contract\n\nClose every programmatic SEO pass with this block. Write the literal templates.\n\n```text\nPLAYBOOK: [name], chosen because [pattern + data fit]\nDATA DEFENSIBILITY: [tier 1-5], source, rights, provenance, refresh cadence\nORIGINAL LAYER: [what exists only because the data was combined]\nPAGE-COUNT BOUND: sample [N] -> phase 1 [N] -> ceiling [N], expansion condition [KPI threshold]\nURL: [literal pattern]   TITLE: [literal]   META: [literal]   H1: [literal]\nOPENING ANSWER TEMPLATE: [literal, with data variables]\nUNIQUENESS: [page-unique fields per page] | template-shared body text: [N%]\nDOORWAY TEST: [pass\u002Ffail on sample, examples]\nLINK PLAN: hub [URL] -> spokes [pattern] | cross-links [rule] | sitemap [file]\nSAMPLE VERDICT: [N of N pass], failing gates: [list or \"none\"]\nKPI PLAN: [metrics, sources, 30\u002F60-day thresholds]\nSHIP GATE: ship | ship-with-caveats | hold, reason\n```\n\n## Boundaries\n\n- Do not generate, publish, submit, or index a full page set before a bounded\n  sample passes. When the sample fails or was never run, name the blocking\n  gate and failing count, give 2 to 4 options (fix the template, narrow the\n  set, add data, publish the passing subset), and recommend one. Proceeding is\n  the user's call.\n- Do not invent source data, claim rankings or traffic, scrape sources whose\n  terms forbid it, or treat keyword volume as user value.\n- Do not alter production routes, templates, canonicals, sitemaps, or internal\n  links without an approved scope and current-site verification.\n\n## Routing\n\n- Audit shipped pages and technical health: `suede-seo-audit`.\n- Make the set quotable and measure AI citations: `suede-ai-seo`.\n- Editorial (non-templated) planning: `suede-content-strategy`.\n- Comparison-page evidence and framing: `suede-competitors`.\n- Interactive tools as page anchors: `suede-free-tools`.\n- Rollout reporting: `suede-analytics`.\n","# Suede AI Programmatic SEO Skills\n\n## Compatibility\n\nRequires a source dataset with reuse rights, query-pattern evidence, and page\u002Ftemplate access. Current search policies require browsing. Local planning\u002Fbuilding needs no new integration; publication requires authority.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nProgrammatic pages work when each one answers a real query with data the\nsearcher cannot get faster elsewhere. They fail, and can drag the whole site\ndown, when they are one template with a swapped city name. This skill treats\npage count as something a sample earns, never a target.\n\n## Gate policy: advisory, not blocking\n\nEvery gate and verdict here is a recommendation to the user, not a control on\nthe agent. A failed gate changes what you report, never what you do. Single\nexception: an extremely risky finding (data loss, credential exposure, legal or\nrights violations, payment mistakes, irreversible public damage) pauses for the\nuser's choice.\n\n## The policy line you must stay behind\n\nGoogle's spam policies name three patterns programmatic sites trip most:\n\n- **Scaled content abuse**: many pages generated mainly to manipulate rankings\n  or AI answers and not to help people, whatever tool produced them.\n- **Doorway abuse**: sites or pages created to rank for similar queries that\n  funnel users to the same destination (\"[service] in [city]\" pages with\n  nothing local on them).\n- **Site reputation abuse**: third-party pages published on a host site to\n  borrow its ranking signals with little first-party oversight.\n\nGoogle also says AI answers need no special pages; producing variants for AI\nis the same abuse. Every gate below exists to keep a page set on the right\nside of this line. Source: https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fessentials\u002Fspam-policies\n\n## Initial assessment\n\nRead `.agents\u002Fproduct-marketing.md` (or `.claude\u002Fproduct-marketing.md`, or the\nlegacy `product-marketing-context.md`) if present. Then establish:\n\n1. **Business**: product, audience, the conversion each page should earn.\n2. **Pattern and demand**: the repeating query pattern, its variables, how many\n   combinations have evidence of demand (Search Console, Keyword Planner, or a\n   dated export; otherwise `unknown`).\n3. **Competition**: who ranks now, what their pages contain, and whether you\n   can offer something they do not.\n4. **Data**: what populates each page, where it comes from, how often it\n   refreshes, and whether you have the rights to publish it.\n5. **Delivery**: CMS or framework, and whether it can template, split sitemaps,\n   and set `noindex` and canonicals per page.\n\n## Data defensibility\n\nThe data decides whether the set is worth building. Rank it:\n\n1. Proprietary (you created it: usage stats, tests, benchmarks)\n2. Product-derived (aggregated from your users, with consent)\n3. User-generated (reviews, submissions, community)\n4. Licensed (exclusive or contracted)\n5. Public (anyone can publish it; weakest, needs real added analysis)\n\nA set built only on tier-5 data needs an original layer (scoring, comparison,\ncalculation, local verification) or it is a doorway set.\n\n## Playbooks\n\n| Playbook | Pattern | Example |\n|---|---|---|\n| Templates | \"[type] template\" | \"invoice template\" |\n| Curation | \"best [category] for [segment]\" | \"best CRM for agencies\" |\n| Conversions | \"[X] to [Y]\" | \"kg to lbs\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [place]\" | \"coworking in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[A] [B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is churn rate\" |\n| Translations | localized versions | \"\u002Fes\u002F\", \"\u002Fde\u002F\" |\n| Directory | \"[category] tools\" | \"ai writing tools\" |\n| Profiles | \"[entity]\" or \"[entity] [attribute]\" | \"stripe pricing history\" |\n\nRead `references\u002Fplaybooks.md` when choosing, layering, or implementing one. It\nholds per-playbook value requirements, URL patterns, and the asset-to-playbook\ntable.\n\n## Implementation\n\n### 1. Pattern and demand\n\nName the pattern, the variables, and the candidate list. Keep only\ncombinations with demand evidence or a clear reader need. Combinations with no\nevidence wait for phase 2 or never ship.\n\n### 2. Data model\n\nOne row per page. Columns for every page-unique field, its source, its\nlast-verified date, and a `publish` flag computed from the gates below. Rows\nthat fail stay in the table with `publish = false`.\n\n### 3. Template\n\n- H1 and title that carry the page's variables naturally.\n- A direct answer in the opening that uses the row's own data (\"Median [metric]\n  in [city] was [value] in [month year], per [source]\"), never generic copy.\n- Data sections that render only when the row has the data (conditional\n  blocks, not empty placeholders).\n- An original layer: a calculation, ranking, comparison, or note that exists\n  only because you combined the data.\n- Related-page links and a CTA matched to intent.\n- Schema only where a supported feature fits; `BreadcrumbList` and\n  `Organization` via a shared `@id` are usually safe.\n\n### 4. Internal linking\n\n- Hub pages per category and per parent (city, industry, integration category)\n  that link to every published child.\n- Children link to the hub, to siblings that share a real relationship (nearby\n  cities, adjacent integrations), and to the main product page.\n- No orphans: every published page reachable within three or four clicks from\n  the home page through crawlable `\u003Ca href>` links.\n- Breadcrumbs, visible and marked up.\n\n### 5. Indexation\n\n- One sitemap per page type so indexation can be read per set.\n- Rows below the gates are not generated, or are generated with `noindex` and\n  left out of the sitemap until they pass.\n- Self-referencing canonicals; no canonicalizing many thin pages to one hub as\n  a substitute for not publishing them.\n- Use subfolders under the main domain unless there is a technical or\n  organizational reason for a subdomain; Google treats both as crawlable, but a\n  subdomain is managed and measured as a separate property.\n- Crawl budget matters only for very large sets (tens of thousands of URLs or\n  more); below that, quality gates are the constraint.\n\n## Quality gates\n\nRun on a **sample of 10 pages or 5% of the planned set, whichever is larger**,\ndrawn across the data range (best-populated, median, thinnest rows), never\nonly showcase pages. **At least 90% of the sample must pass every gate** before\ngenerating, publishing, or submitting anything beyond the sample. A failing\nsample means fix the template or shrink the set.\n\n**Index-worthiness (content)**\n- [ ] At least **5 page-unique data fields** differ from every sibling, and at\n      least one is not on any competing page you checked\n- [ ] **Template-shared text is 40% or less** of rendered body words, measured\n      on the thinnest row\n- [ ] The opening answers the query with this row's data, not generic copy\n- [ ] An original layer exists (calculation, ranking, comparison, verified\n      local detail)\n- [ ] A reader who never buys the product still leaves with something useful\n- [ ] Facts carry a source and a last-verified date\n\n**Doorway test**\n- [ ] Swap the variable (city, persona, tool) with a sibling's: if the page\n      still reads as true, it fails\n- [ ] Pages do not all funnel to one destination with nothing in between\n- [ ] No near-duplicate pages for synonyms of the same query (\"CRM for\n      realtors\" and \"CRM for real estate agents\" is one page)\n\n**Technical**\n- [ ] Unique title, meta description, and H1 per page\n- [ ] Schema validates and matches visible content\n- [ ] Core Web Vitals measured on a real sample page (field data where\n      available), not assumed\n- [ ] Mobile render checked\n\n**Linking and indexation**\n- [ ] Linked from a hub and from at least one sibling\n- [ ] In the right per-type sitemap, crawlable, no conflicting `noindex`\n\n## Rollout and KPIs\n\nShip in phases: sample, then phase 1 (the strongest rows), then expansion only\nwhen phase 1 earns it. Read these at 30 and 60 days after each phase:\n\n| KPI | Source | Expand when | Stop and fix when |\n|---|---|---|---|\n| Indexation rate (indexed \u002F submitted per sitemap) | Search Console Pages | 70% or more | Below 60% |\n| Pages with impressions \u002F pages indexed | Search Console Performance | Rising | Flat after 60 days |\n| CTR on the set vs site average | Search Console | At or above | Well below |\n| Engaged sessions per page | GA4 | Comparable to hand-built pages | Near zero |\n| Conversions from the set | GA4 | Positive and growing | None after 60 days |\n| \"Crawled, currently not indexed\" count | Search Console | Falling | Rising |\n| Manual actions | Search Console | None | Any: halt and remove |\n\nThese thresholds are Suede defaults; adjust them to the user's baseline and\nrecord the change. Hand ongoing reporting to `suede-analytics`.\n\n## Common mistakes\n\n- City or persona swapped into identical copy (doorway).\n- Pages for combinations nobody searches.\n- Stale or unverified data presented as current.\n- Canonicalizing hundreds of thin pages instead of not publishing them.\n- Generating AI-written filler to hit a word count.\n- Publishing the full set before the sample passes.\n\n## Output Contract\n\nClose every programmatic SEO pass with this block. Write the literal templates.\n\n```text\nPLAYBOOK: [name], chosen because [pattern + data fit]\nDATA DEFENSIBILITY: [tier 1-5], source, rights, provenance, refresh cadence\nORIGINAL LAYER: [what exists only because the data was combined]\nPAGE-COUNT BOUND: sample [N] -> phase 1 [N] -> ceiling [N], expansion condition [KPI threshold]\nURL: [literal pattern]   TITLE: [literal]   META: [literal]   H1: [literal]\nOPENING ANSWER TEMPLATE: [literal, with data variables]\nUNIQUENESS: [page-unique fields per page] | template-shared body text: [N%]\nDOORWAY TEST: [pass\u002Ffail on sample, examples]\nLINK PLAN: hub [URL] -> spokes [pattern] | cross-links [rule] | sitemap [file]\nSAMPLE VERDICT: [N of N pass], failing gates: [list or \"none\"]\nKPI PLAN: [metrics, sources, 30\u002F60-day thresholds]\nSHIP GATE: ship | ship-with-caveats | hold, reason\n```\n\n## Boundaries\n\n- Do not generate, publish, submit, or index a full page set before a bounded\n  sample passes. When the sample fails or was never run, name the blocking\n  gate and failing count, give 2 to 4 options (fix the template, narrow the\n  set, add data, publish the passing subset), and recommend one. Proceeding is\n  the user's call.\n- Do not invent source data, claim rankings or traffic, scrape sources whose\n  terms forbid it, or treat keyword volume as user value.\n- Do not alter production routes, templates, canonicals, sitemaps, or internal\n  links without an approved scope and current-site verification.\n\n## Routing\n\n- Audit shipped pages and technical health: `suede-seo-audit`.\n- Make the set quotable and measure AI citations: `suede-ai-seo`.\n- Editorial (non-templated) planning: `suede-content-strategy`.\n- Comparison-page evidence and framing: `suede-competitors`.\n- Interactive tools as page anchors: `suede-free-tools`.\n- Rollout reporting: `suede-analytics`.\n",{"name":5,"metadata":55,"description":7},{"version":56,"display-name":57},"3.0.1","Suede AI Programmatic SEO Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-programmatic-seo",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-programmatic-seo",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-programmatic-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002FSKILL.md",true,[82,88,92,96,100],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"agents\u002Fopenai.yaml","REFERENCE","参考文档",579,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002Fagents\u002Fopenai.yaml",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"CARD.md",4541,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002FCARD.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Fevals.json",7312,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002Fevals\u002Fevals.json",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fplaybooks.md",8401,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002Freferences\u002Fplaybooks.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fworked-contract.md",2084,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-programmatic-seo\u002Freferences\u002Fworked-contract.md",[105,115,123,131,139,147],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":114},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":114},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":114},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":114},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":114},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":114},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]