[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADP3E9PYRBP4T44CWNP3G8":3,"skill-same:01M6ADP3E9PYRBP4T44CWNP3G8":97},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6ADP3E9PYRBP4T44CWNP3G8","gtm-developer-ecosystem",null,"Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgtm-developer-ecosystem\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,9,36,37,38,39,40,41,42],"developer","gtm developer ecosystem","ecosystem","gtm","build","program","when","student","scale","platform","scaling","ecosystems","use","technical","linkedin","open","adoption","https","product","2026-11-10 10:12:30",false,"---\nname: gtm-developer-ecosystem\ndescription: Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.\nlicense: MIT\nmetadata:\n  author: Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)\n  source: https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm\n---\n\n# Developer Ecosystem\n\nBuild and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.\n\n## When to Use\n\n**Triggers:**\n- \"How do we build a developer ecosystem?\"\n- \"Should we curate quality or go open?\"\n- \"Developer community isn't growing\"\n- \"Nobody's building on our API\"\n- \"How do we compete with larger platforms?\"\n\n**Context:**\n- API platforms and developer tools\n- Products with extensibility (plugins, integrations)\n- Developer-first GTM motion\n- Platform business models\n\n---\n\n## Core Frameworks\n\n### 1. Open vs Curated Ecosystem (The Marketplace Decision)\n\n**The Pattern:**\n\nRunning ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality?\n\n**Quality control camp:** \"We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage.\"\n\n**Open camp:** \"Developers route around gatekeepers. Network effects matter more than quality control.\"\n\n**The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping.\n\n**What We Built Instead of Gatekeeping:**\n\n1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation\n2. **Trust signals** — Verified badges, usage stats, health scores\n3. **Community curation** — User ratings, collections, recommendations\n4. **Moderation** — Remove spam after publication, not block before\n\n**Result:** Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.\n\n**Decision Framework:**\n- **Curated** works when: Brand risk high, dozens of partners, can scale human review\n- **Open** works when: Hundreds\u002Fthousands of potential partners, network effects matter more than quality control\n\n**Common Mistake:**\n\nDefaulting to curated because \"we need quality control.\" This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead.\n\n---\n\n### 2. The Three-Year Student Program Arc\n\n**The Pattern:**\n\nMost developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.\n\n**Year 1: University Partnerships**\n- Partner with CS departments\n- Curriculum integration (hackathons, coursework)\n- Student licenses (free or heavily discounted)\n- Metrics: # universities, # students activated\n\n**Year 2: Student Community & Certification**\n- Student expert certification program\n- Student-led workshops and events\n- Campus ambassadors\n- Metrics: # certified, # student-led events\n\n**Year 3: Career Bridge**\n- Job board connecting students → companies\n- Enterprise partnerships (hire certified students)\n- Alumni network\n- Metrics: # hired, company partnerships\n\n**Why This Works:**\n\nStudents become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.\n\n**Common Mistake:**\n\nTreating students as immediate revenue. They're not. They're future enterprise decision-makers.\n\n---\n\n### 3. Developer Journey (Awareness → Integration → Advocacy)\n\n**Stage 1: Awareness**\n- How do they discover you?\n- Content, search, word-of-mouth, events\n\n**Stage 2: Onboarding**\n- First API call in \u003C10 minutes\n- Quick-start guides\n- Sample code in popular languages\n\n**Stage 3: Integration**\n- Building real use cases\n- Integration guides\n- Support when stuck\n\n**Stage 4: Production**\n- Deployed and generating value\n- Monitoring usage\n- Enterprise upgrade path\n\n**Stage 5: Advocacy**\n- Sharing publicly\n- Recommending to others\n- Contributing back (docs, code, community)\n\n**Metrics That Matter:**\n- Time to first API call (onboarding)\n- % reaching production (integration success)\n- Monthly active developers (engagement)\n- Developer NPS (advocacy)\n\n**Common Mistake:**\n\nMeasuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).\n\n---\n\n### 4. Documentation Hierarchy\n\n**Tier 1: Quick Starts (Get to Value Fast)**\n- \"Hello World\" in 5 minutes\n- Common use case examples\n- Copy-paste code that works\n\n**Tier 2: Guides (Solve Real Problems)**\n- Use case-specific tutorials\n- Integration patterns\n- Best practices\n\n**Tier 3: Reference (Complete API Docs)**\n- Every endpoint documented\n- Request\u002Fresponse examples\n- Error codes and handling\n\n**Tier 4: Conceptual (Understand the System)**\n- Architecture overviews\n- Design philosophy\n- Advanced patterns\n\n**Most developers need:** Tier 1 first, then Tier 2. Very few read Tier 4.\n\n**Common Mistake:**\n\nStarting with Tier 3 (comprehensive API reference). Developers want quick wins first.\n\n---\n\n### 5. Community vs Support (When to Use Which)\n\n**Community (Async, Scalable):**\n- Slack\u002FDiscord for real-time help\n- Forum for searchable Q&A\n- GitHub discussions for feature requests\n- Best for: Common questions, peer-to-peer help\n\n**Support (Sync, Expensive):**\n- Email support for enterprise\n- Dedicated Slack channels for partners\n- Video calls for complex integrations\n- Best for: Paying customers, strategic partners\n\n**How to Route:**\n\n**Community first:**\n- Developer asks question\n- Community member answers\n- You validate and upvote\n- Searchable for future developers\n\n**Escalate to support when:**\n- No community answer in 24 hours\n- Enterprise\u002Fpaying customer\n- Security or compliance issue\n- Complex integration requiring custom work\n\n**Common Mistake:**\n\nProviding white-glove support to everyone. Doesn't scale. Build community that helps itself.\n\n---\n\n### 6. Partner Tiering for Developer Ecosystems\n\n**Tier 1: Integration Partners (Self-Serve)**\n- Build with public API\n- You provide: docs, Slack channel, office hours\n- They drive their own marketing\n- Best for: Ambitious partners with resources\n\n**Tier 2: Strategic Partners (Co-Development)**\n- Co-developed integration\n- You provide: dedicated channel, co-marketing\n- Joint case studies\n- Best for: High-impact integrations\n\n**Don't over-tier.** 2 tiers is enough. More creates confusion.\n\n---\n\n## Decision Trees\n\n### Open or Curated Ecosystem?\n\n```\nIs brand damage risk high if low-quality partners join?\n├─ Yes (regulated, security) → Curated\n└─ No → Continue...\n    │\n    Can you scale human review?\n    ├─ No (hundreds\u002Fthousands) → Open + discovery systems\n    └─ Yes (dozens) → Curated\n```\n\n### Community or Support?\n\n```\nIs this a common question?\n├─ Yes → Community (forum, Slack, docs)\n└─ No → Continue...\n    │\n    Is requester paying customer?\n    ├─ Yes → Support (email, dedicated)\n    └─ No → Community (with escalation path)\n```\n\n---\n\n## Common Mistakes\n\n**1. Building ecosystem before product-market fit**\n   - Fix core product first, then build ecosystem\n\n**2. No developer success team**\n   - Developers need help to succeed beyond docs\n\n**3. Poor documentation**\n   - Foundation of ecosystem, non-negotiable\n\n**4. Treating all developers equally**\n   - Tier support by strategic value (paying > free, partners > hobbyists)\n\n**5. No integration quality standards**\n   - Low-quality integrations hurt your brand\n\n**6. Measuring only vanity metrics**\n   - Track activation and production usage, not just sign-ups\n\n**7. Developer advocates with no technical depth**\n   - Hire developers who can code and teach\n\n---\n\n## Quick Reference\n\n**Open ecosystem checklist:**\n- [ ] Search and discovery (surface quality algorithmically)\n- [ ] Trust signals (verified badges, usage stats, ratings)\n- [ ] Community curation (user recommendations, collections)\n- [ ] Moderation (remove spam after publication)\n\n**Developer journey metrics:**\n- Awareness: Traffic, sign-ups\n- Onboarding: Time to first API call (\u003C10 min target)\n- Integration: % reaching production deployment\n- Advocacy: Developer NPS, public sharing\n\n**Documentation hierarchy:**\n1. Quick starts (5-min \"Hello World\")\n2. Use case guides (solve real problems)\n3. API reference (complete documentation)\n4. Conceptual (architecture, philosophy)\n\n**Partner tiers:**\n- Tier 1: Self-serve (public API, docs, community)\n- Tier 2: Strategic (co-development, co-marketing)\n\n**Student program timeline:**\n- Year 1: University partnerships, activation\n- Year 2: Certification, student community\n- Year 3: Job board, enterprise hiring bridge\n\n---\n\n## Related Skills\n\n- **partnership-architecture**: Partner deal structures and co-marketing\n- **product-led-growth**: Self-serve activation funnels for developer products\n- **0-to-1-launch**: Launching developer products\n\n---\n\n*Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.*\n","# Developer Ecosystem\n\nBuild and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.\n\n## When to Use\n\n**Triggers:**\n- \"How do we build a developer ecosystem?\"\n- \"Should we curate quality or go open?\"\n- \"Developer community isn't growing\"\n- \"Nobody's building on our API\"\n- \"How do we compete with larger platforms?\"\n\n**Context:**\n- API platforms and developer tools\n- Products with extensibility (plugins, integrations)\n- Developer-first GTM motion\n- Platform business models\n\n---\n\n## Core Frameworks\n\n### 1. Open vs Curated Ecosystem (The Marketplace Decision)\n\n**The Pattern:**\n\nRunning ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality?\n\n**Quality control camp:** \"We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage.\"\n\n**Open camp:** \"Developers route around gatekeepers. Network effects matter more than quality control.\"\n\n**The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping.\n\n**What We Built Instead of Gatekeeping:**\n\n1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation\n2. **Trust signals** — Verified badges, usage stats, health scores\n3. **Community curation** — User ratings, collections, recommendations\n4. **Moderation** — Remove spam after publication, not block before\n\n**Result:** Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.\n\n**Decision Framework:**\n- **Curated** works when: Brand risk high, dozens of partners, can scale human review\n- **Open** works when: Hundreds\u002Fthousands of potential partners, network effects matter more than quality control\n\n**Common Mistake:**\n\nDefaulting to curated because \"we need quality control.\" This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead.\n\n---\n\n### 2. The Three-Year Student Program Arc\n\n**The Pattern:**\n\nMost developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.\n\n**Year 1: University Partnerships**\n- Partner with CS departments\n- Curriculum integration (hackathons, coursework)\n- Student licenses (free or heavily discounted)\n- Metrics: # universities, # students activated\n\n**Year 2: Student Community & Certification**\n- Student expert certification program\n- Student-led workshops and events\n- Campus ambassadors\n- Metrics: # certified, # student-led events\n\n**Year 3: Career Bridge**\n- Job board connecting students → companies\n- Enterprise partnerships (hire certified students)\n- Alumni network\n- Metrics: # hired, company partnerships\n\n**Why This Works:**\n\nStudents become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.\n\n**Common Mistake:**\n\nTreating students as immediate revenue. They're not. They're future enterprise decision-makers.\n\n---\n\n### 3. Developer Journey (Awareness → Integration → Advocacy)\n\n**Stage 1: Awareness**\n- How do they discover you?\n- Content, search, word-of-mouth, events\n\n**Stage 2: Onboarding**\n- First API call in \u003C10 minutes\n- Quick-start guides\n- Sample code in popular languages\n\n**Stage 3: Integration**\n- Building real use cases\n- Integration guides\n- Support when stuck\n\n**Stage 4: Production**\n- Deployed and generating value\n- Monitoring usage\n- Enterprise upgrade path\n\n**Stage 5: Advocacy**\n- Sharing publicly\n- Recommending to others\n- Contributing back (docs, code, community)\n\n**Metrics That Matter:**\n- Time to first API call (onboarding)\n- % reaching production (integration success)\n- Monthly active developers (engagement)\n- Developer NPS (advocacy)\n\n**Common Mistake:**\n\nMeasuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).\n\n---\n\n### 4. Documentation Hierarchy\n\n**Tier 1: Quick Starts (Get to Value Fast)**\n- \"Hello World\" in 5 minutes\n- Common use case examples\n- Copy-paste code that works\n\n**Tier 2: Guides (Solve Real Problems)**\n- Use case-specific tutorials\n- Integration patterns\n- Best practices\n\n**Tier 3: Reference (Complete API Docs)**\n- Every endpoint documented\n- Request\u002Fresponse examples\n- Error codes and handling\n\n**Tier 4: Conceptual (Understand the System)**\n- Architecture overviews\n- Design philosophy\n- Advanced patterns\n\n**Most developers need:** Tier 1 first, then Tier 2. Very few read Tier 4.\n\n**Common Mistake:**\n\nStarting with Tier 3 (comprehensive API reference). Developers want quick wins first.\n\n---\n\n### 5. Community vs Support (When to Use Which)\n\n**Community (Async, Scalable):**\n- Slack\u002FDiscord for real-time help\n- Forum for searchable Q&A\n- GitHub discussions for feature requests\n- Best for: Common questions, peer-to-peer help\n\n**Support (Sync, Expensive):**\n- Email support for enterprise\n- Dedicated Slack channels for partners\n- Video calls for complex integrations\n- Best for: Paying customers, strategic partners\n\n**How to Route:**\n\n**Community first:**\n- Developer asks question\n- Community member answers\n- You validate and upvote\n- Searchable for future developers\n\n**Escalate to support when:**\n- No community answer in 24 hours\n- Enterprise\u002Fpaying customer\n- Security or compliance issue\n- Complex integration requiring custom work\n\n**Common Mistake:**\n\nProviding white-glove support to everyone. Doesn't scale. Build community that helps itself.\n\n---\n\n### 6. Partner Tiering for Developer Ecosystems\n\n**Tier 1: Integration Partners (Self-Serve)**\n- Build with public API\n- You provide: docs, Slack channel, office hours\n- They drive their own marketing\n- Best for: Ambitious partners with resources\n\n**Tier 2: Strategic Partners (Co-Development)**\n- Co-developed integration\n- You provide: dedicated channel, co-marketing\n- Joint case studies\n- Best for: High-impact integrations\n\n**Don't over-tier.** 2 tiers is enough. More creates confusion.\n\n---\n\n## Decision Trees\n\n### Open or Curated Ecosystem?\n\n```\nIs brand damage risk high if low-quality partners join?\n├─ Yes (regulated, security) → Curated\n└─ No → Continue...\n    │\n    Can you scale human review?\n    ├─ No (hundreds\u002Fthousands) → Open + discovery systems\n    └─ Yes (dozens) → Curated\n```\n\n### Community or Support?\n\n```\nIs this a common question?\n├─ Yes → Community (forum, Slack, docs)\n└─ No → Continue...\n    │\n    Is requester paying customer?\n    ├─ Yes → Support (email, dedicated)\n    └─ No → Community (with escalation path)\n```\n\n---\n\n## Common Mistakes\n\n**1. Building ecosystem before product-market fit**\n   - Fix core product first, then build ecosystem\n\n**2. No developer success team**\n   - Developers need help to succeed beyond docs\n\n**3. Poor documentation**\n   - Foundation of ecosystem, non-negotiable\n\n**4. Treating all developers equally**\n   - Tier support by strategic value (paying > free, partners > hobbyists)\n\n**5. No integration quality standards**\n   - Low-quality integrations hurt your brand\n\n**6. Measuring only vanity metrics**\n   - Track activation and production usage, not just sign-ups\n\n**7. Developer advocates with no technical depth**\n   - Hire developers who can code and teach\n\n---\n\n## Quick Reference\n\n**Open ecosystem checklist:**\n- [ ] Search and discovery (surface quality algorithmically)\n- [ ] Trust signals (verified badges, usage stats, ratings)\n- [ ] Community curation (user recommendations, collections)\n- [ ] Moderation (remove spam after publication)\n\n**Developer journey metrics:**\n- Awareness: Traffic, sign-ups\n- Onboarding: Time to first API call (\u003C10 min target)\n- Integration: % reaching production deployment\n- Advocacy: Developer NPS, public sharing\n\n**Documentation hierarchy:**\n1. Quick starts (5-min \"Hello World\")\n2. Use case guides (solve real problems)\n3. API reference (complete documentation)\n4. Conceptual (architecture, philosophy)\n\n**Partner tiers:**\n- Tier 1: Self-serve (public API, docs, community)\n- Tier 2: Strategic (co-development, co-marketing)\n\n**Student program timeline:**\n- Year 1: University partnerships, activation\n- Year 2: Certification, student community\n- Year 3: Job board, enterprise hiring bridge\n\n---\n\n## Related Skills\n\n- **partnership-architecture**: Partner deal structures and co-marketing\n- **product-led-growth**: Self-serve activation funnels for developer products\n- **0-to-1-launch**: Launching developer products\n\n---\n\n*Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.*\n",{"name":5,"license":15,"metadata":48,"description":7},{"author":49,"source":50},"Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)","https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fgtm-developer-ecosystem",5344,"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-13 02:05:36",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add github\u002Fawesome-copilot --skill gtm-developer-ecosystem",{"tool":67,"command":68},"bunx","bunx skills add github\u002Fawesome-copilot --skill gtm-developer-ecosystem",{"tool":70,"command":71},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill gtm-developer-ecosystem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgtm-developer-ecosystem\u002FSKILL.md",true,[75,81,85,89,93],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fangebot-vorlagen.md","REFERENCE","参考文档",3309,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsynced\u002F0ce0b40f-f33c-4454-8a14-bd4a36250724_492d02ae-7d32-4227-a9d4-d9f601100de4\u002Fmorntag-angebot\u002Freferences\u002Fangebot-vorlagen.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fkundengespraech-methode.md",4967,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsynced\u002F0ce0b40f-f33c-4454-8a14-bd4a36250724_492d02ae-7d32-4227-a9d4-d9f601100de4\u002Fmorntag-angebot\u002Freferences\u002Fkundengespraech-methode.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fpauschalpreis-architektur.md",3527,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsynced\u002F0ce0b40f-f33c-4454-8a14-bd4a36250724_492d02ae-7d32-4227-a9d4-d9f601100de4\u002Fmorntag-angebot\u002Freferences\u002Fpauschalpreis-architektur.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fschreibstil.md",1597,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsynced\u002F0ce0b40f-f33c-4454-8a14-bd4a36250724_492d02ae-7d32-4227-a9d4-d9f601100de4\u002Fmorntag-angebot\u002Freferences\u002Fschreibstil.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fservices-und-pakete.md",2564,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsynced\u002F0ce0b40f-f33c-4454-8a14-bd4a36250724_492d02ae-7d32-4227-a9d4-d9f601100de4\u002Fmorntag-angebot\u002Freferences\u002Fservices-und-pakete.md",[98,131,159,185,218,234],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":112,"publishedAt":43},"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",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",[113,114,115,116,117,30,118,119,120,121,122,123,124,125,126,127,36,128,129,130],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":43},"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",[137],{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":43},"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",[166],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[168,169,170,171,172,173,145,117,174,175,176,177,178,179,180,36,181,182,183,184],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":43},"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",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,30,212,213,214,215,33,145,216,217],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","methods","controls",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":222,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":231,"publishedAt":43},"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",[226,227,230],{"categoryNo":193,"categoryName":194,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":228,"categoryName":229,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[232,142,206,41,233],"resemble detect","identity",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":222,"licenseFileUrl":238,"sourceHtmlUrl":239,"categories":240,"keywords":245,"publishedAt":43},"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",[241,244],{"categoryNo":242,"categoryName":243,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":110,"categoryName":111,"taxonomyType":107,"taxonomyTypeDesc":108},[246,247,248,249,169,118,9,141,250,251,41,252,253,254,255,256,257,258,259,260,261,262,126,263,264,265,266],"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"]