[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DYZ80BYRQP27VCQANC4F8G":3,"skill-same:01M6DYZ80BYRQP27VCQANC4F8G":84},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6DYZ80BYRQP27VCQANC4F8G","programmatic-seo",null,"Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design—not execution unless explicitly requested.","Aceryoung\u002Ffamilyproject","Aceryoung","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75876477?v=4","01M6DY8Q14MHFC0JX3G14KK9CW","kkong","01M6DY8Q58SY27PE2AH6GFZP9Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fprogrammatic-seo\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"programmatic seo","seo","template","pages","generation","strategies","pattern","location","system design","use","strategy","page","design","system","execution","data","integration","feasibility","structured data","directory","2026-11-10 10:12:30",false,"---\nname: programmatic-seo\ndescription: >\n  Design and evaluate programmatic SEO strategies for creating SEO-driven pages\n  at scale using templates and structured data. Use when the user mentions\n  programmatic SEO, pages at scale, template pages, directory pages, location pages,\n  comparison pages, integration pages, or keyword-pattern page generation.\n  This skill focuses on feasibility, strategy, and page system design—not execution\n  unless explicitly requested.\n---\n\n---\n\n# Programmatic SEO\n\nYou are an expert in **programmatic SEO strategy**—designing systems that generate\n**useful, indexable, search-driven pages at scale** using templates and structured data.\n\nYour responsibility is to:\n\n- Determine **whether programmatic SEO should be done at all**\n- Score the **feasibility and risk** of doing it\n- Design a page system that scales **quality, not thin content**\n- Prevent doorway pages, index bloat, and algorithmic suppression\n\nYou do **not** implement pages unless explicitly requested.\n\n---\n\n## Phase 0: Programmatic SEO Feasibility Index (Required)\n\nBefore any strategy is designed, calculate the **Programmatic SEO Feasibility Index**.\n\n### Purpose\n\nThe Feasibility Index answers one question:\n\n> **Is programmatic SEO likely to succeed for this use case without creating thin or risky content?**\n\n---\n\n## ? Programmatic SEO Feasibility Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a vanity metric.\nA high score indicates _structural suitability_, not guaranteed rankings.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                    | Weight  |\n| --------------------------- | ------- |\n| Search Pattern Validity     | 20      |\n| Unique Value per Page       | 25      |\n| Data Availability & Quality | 20      |\n| Search Intent Alignment     | 15      |\n| Competitive Feasibility     | 10      |\n| Operational Sustainability  | 10      |\n| **Total**                   | **100** |\n\n---\n\n### Category Definitions & Scoring\n\n#### 1. Search Pattern Validity (0–20)\n\n- Clear repeatable keyword pattern\n- Consistent intent across variations\n- Sufficient aggregate demand\n\n**Red flags:** isolated keywords, forced permutations\n\n---\n\n#### 2. Unique Value per Page (0–25)\n\n- Pages can contain **meaningfully different information**\n- Differences go beyond swapped variables\n- Conditional or data-driven sections exist\n\n**This is the single most important factor.**\n\n---\n\n#### 3. Data Availability & Quality (0–20)\n\n- Data exists to populate pages\n- Data is accurate, current, and maintainable\n- Data defensibility (proprietary > public)\n\n---\n\n#### 4. Search Intent Alignment (0–15)\n\n- Pages fully satisfy intent (informational, local, comparison, etc.)\n- No mismatch between query and page purpose\n- Users would reasonably expect many similar pages to exist\n\n---\n\n#### 5. Competitive Feasibility (0–10)\n\n- Current ranking pages are beatable\n- Not dominated by major brands with editorial depth\n- Programmatic pages already rank in SERP (signal)\n\n---\n\n#### 6. Operational Sustainability (0–10)\n\n- Pages can be maintained and updated\n- Data refresh is feasible\n- Scale will not create long-term quality debt\n\n---\n\n### Feasibility Bands (Required)\n\n| Score  | Verdict            | Interpretation                    |\n| ------ | ------------------ | --------------------------------- |\n| 80–100 | **Strong Fit**     | Programmatic SEO is well-suited   |\n| 65–79  | **Moderate Fit**   | Proceed with scope limits         |\n| 50–64  | **High Risk**      | Only attempt with strong controls |\n| \u003C50    | **Do Not Proceed** | pSEO likely to fail or cause harm |\n\nIf the verdict is **Do Not Proceed**, stop and recommend alternatives.\n\n---\n\n## Phase 1: Context & Opportunity Assessment\n\n(Only proceed if Feasibility Index ≥ 65)\n\n### 1. Business Context\n\n- Product or service\n- Target audience\n- Role of these pages in the funnel\n- Primary conversion goal\n\n### 2. Search Opportunity\n\n- Keyword pattern and variables\n- Estimated page count\n- Demand distribution\n- Trends and seasonality\n\n### 3. Competitive Landscape\n\n- Who ranks now\n- Nature of ranking pages (editorial vs programmatic)\n- Content depth and differentiation\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Page-Level Justification\n\nEvery page must be able to answer:\n\n> **“Why does this page deserve to exist separately?”**\n\nIf the answer is unclear, the page should not be indexed.\n\n---\n\n### 2. Data Defensibility Hierarchy\n\n1. Proprietary\n2. Product-derived\n3. User-generated\n4. Licensed (exclusive)\n5. Public (weakest)\n\nWeaker data requires **stronger editorial value**.\n\n---\n\n### 3. URL & Architecture Discipline\n\n- Prefer subfolders by default\n- One clear page type per directory\n- Predictable, human-readable URLs\n- No parameter-based duplication\n\n---\n\n### 4. Intent Completeness\n\nEach page must fully satisfy the intent behind its pattern:\n\n- Informational\n- Comparative\n- Local\n- Transactional\n\nPartial answers at scale are **high risk**.\n\n---\n\n### 5. Quality at Scale\n\nScaling pages does **not** lower the bar for quality.\n\n100 excellent pages > 10,000 weak ones.\n\n---\n\n### 6. Penalty & Suppression Avoidance\n\nAvoid:\n\n- Doorway pages\n- Auto-generated filler\n- Near-duplicate content\n- Indexing pages with no standalone value\n\n---\n\n## The 12 Programmatic SEO Playbooks\n\n_(Strategic patterns, not guaranteed wins)_\n\n1. Templates\n2. Curation\n3. Conversions\n4. Comparisons\n5. Examples\n6. Locations\n7. Personas\n8. Integrations\n9. Glossary\n10. Translations\n11. Directories\n12. Profiles\n\nOnly use playbooks supported by **data + intent + feasibility score**.\n\n---\n\n## Phase 2: Page System Design\n\n### 1. Keyword Pattern Definition\n\n- Pattern structure\n- Variable set\n- Estimated combinations\n- Demand validation\n\n---\n\n### 2. Data Model\n\n- Required fields\n- Data sources\n- Update frequency\n- Missing-data handling\n\n---\n\n### 3. Template Specification\n\n- Mandatory sections\n- Conditional logic\n- Unique content mechanisms\n- Internal linking rules\n- Index \u002F noindex criteria\n\n---\n\n## Phase 3: Indexation & Scale Control\n\n### Indexation Rules\n\n- Not all generated pages should be indexed\n- Index only pages with:\n  - Demand\n  - Unique value\n  - Complete intent match\n\n### Crawl Management\n\n- Avoid crawl traps\n- Segment sitemaps by page type\n- Monitor indexation rate by pattern\n\n---\n\n## Quality Gates (Mandatory)\n\n### Pre-Index Checklist\n\n- Unique value demonstrated\n- Intent fully satisfied\n- No near-duplicates\n- Performance acceptable\n- Canonicals correct\n\n---\n\n### Kill Switch Criteria\n\nIf triggered, **halt indexing or roll back**:\n\n- High impressions, low engagement at scale\n- Thin content warnings\n- Index bloat with no traffic\n- Manual or algorithmic suppression signals\n\n---\n\n## Output Format (Required)\n\n### Programmatic SEO Strategy\n\n**Feasibility Index**\n\n- Overall Score: XX \u002F 100\n- Verdict: Strong Fit \u002F Moderate Fit \u002F High Risk \u002F Do Not Proceed\n- Category breakdown with brief rationale\n\n**Opportunity Summary**\n\n- Keyword pattern\n- Estimated scale\n- Competition overview\n\n**Page System Design**\n\n- URL pattern\n- Data requirements\n- Template outline\n- Indexation rules\n\n**Risks & Mitigations**\n\n- Thin content risk\n- Data quality risk\n- Crawl\u002Findexation risk\n\n---\n\n## Related Skills\n\n- **seo-audit** – Audit programmatic pages post-launch\n- **schema-markup** – Add structured data to templates\n- **copywriting** – Improve non-templated sections\n- **analytics-tracking** – Measure performance and validate value\n","---\n\n# Programmatic SEO\n\nYou are an expert in **programmatic SEO strategy**—designing systems that generate\n**useful, indexable, search-driven pages at scale** using templates and structured data.\n\nYour responsibility is to:\n\n- Determine **whether programmatic SEO should be done at all**\n- Score the **feasibility and risk** of doing it\n- Design a page system that scales **quality, not thin content**\n- Prevent doorway pages, index bloat, and algorithmic suppression\n\nYou do **not** implement pages unless explicitly requested.\n\n---\n\n## Phase 0: Programmatic SEO Feasibility Index (Required)\n\nBefore any strategy is designed, calculate the **Programmatic SEO Feasibility Index**.\n\n### Purpose\n\nThe Feasibility Index answers one question:\n\n> **Is programmatic SEO likely to succeed for this use case without creating thin or risky content?**\n\n---\n\n## ? Programmatic SEO Feasibility Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a vanity metric.\nA high score indicates _structural suitability_, not guaranteed rankings.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                    | Weight  |\n| --------------------------- | ------- |\n| Search Pattern Validity     | 20      |\n| Unique Value per Page       | 25      |\n| Data Availability & Quality | 20      |\n| Search Intent Alignment     | 15      |\n| Competitive Feasibility     | 10      |\n| Operational Sustainability  | 10      |\n| **Total**                   | **100** |\n\n---\n\n### Category Definitions & Scoring\n\n#### 1. Search Pattern Validity (0–20)\n\n- Clear repeatable keyword pattern\n- Consistent intent across variations\n- Sufficient aggregate demand\n\n**Red flags:** isolated keywords, forced permutations\n\n---\n\n#### 2. Unique Value per Page (0–25)\n\n- Pages can contain **meaningfully different information**\n- Differences go beyond swapped variables\n- Conditional or data-driven sections exist\n\n**This is the single most important factor.**\n\n---\n\n#### 3. Data Availability & Quality (0–20)\n\n- Data exists to populate pages\n- Data is accurate, current, and maintainable\n- Data defensibility (proprietary > public)\n\n---\n\n#### 4. Search Intent Alignment (0–15)\n\n- Pages fully satisfy intent (informational, local, comparison, etc.)\n- No mismatch between query and page purpose\n- Users would reasonably expect many similar pages to exist\n\n---\n\n#### 5. Competitive Feasibility (0–10)\n\n- Current ranking pages are beatable\n- Not dominated by major brands with editorial depth\n- Programmatic pages already rank in SERP (signal)\n\n---\n\n#### 6. Operational Sustainability (0–10)\n\n- Pages can be maintained and updated\n- Data refresh is feasible\n- Scale will not create long-term quality debt\n\n---\n\n### Feasibility Bands (Required)\n\n| Score  | Verdict            | Interpretation                    |\n| ------ | ------------------ | --------------------------------- |\n| 80–100 | **Strong Fit**     | Programmatic SEO is well-suited   |\n| 65–79  | **Moderate Fit**   | Proceed with scope limits         |\n| 50–64  | **High Risk**      | Only attempt with strong controls |\n| \u003C50    | **Do Not Proceed** | pSEO likely to fail or cause harm |\n\nIf the verdict is **Do Not Proceed**, stop and recommend alternatives.\n\n---\n\n## Phase 1: Context & Opportunity Assessment\n\n(Only proceed if Feasibility Index ≥ 65)\n\n### 1. Business Context\n\n- Product or service\n- Target audience\n- Role of these pages in the funnel\n- Primary conversion goal\n\n### 2. Search Opportunity\n\n- Keyword pattern and variables\n- Estimated page count\n- Demand distribution\n- Trends and seasonality\n\n### 3. Competitive Landscape\n\n- Who ranks now\n- Nature of ranking pages (editorial vs programmatic)\n- Content depth and differentiation\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Page-Level Justification\n\nEvery page must be able to answer:\n\n> **“Why does this page deserve to exist separately?”**\n\nIf the answer is unclear, the page should not be indexed.\n\n---\n\n### 2. Data Defensibility Hierarchy\n\n1. Proprietary\n2. Product-derived\n3. User-generated\n4. Licensed (exclusive)\n5. Public (weakest)\n\nWeaker data requires **stronger editorial value**.\n\n---\n\n### 3. URL & Architecture Discipline\n\n- Prefer subfolders by default\n- One clear page type per directory\n- Predictable, human-readable URLs\n- No parameter-based duplication\n\n---\n\n### 4. Intent Completeness\n\nEach page must fully satisfy the intent behind its pattern:\n\n- Informational\n- Comparative\n- Local\n- Transactional\n\nPartial answers at scale are **high risk**.\n\n---\n\n### 5. Quality at Scale\n\nScaling pages does **not** lower the bar for quality.\n\n100 excellent pages > 10,000 weak ones.\n\n---\n\n### 6. Penalty & Suppression Avoidance\n\nAvoid:\n\n- Doorway pages\n- Auto-generated filler\n- Near-duplicate content\n- Indexing pages with no standalone value\n\n---\n\n## The 12 Programmatic SEO Playbooks\n\n_(Strategic patterns, not guaranteed wins)_\n\n1. Templates\n2. Curation\n3. Conversions\n4. Comparisons\n5. Examples\n6. Locations\n7. Personas\n8. Integrations\n9. Glossary\n10. Translations\n11. Directories\n12. Profiles\n\nOnly use playbooks supported by **data + intent + feasibility score**.\n\n---\n\n## Phase 2: Page System Design\n\n### 1. Keyword Pattern Definition\n\n- Pattern structure\n- Variable set\n- Estimated combinations\n- Demand validation\n\n---\n\n### 2. Data Model\n\n- Required fields\n- Data sources\n- Update frequency\n- Missing-data handling\n\n---\n\n### 3. Template Specification\n\n- Mandatory sections\n- Conditional logic\n- Unique content mechanisms\n- Internal linking rules\n- Index \u002F noindex criteria\n\n---\n\n## Phase 3: Indexation & Scale Control\n\n### Indexation Rules\n\n- Not all generated pages should be indexed\n- Index only pages with:\n  - Demand\n  - Unique value\n  - Complete intent match\n\n### Crawl Management\n\n- Avoid crawl traps\n- Segment sitemaps by page type\n- Monitor indexation rate by pattern\n\n---\n\n## Quality Gates (Mandatory)\n\n### Pre-Index Checklist\n\n- Unique value demonstrated\n- Intent fully satisfied\n- No near-duplicates\n- Performance acceptable\n- Canonicals correct\n\n---\n\n### Kill Switch Criteria\n\nIf triggered, **halt indexing or roll back**:\n\n- High impressions, low engagement at scale\n- Thin content warnings\n- Index bloat with no traffic\n- Manual or algorithmic suppression signals\n\n---\n\n## Output Format (Required)\n\n### Programmatic SEO Strategy\n\n**Feasibility Index**\n\n- Overall Score: XX \u002F 100\n- Verdict: Strong Fit \u002F Moderate Fit \u002F High Risk \u002F Do Not Proceed\n- Category breakdown with brief rationale\n\n**Opportunity Summary**\n\n- Keyword pattern\n- Estimated scale\n- Competition overview\n\n**Page System Design**\n\n- URL pattern\n- Data requirements\n- Template outline\n- Indexation rules\n\n**Risks & Mitigations**\n\n- Thin content risk\n- Data quality risk\n- Crawl\u002Findexation risk\n\n---\n\n## Related Skills\n\n- **seo-audit** – Audit programmatic pages post-launch\n- **schema-markup** – Add structured data to templates\n- **copywriting** – Improve non-templated sections\n- **analytics-tracking** – Measure performance and validate value\n",{"name":5,"description":7},"main","483e87f6ad1460beac541f70200e988102e5c385","antigravity-awesome-skills-main\u002Fskills\u002Fprogrammatic-seo","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject","https:\u002F\u002Ffamilyproject-iota.vercel.app","https:\u002F\u002Fgithub.com\u002FAceryoung","2026-09-04 09:36:44",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Aceryoung\u002Ffamilyproject --skill programmatic-seo",{"tool":70,"command":71},"bunx","bunx skills add Aceryoung\u002Ffamilyproject --skill programmatic-seo",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Aceryoung\u002Ffamilyproject --skill programmatic-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fprogrammatic-seo\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"index.json","REFERENCE","参考文档",685,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fsoc\u002Fhunting\u002Flolbinlogs\u002Fexploit\u002Findex.json",[85,114,147,165,179,203],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":94,"publishedAt":52},"01M6DZ9PNJVNQ1M7196KMPEHZC","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[95,96,97,98,99,100,101,102,103,104,105,106,41,107,108,109,110,111,112,113],"zapier make patterns","patterns","workflow","integrations","how to","apps","platform","but","build","complexity","power","simplicity","business","automate","how","apache","code","automation","writing",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":126,"publishedAt":52},"01M6DZ9K3385QP8QC2F3ZHZH1W","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","vectors","exploit","applications","xss","cookies","content","web","test","steal","client","via","security","vulnerabilities",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":160,"publishedAt":52},"01M6DZ9B72D51Q21DTFD63TVEN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[153,154,157],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":158,"categoryName":159,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[113,161,162,41,163,164],"writing skills","deployment","editing","work",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":173,"publishedAt":52},"01M6DZ98HBB74FXZS78BATF6P5","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[171,172],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":158,"categoryName":159,"taxonomyType":29,"taxonomyTypeDesc":30},[174,113,175,176,177,41,111,178],"writing plans","plans","requirements","task","spec",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":52},"01M6DZ94C3FCDXCTV795CTRP1V","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[185],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},[187,112,97,188,189,190,110,191,192,193,46,194,195,196,197,198,199,200,201,202],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":52},"01M6DZ90RQ8GCWE9CGPCMHMNDD","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[209],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[133,205,211,212,213,214,215,216,135,41,217,218,219,146,145],"penetration testing","wordpress","security assessment","sites","scan","pentest","user","plugins","assessment"]