[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADQ2TX833H62QW0X60HB4M":3,"skill-same:01M6ADQ2TX833H62QW0X60HB4M":96},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6ADQ2TX833H62QW0X60HB4M","impediment-prioritization",null,"Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 \u002F lean countermeasure ranking, ROI vs. effort scoring, or building a remediation \u002F improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41133,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fimpediment-prioritization\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"impediment prioritization","prioritization","model","action items","2026","when","sequence","action","ranking","free","factor","scoring","formula","value-stream","lean","review","remediation","audit","ghqr","deployment","retrospective","architecture review","architecture","roi","triage","implement","2026-11-10 10:12:30",false,"---\nname: impediment-prioritization\ndescription: 'Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 \u002F lean countermeasure ranking, ROI vs. effort scoring, or building a remediation \u002F improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.'\nlicense: MIT\nmetadata:\n  author: ajenns\n  version: \"2.0.0\"\n  created: \"2026-04-19\"\n  updated: \"2026-04-21\"\n  framework: value-stream-prioritization\n  domain: general\n---\n\n# Impediment Prioritization Skill\n\nA domain-agnostic skill for ranking impediments and their countermeasures. Works with any `{impediment, countermeasure}` list — GHQR findings, audit results, retro action items, risk registers, architecture review gaps, etc.\n\n## When to Activate\n\nActivate when the user:\n- Asks to prioritize, rank, sequence, or triage impediments, gaps, risks, findings, or remediation items\n- Provides a list of impediments with proposed countermeasures (or asks you to propose countermeasures for a list of problems)\n- Asks \"what should we fix first\" on any improvement \u002F remediation backlog\n- Mentions value-stream prioritization, A3 countermeasures, ROI-vs-effort, or lean impediment ranking\n\n## Inputs\n\nAccepted input: a list of `{impediment, countermeasure}` pairs. Sources include (non-exhaustive):\n\n| Source | Maps to Impediment | Maps to Countermeasure |\n|--------|---------------------|-------------------------|\n| GHQR \u002F health-check findings | Finding or gap (Status ≠ Expected) | Recommendation \u002F expected value |\n| Audit results | Non-conformance | Remediation action |\n| Retrospective | \"What went wrong\" item | Agreed improvement |\n| Risk register | Risk | Mitigation |\n| Architecture review | Gap vs. target state | Proposed change |\n| User free-form list | Problem statement | Proposed fix |\n\n**Rules:**\n- One countermeasure per impediment. If the input suggests multiple remediation paths, select the primary one and note alternatives in the rationale — do not emit multiple rows for the same impediment.\n- Collapse duplicates before scoring.\n- If a source link \u002F citation is available, attach it to the countermeasure.\n- If a confidence level is available on the source, surface it as an optional `Confidence` column.\n\n## Scoring Rubric (1–10 scales)\n\nScore each impediment's countermeasure against all four criteria. See [references\u002Fscoring-rubric.md](.\u002Freferences\u002Fscoring-rubric.md) for anchoring examples at the 1 \u002F 5 \u002F 10 levels across multiple domains (platform engineering, security, SRE, application development, governance).\n\n| Criterion | Scale | Definition |\n|-----------|-------|------------|\n| **Return on Investment (ROI)** | 1 = low, 10 = high | Efficiency gain delivered by the countermeasure to this step AND to the overall value stream. Not purely financial — weight throughput, cycle-time reduction, defect removal, user \u002F developer experience, and compliance lift. |\n| **Cost to Implement** | 1 = inexpensive, 10 = very expensive | Human capital (salary + time of people needed) plus any purchases, licenses, or infrastructure required to implement the countermeasure. |\n| **Ease of Deployment** | 1 = extremely hard, 10 = very easy | Remediation effort required to actually deploy the countermeasure end-to-end. Reflects technical complexity, change-management burden, and rollback risk. |\n| **Risk Factor** | 1 = low risk, 10 = very high risk | Risk weighted on impact to the overall value stream if the countermeasure goes wrong, stalls, or is deferred. |\n\nEvery score must be accompanied by a one-line rationale. When a score is an estimate rather than drawn from explicit data, mark the rationale with `(estimated)`.\n\n## Formula\n\n```\nPriority = ((ROI * (10 \u002F Cost)) + (Ease * (10 \u002F Risk))) \u002F 2\n```\n\n- Theoretical range: **1 → 100**. Practical range on typical backlogs: ~1 → 100.\n- The scale minimum of `1` guarantees Cost and Risk are never zero (no divide-by-zero).\n- Higher Priority = do first.\n- Boundary checks:\n  - ROI=10, Cost=1, Ease=10, Risk=1 → `((10*10)+(10*10))\u002F2 = 100`\n  - ROI=1, Cost=10, Ease=1, Risk=10 → `((1*1)+(1*1))\u002F2 = 1`\n\nUse the formula verbatim. Do not reweight, normalize, or substitute.\n\n## Method (agent procedure)\n\n1. **Ingest** the impediment list. Confirm 1:1 impediment-to-countermeasure mapping; collapse duplicates.\n2. **Confirm the countermeasure** for each impediment. Prefer documented best practice for the domain. Cite a public \u002F authoritative link when one is available.\n3. **Score** all four criteria using the rubric. Write a one-line rationale per criterion.\n4. **Compute** Priority using the formula. Round to one decimal place.\n5. **Sort** rows by Priority descending. Assign Rank starting at 1.\n6. **Render** the output table (see below).\n7. **Call out** the top 3 impediments with a short \"why act first\" paragraph.\n8. **Optional tags**: if the workflow requires ownership flags (e.g., `[CSA Action Required]` vs. `[Customer Self-Service]` for GHQR\u002FPAK, or `[Owner: Team X]` \u002F `[Self-Service]` for internal backlogs), include them on the top-ranked items. Skip if not requested.\n\n## Output Template\n\n```markdown\n## Prioritized Impediments\n\n**Scoring:** ROI (1 low → 10 high), Cost (1 cheap → 10 expensive), Ease (1 hard → 10 easy), Risk (1 low → 10 high).\n**Formula:** `Priority = ((ROI * (10\u002FCost)) + (Ease * (10\u002FRisk))) \u002F 2`\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority | Rationale |\n|------|------------|----------------|-----|------|------|------|----------|-----------|\n| 1 | [gap] | [action + link] | [n] | [n] | [n] | [n] | [n.n] | ROI: …\u003Cbr>Cost: …\u003Cbr>Ease: …\u003Cbr>Risk: … |\n\n### Top 3 — Act First\n1. **[Impediment]** — [why it wins on the formula + optional ownership tag]\n2. …\n3. …\n```\n\n**Worked example (GitHub Enterprise adoption):**\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority | Rationale |\n|------|------------|----------------|-----|------|------|------|----------|-----------|\n| 1 | 2FA not enforced at org level | Enforce org-wide 2FA ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Forganizations\u002Fkeeping-your-organization-secure\u002Fsetting-up-two-factor-authentication\u002Frequiring-two-factor-authentication-in-your-organization)) | 9 | 2 | 8 | 2 | 42.5 | ROI: removes broad credential-compromise class\u003Cbr>Cost: admin toggle + member comms\u003Cbr>Ease: single org setting, members re-enroll\u003Cbr>Risk: low — can stage with grace period |\n| 2 | Secret scanning disabled | Enable secret scanning + push protection org-wide ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fcode-security\u002Fsecret-scanning\u002Fabout-secret-scanning)) | 8 | 3 | 7 | 3 | 25.0 | ROI: catches leaked creds pre-merge\u003Cbr>Cost: GHAS seats if not bundled (estimated)\u003Cbr>Ease: org-level default\u003Cbr>Risk: push-protection may block legitimate commits; stage per repo |\n| 3 | No CODEOWNERS on critical repos | Add CODEOWNERS to top-20 repos ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frepositories\u002Fmanaging-your-repositorys-settings-and-features\u002Fcustomizing-your-repository\u002Fabout-code-owners)) | 6 | 4 | 6 | 4 | 15.0 | ROI: targeted review coverage\u003Cbr>Cost: team time to define owners (estimated)\u003Cbr>Ease: file-level change, but requires owner buy-in\u003Cbr>Risk: review bottlenecks if owners undersized |\n\n**Worked example (generic retrospective action items):**\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority |\n|------|------------|----------------|-----|------|------|------|----------|\n| 1 | Flaky test suite blocks deploys daily | Quarantine top-10 flaky tests + add retry policy | 9 | 2 | 8 | 2 | 42.5 |\n| 2 | No on-call runbook for payment service | Draft runbook from last 3 incidents | 7 | 3 | 8 | 2 | 31.7 |\n| 3 | Manual release notes take 2h\u002Frelease | Generate from Conventional Commits via CI | 6 | 4 | 5 | 3 | 15.8 |\n\n## Assumptions & Guardrails\n\n- Scores are estimates informed by the rubric and any available source \u002F citation. Mark estimated rationales explicitly with `(estimated)`.\n- Never fabricate context (team size, budget, tool inventory, organizational constraints). If required, ask the user or mark the score as estimated.\n- Final ranking is a recommendation — it should be reviewed with the accountable team \u002F owner before it's committed to an execution plan.\n- Read-only by default — this skill does not execute remediations; it produces a ranked list consumed downstream.\n\n## Downstream Integration (optional)\n\nThe ranked table produced by this skill is the deliverable. Wire it into whatever downstream artifact your workflow needs (Jira epic, ADR, OKR backlog, incident review, health check report, etc.). This skill does not depend on any sibling skills or external templates.\n","# Impediment Prioritization Skill\n\nA domain-agnostic skill for ranking impediments and their countermeasures. Works with any `{impediment, countermeasure}` list — GHQR findings, audit results, retro action items, risk registers, architecture review gaps, etc.\n\n## When to Activate\n\nActivate when the user:\n- Asks to prioritize, rank, sequence, or triage impediments, gaps, risks, findings, or remediation items\n- Provides a list of impediments with proposed countermeasures (or asks you to propose countermeasures for a list of problems)\n- Asks \"what should we fix first\" on any improvement \u002F remediation backlog\n- Mentions value-stream prioritization, A3 countermeasures, ROI-vs-effort, or lean impediment ranking\n\n## Inputs\n\nAccepted input: a list of `{impediment, countermeasure}` pairs. Sources include (non-exhaustive):\n\n| Source | Maps to Impediment | Maps to Countermeasure |\n|--------|---------------------|-------------------------|\n| GHQR \u002F health-check findings | Finding or gap (Status ≠ Expected) | Recommendation \u002F expected value |\n| Audit results | Non-conformance | Remediation action |\n| Retrospective | \"What went wrong\" item | Agreed improvement |\n| Risk register | Risk | Mitigation |\n| Architecture review | Gap vs. target state | Proposed change |\n| User free-form list | Problem statement | Proposed fix |\n\n**Rules:**\n- One countermeasure per impediment. If the input suggests multiple remediation paths, select the primary one and note alternatives in the rationale — do not emit multiple rows for the same impediment.\n- Collapse duplicates before scoring.\n- If a source link \u002F citation is available, attach it to the countermeasure.\n- If a confidence level is available on the source, surface it as an optional `Confidence` column.\n\n## Scoring Rubric (1–10 scales)\n\nScore each impediment's countermeasure against all four criteria. See [references\u002Fscoring-rubric.md](.\u002Freferences\u002Fscoring-rubric.md) for anchoring examples at the 1 \u002F 5 \u002F 10 levels across multiple domains (platform engineering, security, SRE, application development, governance).\n\n| Criterion | Scale | Definition |\n|-----------|-------|------------|\n| **Return on Investment (ROI)** | 1 = low, 10 = high | Efficiency gain delivered by the countermeasure to this step AND to the overall value stream. Not purely financial — weight throughput, cycle-time reduction, defect removal, user \u002F developer experience, and compliance lift. |\n| **Cost to Implement** | 1 = inexpensive, 10 = very expensive | Human capital (salary + time of people needed) plus any purchases, licenses, or infrastructure required to implement the countermeasure. |\n| **Ease of Deployment** | 1 = extremely hard, 10 = very easy | Remediation effort required to actually deploy the countermeasure end-to-end. Reflects technical complexity, change-management burden, and rollback risk. |\n| **Risk Factor** | 1 = low risk, 10 = very high risk | Risk weighted on impact to the overall value stream if the countermeasure goes wrong, stalls, or is deferred. |\n\nEvery score must be accompanied by a one-line rationale. When a score is an estimate rather than drawn from explicit data, mark the rationale with `(estimated)`.\n\n## Formula\n\n```\nPriority = ((ROI * (10 \u002F Cost)) + (Ease * (10 \u002F Risk))) \u002F 2\n```\n\n- Theoretical range: **1 → 100**. Practical range on typical backlogs: ~1 → 100.\n- The scale minimum of `1` guarantees Cost and Risk are never zero (no divide-by-zero).\n- Higher Priority = do first.\n- Boundary checks:\n  - ROI=10, Cost=1, Ease=10, Risk=1 → `((10*10)+(10*10))\u002F2 = 100`\n  - ROI=1, Cost=10, Ease=1, Risk=10 → `((1*1)+(1*1))\u002F2 = 1`\n\nUse the formula verbatim. Do not reweight, normalize, or substitute.\n\n## Method (agent procedure)\n\n1. **Ingest** the impediment list. Confirm 1:1 impediment-to-countermeasure mapping; collapse duplicates.\n2. **Confirm the countermeasure** for each impediment. Prefer documented best practice for the domain. Cite a public \u002F authoritative link when one is available.\n3. **Score** all four criteria using the rubric. Write a one-line rationale per criterion.\n4. **Compute** Priority using the formula. Round to one decimal place.\n5. **Sort** rows by Priority descending. Assign Rank starting at 1.\n6. **Render** the output table (see below).\n7. **Call out** the top 3 impediments with a short \"why act first\" paragraph.\n8. **Optional tags**: if the workflow requires ownership flags (e.g., `[CSA Action Required]` vs. `[Customer Self-Service]` for GHQR\u002FPAK, or `[Owner: Team X]` \u002F `[Self-Service]` for internal backlogs), include them on the top-ranked items. Skip if not requested.\n\n## Output Template\n\n```markdown\n## Prioritized Impediments\n\n**Scoring:** ROI (1 low → 10 high), Cost (1 cheap → 10 expensive), Ease (1 hard → 10 easy), Risk (1 low → 10 high).\n**Formula:** `Priority = ((ROI * (10\u002FCost)) + (Ease * (10\u002FRisk))) \u002F 2`\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority | Rationale |\n|------|------------|----------------|-----|------|------|------|----------|-----------|\n| 1 | [gap] | [action + link] | [n] | [n] | [n] | [n] | [n.n] | ROI: …\u003Cbr>Cost: …\u003Cbr>Ease: …\u003Cbr>Risk: … |\n\n### Top 3 — Act First\n1. **[Impediment]** — [why it wins on the formula + optional ownership tag]\n2. …\n3. …\n```\n\n**Worked example (GitHub Enterprise adoption):**\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority | Rationale |\n|------|------------|----------------|-----|------|------|------|----------|-----------|\n| 1 | 2FA not enforced at org level | Enforce org-wide 2FA ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Forganizations\u002Fkeeping-your-organization-secure\u002Fsetting-up-two-factor-authentication\u002Frequiring-two-factor-authentication-in-your-organization)) | 9 | 2 | 8 | 2 | 42.5 | ROI: removes broad credential-compromise class\u003Cbr>Cost: admin toggle + member comms\u003Cbr>Ease: single org setting, members re-enroll\u003Cbr>Risk: low — can stage with grace period |\n| 2 | Secret scanning disabled | Enable secret scanning + push protection org-wide ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fcode-security\u002Fsecret-scanning\u002Fabout-secret-scanning)) | 8 | 3 | 7 | 3 | 25.0 | ROI: catches leaked creds pre-merge\u003Cbr>Cost: GHAS seats if not bundled (estimated)\u003Cbr>Ease: org-level default\u003Cbr>Risk: push-protection may block legitimate commits; stage per repo |\n| 3 | No CODEOWNERS on critical repos | Add CODEOWNERS to top-20 repos ([docs](https:\u002F\u002Fdocs.github.com\u002Fen\u002Frepositories\u002Fmanaging-your-repositorys-settings-and-features\u002Fcustomizing-your-repository\u002Fabout-code-owners)) | 6 | 4 | 6 | 4 | 15.0 | ROI: targeted review coverage\u003Cbr>Cost: team time to define owners (estimated)\u003Cbr>Ease: file-level change, but requires owner buy-in\u003Cbr>Risk: review bottlenecks if owners undersized |\n\n**Worked example (generic retrospective action items):**\n\n| Rank | Impediment | Countermeasure | ROI | Cost | Ease | Risk | Priority |\n|------|------------|----------------|-----|------|------|------|----------|\n| 1 | Flaky test suite blocks deploys daily | Quarantine top-10 flaky tests + add retry policy | 9 | 2 | 8 | 2 | 42.5 |\n| 2 | No on-call runbook for payment service | Draft runbook from last 3 incidents | 7 | 3 | 8 | 2 | 31.7 |\n| 3 | Manual release notes take 2h\u002Frelease | Generate from Conventional Commits via CI | 6 | 4 | 5 | 3 | 15.8 |\n\n## Assumptions & Guardrails\n\n- Scores are estimates informed by the rubric and any available source \u002F citation. Mark estimated rationales explicitly with `(estimated)`.\n- Never fabricate context (team size, budget, tool inventory, organizational constraints). If required, ask the user or mark the score as estimated.\n- Final ranking is a recommendation — it should be reviewed with the accountable team \u002F owner before it's committed to an execution plan.\n- Read-only by default — this skill does not execute remediations; it produces a ranked list consumed downstream.\n\n## Downstream Integration (optional)\n\nThe ranked table produced by this skill is the deliverable. Wire it into whatever downstream artifact your workflow needs (Jira epic, ADR, OKR backlog, incident review, health check report, etc.). This skill does not depend on any sibling skills or external templates.\n",{"name":5,"license":15,"metadata":55,"description":7},{"author":56,"domain":57,"created":58,"updated":59,"version":60,"framework":61},"ajenns","general","2026-04-19","2026-04-21","2.0.0","value-stream-prioritization","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fimpediment-prioritization",5354,"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-14 05:37:52",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add github\u002Fawesome-copilot --skill impediment-prioritization",{"tool":78,"command":79},"bunx","bunx skills add github\u002Fawesome-copilot --skill impediment-prioritization",{"tool":81,"command":82},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill impediment-prioritization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fimpediment-prioritization\u002FSKILL.md",true,[86,92],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"agents\u002Fopenai.yaml","REFERENCE","参考文档",213,"https:\u002F\u002Fgithub.com\u002Fswarmauri\u002Fswarmauri-sdk\u002Fblob\u002Fmaster\u002Fplugins\u002Fswarmauri-sdk-authoring\u002Fskills\u002Fswarmauri-add-core-interface\u002Fagents\u002Fopenai.yaml",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fscoring-rubric.md",5953,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fimpediment-prioritization\u002Freferences\u002Fscoring-rubric.md",[97,126,153,182,216,233],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":107,"publishedAt":50},"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",[103,106],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,29,39,113,114,115,116,117,118,119,120,121,122,123,124,125],"supabase","rls","supabase rls","supabase rls policies","project","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":50},"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",[132],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[134,135,41,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152],"distribution","skill distribution audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":165,"publishedAt":50},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[166,167,168,169,170,171,139,112,43,172,173,174,175,176,177,122,178,179,180,181],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":50},"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",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},[194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,29,209,210,211,212,213,139,214,215],"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":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":220,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":229,"publishedAt":50},"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",[224,225,228],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,136,203,231,232],"resemble detect","https","identity",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":220,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":244,"publishedAt":50},"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",[240,243],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,248,167,39,9,41,249,250,231,251,252,253,254,255,256,257,258,259,260,261,120,262,26,263,264],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","regression","structural"]