[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADTYBFC47NJGBFGDN2GY6S":3,"skill-same:01M6ADTYBFC47NJGBFGDN2GY6S":73},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6ADTYBFC47NJGBFGDN2GY6S","meeting-minutes",null,"Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","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\u002Fmeeting-minutes\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"meeting minutes","meeting","minutes","generate","metadata","decisions","meetings","up","agenda","actionable","concise","follow-up","action","for","action items","2026-11-10 10:12:30",false,"---\nname: meeting-minutes\ndescription: 'Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.'\n---\n\n# Meeting Minutes Skill — Short Internal Meetings\n\n## Purpose \u002F Overview\n\nThis Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.\n\n## When to Use\n\nUse this skill when:\n\n- Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration\n- Situations that require a concise record of decisions, assigned action items, and follow-ups\n- Creating a standardized minutes document from a live meeting, transcript, recording, or notes\n\n---\n\n## Operational Workflow\n\n### Phase 1: Intake (before drafting)\n\n- Obtain meeting metadata: title, date, start\u002Fend time (or duration), organizer, and intended audience.\n- Confirm available inputs: agenda, slides, recording, transcript, or raw notes.\n- If key details are missing, ask up to 3 clarifying questions before producing minutes (see \"Discovery\" below).\n\n### Phase 2: Capture (during \u002F immediately after meeting)\n\n- Record attendees and absentees.\n- Capture brief notes per agenda item with time markers if available.\n- Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).\n\n### Phase 3: Drafting\n\n- Generate minutes following the **Strict Minutes Schema** (below).\n- Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.\n- Mark unresolved issues or items requiring follow-up in the Parking Lot.\n\n### Phase 4: Review & Publish\n\n- If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).\n- Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.\n\n---\n\n## Discovery (required clarifying questions)\n\nBefore generating minutes, the agent **MUST** ask up to three clarifying questions if any of these are missing:\n\n- What is the meeting title, date, start time (or duration), and organizer?\n- Is there an agenda or transcript\u002Frecording to reference? If yes, please provide.\n- Who should be assigned as the reviewer or approver for the minutes?\n\nIf the user responds \"no transcript\" or \"no agenda,\" proceed but mark source material as \"ad-hoc notes\" and flag potential gaps.\n\n---\n\n## Strict Minutes Schema (Output Structure)\n\nYou **MUST** produce meeting minutes following this exact structure. If information is unavailable, use `TBD` or `Unknown` and explain how to obtain it.\n\n### 1. Metadata\n\n- **Title**:\n- **Date (YYYY-MM-DD)**:\n- **Start Time (UTC)**:\n- **End Time (UTC) or Duration**:\n- **Organizer**:\n- **Location \u002F Virtual Link**:\n- **Minutes Author** (agent or person):\n- **Distribution List** (who receives the minutes):\n\n### 2. Attendance\n\n- **Present**: [list of names + roles]\n- **Regrets \u002F Absent**: [list]\n- **Notetaker \u002F Recorder**: [name or \"agent\"]\n\n### 3. Agenda\n\nBullet list of agenda items, in order:\n\n- Item 1: short title\n- Item 2: short title\n- ...\n\n### 4. Summary\n\nA concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.\n\n### 5. Decisions Made\n\nEach as a separate bullet:\n\n- **Decision 1**: statement of decision.\n  - Who decided \u002F approved: [name(s) or group]\n  - Rationale (1–2 sentences): brief reason.\n  - Effective date (if applicable): YYYY-MM-DD\n- **Decision 2**: ...\n\n### 6. Action Items\n\nTable-style bullets; **must include owner and due date**:\n\n- **[ID] Action**: short description\n  - **Owner**: Name (team)\n  - **Due**: YYYY-MM-DD or \"ASAP\" \u002F timeframe\n  - **Acceptance Criteria**: (what completes this action)\n  - **Linked artifacts \u002F tickets**: (optional URL or ticket id)\n\n**Example:**\n\n- [A1] Draft deployment runbook for feature X\n  - Owner: Alex (Engineering)\n  - Due: 2026-02-05\n  - Acceptance Criteria: runbook includes steps for rollback, health checks, and monitoring links\n  - Linked artifacts: https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123\n\n### 7. Notes by Agenda Item\n\nBrief, factual, timestamp optional:\n\n- **Agenda Item 1**: title\n  - Key points:\n    - Point A (timestamp 00:05)\n    - Point B (timestamp 00:12)\n  - Open issues \u002F questions:\n    - Q1: question text (owner if assigned)\n- **Agenda Item 2**: ...\n\n### 8. Parking Lot \u002F Unresolved Items\n\n- **Item**: short description\n  - Why parked \u002F next step:\n  - Suggested owner or next meeting to resolve\n\n### 9. Risks \u002F Blockers (if any)\n\n- **Risk 1**: short description, impact, mitigation owner\n- **Risk 2**: ...\n\n### 10. Next Meeting \u002F Follow-up\n\n- Proposed date\u002Ftime (if any)\n- Objectives for next meeting\n\n### 11. Attachments \u002F References\n\n- Agenda document: URL\n- Slides: URL\n- Transcript \u002F Recording: URL\n- Related tickets: list of URLs or IDs\n\n### 12. Version & Change Log\n\n- **Version**: 1.0\n- **Last updated**: YYYY-MM-DDTHH:MM:SSZ\n- **Changes**: short notes on edits and who made them\n\n---\n\n## Style & Quality Rules\n\n- Keep minutes concise: total length should typically be under 1 A4 page for meetings \u003C= 30 minutes and under 2 pages for meetings close to 60 minutes.\n- Use plain language and bullet lists for readability.\n- Prioritize decisions and action items at the top of the document.\n- Do NOT include speculative language or unverified claims. If something is uncertain, label it `TBD` and note the missing info source.\n- Use consistent timestamps and ISO 8601 dates (YYYY-MM-DD or full UTC timestamp).\n\n---\n\n## DO \u002F DON'T\n\n**DO:**\n\n- Include owner and due date for every action item.\n- Provide acceptance criteria for action items when possible.\n- Link to artifacts (tickets, slides, recordings) for traceability.\n- Send draft for quick review if minutes contain significant decisions.\n\n**DON'T:**\n\n- Omit decisions or action items — these are the primary value of minutes.\n- Mix personal opinions with facts. Keep commentary clearly marked as \"Opinion\" or exclude it.\n- Publish raw PII gathered during discussion unless required and authorized.\n\n---\n\n## Example Prompts (for Copilot \u002F Agent)\n\n**Prompt to generate minutes from transcript:**\n\n> \"Generate meeting minutes from the following meeting transcript. Meeting title: 'Platform Weekly Sync'. Date: 2026-02-10. Duration: 45 minutes. Organizer: Priya (Platform Lead). Transcript: \u003Cpaste transcript>. Follow the Strict Minutes Schema. Highlight decisions and create action items with owners and due dates where implied.\"\n\n**Prompt to generate minutes from notes:**\n\n> \"I have raw notes from a 30-minute design review. Title: 'Feature Y Design Review'. Date: 2026-02-11. Notes: \u003Cpaste notes>. Produce concise minutes following the Strict Minutes Schema. Ask up to 3 clarifying questions if critical fields are missing.\"\n\n---\n\n## Quick Templates (copyable)\n\n### Concise minutes template (short):\n\n```\n- Title:\n- Date:\n- Organizer:\n- Present:\n- Summary:\n- Decisions:\n  - Decision 1 — Who — Effective:\n- Action Items:\n  - [A1] Action — Owner — Due — Acceptance Criteria\n- Next Steps \u002F Next Meeting:\n```\n\n### Detailed minutes template (full schema):\n\nUse the Strict Minutes Schema above.\n\n---\n\n## Verification & Acceptance Criteria for Generated Minutes\n\nA generated minutes document is acceptable if:\n\n- It contains Metadata, Attendance, Decisions, and Action Items sections.\n- Every action item has an assigned owner and a due date or a clear timeframe.\n- All significant decisions are captured with at least 1-line rationale.\n- Attachments or references are listed or explicitly marked `None`.\n- The document is factual; uncertain items are labeled `TBD`.\n","# Meeting Minutes Skill — Short Internal Meetings\n\n## Purpose \u002F Overview\n\nThis Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.\n\n## When to Use\n\nUse this skill when:\n\n- Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration\n- Situations that require a concise record of decisions, assigned action items, and follow-ups\n- Creating a standardized minutes document from a live meeting, transcript, recording, or notes\n\n---\n\n## Operational Workflow\n\n### Phase 1: Intake (before drafting)\n\n- Obtain meeting metadata: title, date, start\u002Fend time (or duration), organizer, and intended audience.\n- Confirm available inputs: agenda, slides, recording, transcript, or raw notes.\n- If key details are missing, ask up to 3 clarifying questions before producing minutes (see \"Discovery\" below).\n\n### Phase 2: Capture (during \u002F immediately after meeting)\n\n- Record attendees and absentees.\n- Capture brief notes per agenda item with time markers if available.\n- Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).\n\n### Phase 3: Drafting\n\n- Generate minutes following the **Strict Minutes Schema** (below).\n- Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.\n- Mark unresolved issues or items requiring follow-up in the Parking Lot.\n\n### Phase 4: Review & Publish\n\n- If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).\n- Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.\n\n---\n\n## Discovery (required clarifying questions)\n\nBefore generating minutes, the agent **MUST** ask up to three clarifying questions if any of these are missing:\n\n- What is the meeting title, date, start time (or duration), and organizer?\n- Is there an agenda or transcript\u002Frecording to reference? If yes, please provide.\n- Who should be assigned as the reviewer or approver for the minutes?\n\nIf the user responds \"no transcript\" or \"no agenda,\" proceed but mark source material as \"ad-hoc notes\" and flag potential gaps.\n\n---\n\n## Strict Minutes Schema (Output Structure)\n\nYou **MUST** produce meeting minutes following this exact structure. If information is unavailable, use `TBD` or `Unknown` and explain how to obtain it.\n\n### 1. Metadata\n\n- **Title**:\n- **Date (YYYY-MM-DD)**:\n- **Start Time (UTC)**:\n- **End Time (UTC) or Duration**:\n- **Organizer**:\n- **Location \u002F Virtual Link**:\n- **Minutes Author** (agent or person):\n- **Distribution List** (who receives the minutes):\n\n### 2. Attendance\n\n- **Present**: [list of names + roles]\n- **Regrets \u002F Absent**: [list]\n- **Notetaker \u002F Recorder**: [name or \"agent\"]\n\n### 3. Agenda\n\nBullet list of agenda items, in order:\n\n- Item 1: short title\n- Item 2: short title\n- ...\n\n### 4. Summary\n\nA concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.\n\n### 5. Decisions Made\n\nEach as a separate bullet:\n\n- **Decision 1**: statement of decision.\n  - Who decided \u002F approved: [name(s) or group]\n  - Rationale (1–2 sentences): brief reason.\n  - Effective date (if applicable): YYYY-MM-DD\n- **Decision 2**: ...\n\n### 6. Action Items\n\nTable-style bullets; **must include owner and due date**:\n\n- **[ID] Action**: short description\n  - **Owner**: Name (team)\n  - **Due**: YYYY-MM-DD or \"ASAP\" \u002F timeframe\n  - **Acceptance Criteria**: (what completes this action)\n  - **Linked artifacts \u002F tickets**: (optional URL or ticket id)\n\n**Example:**\n\n- [A1] Draft deployment runbook for feature X\n  - Owner: Alex (Engineering)\n  - Due: 2026-02-05\n  - Acceptance Criteria: runbook includes steps for rollback, health checks, and monitoring links\n  - Linked artifacts: https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fissues\u002F123\n\n### 7. Notes by Agenda Item\n\nBrief, factual, timestamp optional:\n\n- **Agenda Item 1**: title\n  - Key points:\n    - Point A (timestamp 00:05)\n    - Point B (timestamp 00:12)\n  - Open issues \u002F questions:\n    - Q1: question text (owner if assigned)\n- **Agenda Item 2**: ...\n\n### 8. Parking Lot \u002F Unresolved Items\n\n- **Item**: short description\n  - Why parked \u002F next step:\n  - Suggested owner or next meeting to resolve\n\n### 9. Risks \u002F Blockers (if any)\n\n- **Risk 1**: short description, impact, mitigation owner\n- **Risk 2**: ...\n\n### 10. Next Meeting \u002F Follow-up\n\n- Proposed date\u002Ftime (if any)\n- Objectives for next meeting\n\n### 11. Attachments \u002F References\n\n- Agenda document: URL\n- Slides: URL\n- Transcript \u002F Recording: URL\n- Related tickets: list of URLs or IDs\n\n### 12. Version & Change Log\n\n- **Version**: 1.0\n- **Last updated**: YYYY-MM-DDTHH:MM:SSZ\n- **Changes**: short notes on edits and who made them\n\n---\n\n## Style & Quality Rules\n\n- Keep minutes concise: total length should typically be under 1 A4 page for meetings \u003C= 30 minutes and under 2 pages for meetings close to 60 minutes.\n- Use plain language and bullet lists for readability.\n- Prioritize decisions and action items at the top of the document.\n- Do NOT include speculative language or unverified claims. If something is uncertain, label it `TBD` and note the missing info source.\n- Use consistent timestamps and ISO 8601 dates (YYYY-MM-DD or full UTC timestamp).\n\n---\n\n## DO \u002F DON'T\n\n**DO:**\n\n- Include owner and due date for every action item.\n- Provide acceptance criteria for action items when possible.\n- Link to artifacts (tickets, slides, recordings) for traceability.\n- Send draft for quick review if minutes contain significant decisions.\n\n**DON'T:**\n\n- Omit decisions or action items — these are the primary value of minutes.\n- Mix personal opinions with facts. Keep commentary clearly marked as \"Opinion\" or exclude it.\n- Publish raw PII gathered during discussion unless required and authorized.\n\n---\n\n## Example Prompts (for Copilot \u002F Agent)\n\n**Prompt to generate minutes from transcript:**\n\n> \"Generate meeting minutes from the following meeting transcript. Meeting title: 'Platform Weekly Sync'. Date: 2026-02-10. Duration: 45 minutes. Organizer: Priya (Platform Lead). Transcript: \u003Cpaste transcript>. Follow the Strict Minutes Schema. Highlight decisions and create action items with owners and due dates where implied.\"\n\n**Prompt to generate minutes from notes:**\n\n> \"I have raw notes from a 30-minute design review. Title: 'Feature Y Design Review'. Date: 2026-02-11. Notes: \u003Cpaste notes>. Produce concise minutes following the Strict Minutes Schema. Ask up to 3 clarifying questions if critical fields are missing.\"\n\n---\n\n## Quick Templates (copyable)\n\n### Concise minutes template (short):\n\n```\n- Title:\n- Date:\n- Organizer:\n- Present:\n- Summary:\n- Decisions:\n  - Decision 1 — Who — Effective:\n- Action Items:\n  - [A1] Action — Owner — Due — Acceptance Criteria\n- Next Steps \u002F Next Meeting:\n```\n\n### Detailed minutes template (full schema):\n\nUse the Strict Minutes Schema above.\n\n---\n\n## Verification & Acceptance Criteria for Generated Minutes\n\nA generated minutes document is acceptable if:\n\n- It contains Metadata, Attendance, Decisions, and Action Items sections.\n- Every action item has an assigned owner and a due date or a clear timeframe.\n- All significant decisions are captured with at least 1-line rationale.\n- Attachments or references are listed or explicitly marked `None`.\n- The document is factual; uncertain items are labeled `TBD`.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fmeeting-minutes",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add github\u002Fawesome-copilot --skill meeting-minutes",{"tool":65,"command":66},"bunx","bunx skills add github\u002Fawesome-copilot --skill meeting-minutes",{"tool":68,"command":69},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill meeting-minutes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-minutes\u002FSKILL.md",true,[],[74,105,132,160,194,211],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":84,"publishedAt":44},"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",[80,83],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":44},"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",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[113,114,115,116,117,118,42,119,120,121,122,123,124,125,126,127,128,129,130,131],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":44},"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",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[143,144,145,146,147,148,42,89,149,150,151,152,153,154,155,101,156,157,158,159],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":171,"publishedAt":44},"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",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":140,"categoryName":141,"taxonomyType":26,"taxonomyTypeDesc":27},[172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,90,187,188,189,190,191,42,192,193],"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":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":207,"publishedAt":44},"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",[202,203,206],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[208,116,181,209,210],"resemble detect","https","identity",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":198,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":222,"publishedAt":44},"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",[218,221],{"categoryNo":219,"categoryName":220,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[223,224,225,226,144,91,9,115,227,228,209,229,230,231,232,233,234,235,236,237,238,239,99,240,241,242,243],"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"]