[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADBF0PR5WWVPJSV87FPJ8R":3,"skill-same:01M6ADBF0PR5WWVPJSV87FPJ8R":88},{"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":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6ADBF0PR5WWVPJSV87FPJ8R","content-management-systems",null,"Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-management-systems\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"content","content management systems","management","systems","modules","when","static","manager","adobe","themes","panels","apps","across","woocommerce","hubspot","wordpress","export","markdown","Media","cms","plugins","admin","workflows","workflow","2026-11-10 10:12:30",false,"---\nname: content-management-systems\ndescription: 'Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.'\n---\n\n# Content Management Systems\n\nUse this skill when the user is working on a content management system or on software that behaves like one.\n\nThis skill focuses on the seams that matter in CMS work:\n\n- themes and templates\n- plugins, apps, modules, and extensions\n- admin and editor interfaces\n- media and upload handling\n- content models, taxonomy, and metadata\n- render pipelines and static export flows\n\n## When to Use This Skill\n\n- The user mentions a CMS platform such as WordPress, Shopify, Drupal, Joomla, Webflow, Squarespace, Wix, WooCommerce, HubSpot CMS Hub, or Adobe Experience Manager.\n- The task is about theme development, template changes, or design system work inside a CMS.\n- The task is about plugins, modules, apps, or extension points.\n- The task touches editor UX, previews, taxonomy, slugs, SEO fields, or publishing behavior.\n- The task involves uploads, media libraries, authored assets, markdown rendering, or static export.\n\n## First Pass\n\n1. Identify the platform category: self-hosted CMS, SaaS site builder, commerce platform, or hybrid\u002Fheadless system.\n2. Find the owning implementation seam before editing:\n   - theme or template layer\n   - plugin, app, module, or extension layer\n   - admin or editor surface\n   - content model or storage layer\n   - media pipeline\n   - export, deploy, or rendering pipeline\n3. Check platform constraints before choosing an approach:\n   - what is editable locally\n   - what is authored content versus code\n   - where media belongs\n   - whether the final site is server-rendered, static-exported, or hosted remotely\n\n## CMS Rules\n\n- Follow the platform's naming and folder conventions for themes, modules, template parts, or sections.\n- Keep theme assets separate from user-uploaded media unless the platform explicitly combines them.\n- Prefer structured content fields over storing important metadata inside presentation markup.\n- Treat previews, slugs, taxonomy, excerpts, meta fields, and publish states as first-class CMS concerns.\n- Prefer safe defaults and graceful fallback behavior when config, theme selection, or content input is invalid.\n- When changing editor or admin behavior, trace the stored field, validation rules, preview path, and final render path together.\n\n## Common Workflows\n\n### Themes and Templates\n\n- Start at the template loader or theme runtime, not at a downstream include.\n- Preserve the platform's template hierarchy and partial naming conventions.\n- Keep presentation changes close to templates and shared theme helpers.\n\n### Plugins, Apps, and Modules\n\n- Add behavior at the platform's extension seam instead of scattering logic into templates.\n- Keep migrations, seed data, and configuration updates explicit and versioned.\n- Document the extension's setup assumptions when the platform requires activation or registration.\n\n### Admin and Editor UX\n\n- Keep forms aligned with the stored content model.\n- Prefer author-facing previews when content transformations are non-trivial.\n- Keep validation, CSRF or equivalent safeguards, and permissions consistent with the surrounding admin code.\n\n### Media and Uploads\n\n- Use a dedicated upload path for authored media.\n- Keep decorative or theme-owned imagery in the active theme folder.\n- Default to conventional locations like `uploads\u002F` for authored media and `img\u002F` for theme assets unless the platform dictates a stronger convention.\n- When a CMS supports configurable media directories, expose the setting with a safe fallback.\n\n### Content Models and Migrations\n\n- Distinguish content entities clearly: pages, posts, products, entries, collections, taxonomies, and settings.\n- Prefer migration files or exportable schema definitions over ad hoc runtime mutations.\n- Keep slugs, publish dates, excerpts, canonical metadata, and taxonomy relations structured.\n\n### Markdown, HTML, and Static Export\n\n- Decide whether markdown is authored input, intermediate content, or build output before changing the renderer.\n- Pair renderer changes with preview or validation when feasible.\n- For static-exported CMS systems, validate rewritten permalinks and asset paths after build changes.\n\n## Identifying the Owning Seam\n\nRegardless of platform, locate the owning seam before editing by mapping the codebase to these CMS roles:\n\n- Runtime bootstrap and request routing\n- Admin or editor controllers and their view templates\n- Theme loading, template hierarchy, and shared template helpers\n- Repositories, models, or schema\u002Fmigration files for content, taxonomy, and settings\n- Markdown or content transformation utilities\n- Static export, deploy, or render pipeline entry points\n\nStep to the owning seam first, then make the smallest change that preserves the CMS structure.\n\n## Platform Notes\n\nSee `references\u002Fcms-platform-workflows.md` for a compact mapping of common CMS platforms, extension surfaces, and media conventions.\n","# Content Management Systems\n\nUse this skill when the user is working on a content management system or on software that behaves like one.\n\nThis skill focuses on the seams that matter in CMS work:\n\n- themes and templates\n- plugins, apps, modules, and extensions\n- admin and editor interfaces\n- media and upload handling\n- content models, taxonomy, and metadata\n- render pipelines and static export flows\n\n## When to Use This Skill\n\n- The user mentions a CMS platform such as WordPress, Shopify, Drupal, Joomla, Webflow, Squarespace, Wix, WooCommerce, HubSpot CMS Hub, or Adobe Experience Manager.\n- The task is about theme development, template changes, or design system work inside a CMS.\n- The task is about plugins, modules, apps, or extension points.\n- The task touches editor UX, previews, taxonomy, slugs, SEO fields, or publishing behavior.\n- The task involves uploads, media libraries, authored assets, markdown rendering, or static export.\n\n## First Pass\n\n1. Identify the platform category: self-hosted CMS, SaaS site builder, commerce platform, or hybrid\u002Fheadless system.\n2. Find the owning implementation seam before editing:\n   - theme or template layer\n   - plugin, app, module, or extension layer\n   - admin or editor surface\n   - content model or storage layer\n   - media pipeline\n   - export, deploy, or rendering pipeline\n3. Check platform constraints before choosing an approach:\n   - what is editable locally\n   - what is authored content versus code\n   - where media belongs\n   - whether the final site is server-rendered, static-exported, or hosted remotely\n\n## CMS Rules\n\n- Follow the platform's naming and folder conventions for themes, modules, template parts, or sections.\n- Keep theme assets separate from user-uploaded media unless the platform explicitly combines them.\n- Prefer structured content fields over storing important metadata inside presentation markup.\n- Treat previews, slugs, taxonomy, excerpts, meta fields, and publish states as first-class CMS concerns.\n- Prefer safe defaults and graceful fallback behavior when config, theme selection, or content input is invalid.\n- When changing editor or admin behavior, trace the stored field, validation rules, preview path, and final render path together.\n\n## Common Workflows\n\n### Themes and Templates\n\n- Start at the template loader or theme runtime, not at a downstream include.\n- Preserve the platform's template hierarchy and partial naming conventions.\n- Keep presentation changes close to templates and shared theme helpers.\n\n### Plugins, Apps, and Modules\n\n- Add behavior at the platform's extension seam instead of scattering logic into templates.\n- Keep migrations, seed data, and configuration updates explicit and versioned.\n- Document the extension's setup assumptions when the platform requires activation or registration.\n\n### Admin and Editor UX\n\n- Keep forms aligned with the stored content model.\n- Prefer author-facing previews when content transformations are non-trivial.\n- Keep validation, CSRF or equivalent safeguards, and permissions consistent with the surrounding admin code.\n\n### Media and Uploads\n\n- Use a dedicated upload path for authored media.\n- Keep decorative or theme-owned imagery in the active theme folder.\n- Default to conventional locations like `uploads\u002F` for authored media and `img\u002F` for theme assets unless the platform dictates a stronger convention.\n- When a CMS supports configurable media directories, expose the setting with a safe fallback.\n\n### Content Models and Migrations\n\n- Distinguish content entities clearly: pages, posts, products, entries, collections, taxonomies, and settings.\n- Prefer migration files or exportable schema definitions over ad hoc runtime mutations.\n- Keep slugs, publish dates, excerpts, canonical metadata, and taxonomy relations structured.\n\n### Markdown, HTML, and Static Export\n\n- Decide whether markdown is authored input, intermediate content, or build output before changing the renderer.\n- Pair renderer changes with preview or validation when feasible.\n- For static-exported CMS systems, validate rewritten permalinks and asset paths after build changes.\n\n## Identifying the Owning Seam\n\nRegardless of platform, locate the owning seam before editing by mapping the codebase to these CMS roles:\n\n- Runtime bootstrap and request routing\n- Admin or editor controllers and their view templates\n- Theme loading, template hierarchy, and shared template helpers\n- Repositories, models, or schema\u002Fmigration files for content, taxonomy, and settings\n- Markdown or content transformation utilities\n- Static export, deploy, or render pipeline entry points\n\nStep to the owning seam first, then make the smallest change that preserves the CMS structure.\n\n## Platform Notes\n\nSee `references\u002Fcms-platform-workflows.md` for a compact mapping of common CMS platforms, extension surfaces, and media conventions.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcontent-management-systems",5335,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-11 11:59:04",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add github\u002Fawesome-copilot --skill content-management-systems",{"tool":74,"command":75},"bunx","bunx skills add github\u002Fawesome-copilot --skill content-management-systems",{"tool":77,"command":78},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill content-management-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-management-systems\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fcms-platform-workflows.md","REFERENCE","参考文档",3314,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-management-systems\u002Freferences\u002Fcms-platform-workflows.md",[89,119,147,173,207,224],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":99,"publishedAt":53},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[95,98],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[100,101,102,103,104,34,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":53},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[125],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"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":151,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":53},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[158,159,160,161,162,163,133,104,164,165,166,167,168,169,170,115,40,171,172,51],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","Legacy","debugging",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":53},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[180,183],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":155,"categoryName":156,"taxonomyType":26,"taxonomyTypeDesc":27},[185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,34,200,201,202,203,204,133,205,206],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":211,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":220,"publishedAt":53},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[215,216,219],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[221,130,194,222,223],"resemble detect","https","identity",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":211,"licenseFileUrl":228,"sourceHtmlUrl":229,"categories":230,"keywords":235,"publishedAt":53},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[231,234],{"categoryNo":232,"categoryName":233,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[236,237,238,239,159,105,9,129,240,241,222,242,243,244,245,246,247,248,249,250,251,252,113,253,254,255,256],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]