[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADN8FHXT98XH7APBZ2DX94":3,"skill-same:01M6ADN8FHXT98XH7APBZ2DX94":130},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6ADN8FHXT98XH7APBZ2DX94","github-issues",null,"Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels\u002Fassignees\u002Fmilestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by\u002Fblocking relationships. Triggers on requests like \"create an issue\", \"file a bug\", \"request a feature\", \"update issue X\", \"set the priority\", \"set the start date\", \"create a label\", \"rename a label\", \"list repo labels\", \"link issues\", \"add dependency\", \"blocked by\", \"blocking\", or any GitHub issue management task.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[9,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"github issues","issues","when","MCP","request","track","milestones","labels","types","update issue","rename","reports","bug","dependency","SET","start","repository","file","mcp tools","update","create","feature requests","workflows","2026-11-10 10:12:30",false,"---\nname: github-issues\ndescription: 'Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels\u002Fassignees\u002Fmilestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by\u002Fblocking relationships. Triggers on requests like \"create an issue\", \"file a bug\", \"request a feature\", \"update issue X\", \"set the priority\", \"set the start date\", \"create a label\", \"rename a label\", \"list repo labels\", \"link issues\", \"add dependency\", \"blocked by\", \"blocking\", or any GitHub issue management task.'\n---\n\n# GitHub Issues\n\nManage GitHub issues using the `@modelcontextprotocol\u002Fserver-github` MCP server.\n\n## Available Tools\n\n### MCP Tools (read operations)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__issue_read` | Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) |\n| `mcp__github__list_issues` | List and filter repository issues by state, labels, date |\n| `mcp__github__search_issues` | Search issues across repos using GitHub search syntax |\n| `mcp__github__projects_list` | List projects, project fields, project items, status updates |\n| `mcp__github__projects_get` | Get details of a project, field, item, or status update |\n| `mcp__github__projects_write` | Add\u002Fupdate\u002Fdelete project items, create status updates |\n\n### MCP Tools (write operations)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__issue_write` | Create or update an issue (methods: create, update). Supports title, body, type, labels, assignees, milestone, and issue fields |\n| `mcp__github__add_issue_comment` | Add a comment or a reaction to an issue |\n| `mcp__github__sub_issue_write` | Add, remove, or reprioritize a sub-issue |\n\n### CLI \u002F REST API (write operations)\n\n`gh api` performs the same writes and is the form used in the examples below. Reach for it when the MCP server is not connected, or when you need a REST field the MCP tools do not expose.\n\n| Operation | Command |\n|-----------|---------|\n| Create issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues -X POST -f title=... -f body=...` |\n| Update issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} -X PATCH -f title=... -f state=...` |\n| Add comment | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number}\u002Fcomments -X POST -f body=...` |\n| Close issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} -X PATCH -f state=closed` |\n| Set issue type | Include `-f type=Bug` in the create call (REST API only, not supported by `gh issue create` CLI) |\n\n**Note:** `gh issue create` works for basic issue creation but does **not** support the `--type` flag. Use `gh api` when you need to set issue types.\n\n## Workflow\n\n1. **Determine action**: Create, update, or query?\n2. **Gather context**: Get repo info, existing labels, milestones if needed\n3. **Structure content**: Use appropriate template from [references\u002Ftemplates.md](references\u002Ftemplates.md)\n4. **Execute**: Use MCP tools for reads, `gh api` for writes\n5. **Confirm**: Report the issue URL to user\n\n## Creating Issues\n\nUse `gh api` to create issues. This supports all parameters including issue types.\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fissues \\\n  -X POST \\\n  -f title=\"Issue title\" \\\n  -f body=\"Issue body in markdown\" \\\n  -f type=\"Bug\" \\\n  --jq '{number, html_url}'\n```\n\n### Optional Parameters\n\nAdd any of these flags to the `gh api` call:\n\n```\n-f type=\"Bug\"                    # Issue type (Bug, Feature, Task, Epic, etc.)\n-f 'labels[]=bug'                # Labels (repeat for multiple)\n-f 'assignees[]=username'        # Assignees (repeat for multiple)\n-f milestone=1                   # Milestone number\n```\n\n**Quote the whole `name[]=value` pair.** `[]` is a glob pattern in zsh, the default shell\non macOS, so an unquoted `-f labels[]=bug` never reaches `gh`:\n\n```\nzsh: no matches found: labels[]=bug\n```\n\n**Issue types** are organization-level metadata. To discover available types, use:\n```bash\ngh api graphql -f query='{ organization(login: \"ORG\") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name'\n```\n\n**Prefer issue types over labels for categorization.** When issue types are available (e.g., Bug, Feature, Task), use the `type` parameter instead of applying equivalent labels like `bug` or `enhancement`. Issue types are the canonical way to categorize issues on GitHub. Only fall back to labels when the org has no issue types configured.\n\n### Title Guidelines\n\n- Be specific and actionable\n- Keep under 72 characters\n- When issue types are set, don't add redundant prefixes like `[Bug]`\n- Examples:\n  - `Login fails with SSO enabled` (with type=Bug)\n  - `Add dark mode support` (with type=Feature)\n  - `Add unit tests for auth module` (with type=Task)\n\n### Body Structure\n\nAlways use the templates in [references\u002Ftemplates.md](references\u002Ftemplates.md). Choose based on issue type:\n\n| User Request | Template |\n|--------------|----------|\n| Bug, error, broken, not working | Bug Report |\n| Feature, enhancement, add, new | Feature Request |\n| Task, chore, refactor, update | Task |\n\n## Updating Issues\n\nUse `gh api` with PATCH:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} \\\n  -X PATCH \\\n  -f state=closed \\\n  -f title=\"Updated title\" \\\n  --jq '{number, html_url}'\n```\n\nOnly include fields you want to change. Available fields: `title`, `body`, `state` (open\u002Fclosed), `labels`, `assignees`, `milestone`.\n\n## Examples\n\n### Example 1: Bug Report\n\n**User**: \"Create a bug issue - the login page crashes when using SSO\"\n\n**Action**: \n```bash\ngh api repos\u002Fgithub\u002Fawesome-copilot\u002Fissues \\\n  -X POST \\\n  -f title=\"Login page crashes when using SSO\" \\\n  -f type=\"Bug\" \\\n  -f body=\"## Description\nThe login page crashes when users attempt to authenticate using SSO.\n\n## Steps to Reproduce\n1. Navigate to login page\n2. Click 'Sign in with SSO'\n3. Page crashes\n\n## Expected Behavior\nSSO authentication should complete and redirect to dashboard.\n\n## Actual Behavior\nPage becomes unresponsive and displays error.\" \\\n  --jq '{number, html_url}'\n```\n\n### Example 2: Feature Request\n\n**User**: \"Create a feature request for dark mode with high priority\"\n\n**Action**:\n```bash\ngh api repos\u002Fgithub\u002Fawesome-copilot\u002Fissues \\\n  -X POST \\\n  -f title=\"Add dark mode support\" \\\n  -f type=\"Feature\" \\\n  -f 'labels[]=high-priority' \\\n  -f body=\"## Summary\nAdd dark mode theme option for improved user experience and accessibility.\n\n## Motivation\n- Reduces eye strain in low-light environments\n- Increasingly expected by users\n\n## Proposed Solution\nImplement theme toggle with system preference detection.\n\n## Acceptance Criteria\n- [ ] Toggle switch in settings\n- [ ] Persists user preference\n- [ ] Respects system preference by default\" \\\n  --jq '{number, html_url}'\n```\n\n## Common Labels\n\nUse these standard labels when applicable:\n\n| Label | Use For |\n|-------|---------|\n| `bug` | Something isn't working |\n| `enhancement` | New feature or improvement |\n| `documentation` | Documentation updates |\n| `good first issue` | Good for newcomers |\n| `help wanted` | Extra attention needed |\n| `question` | Further information requested |\n| `wontfix` | Will not be addressed |\n| `duplicate` | Already exists |\n| `high-priority` | Urgent issues |\n\n## Tips\n\n- Always confirm the repository context before creating issues\n- Ask for missing critical information rather than guessing\n- Link related issues when known: `Related to #123`\n- For updates, fetch current issue first to preserve unchanged fields\n\n## Extended Capabilities\n\nThe following features require REST or GraphQL APIs beyond the basic MCP tools. Each is documented in its own reference file so the agent only loads the knowledge it needs.\n\n| Capability | When to use | Reference |\n|------------|-------------|-----------|\n| Advanced search | Complex queries with boolean logic, date ranges, cross-repo search, issue field filters (`field.name:value`) | [references\u002Fsearch.md](references\u002Fsearch.md) |\n| Sub-issues & parent issues | Breaking work into hierarchical tasks | [references\u002Fsub-issues.md](references\u002Fsub-issues.md) |\n| Milestones | Create, read, update, close, reopen, delete milestones and manage milestone issues | [references\u002Fmilestones.md](references\u002Fmilestones.md) |\n| Labels | Discover, create, rename, recolor, and delete repository labels; add or replace labels on an issue | [references\u002Flabels.md](references\u002Flabels.md) |\n| Issue dependencies | Tracking blocked-by \u002F blocking relationships | [references\u002Fdependencies.md](references\u002Fdependencies.md) |\n| Issue types (advanced) | GraphQL operations beyond MCP `list_issue_types` \u002F `type` param | [references\u002Fissue-types.md](references\u002Fissue-types.md) |\n| Projects V2 | Project boards, progress reports, field management | [references\u002Fprojects.md](references\u002Fprojects.md) |\n| Issue fields | Custom metadata: dates, priority, text, numbers (private preview) | [references\u002Fissue-fields.md](references\u002Fissue-fields.md) |\n| Images in issues | Embedding images in issue bodies and comments via CLI | [references\u002Fimages.md](references\u002Fimages.md) |\n","# GitHub Issues\n\nManage GitHub issues using the `@modelcontextprotocol\u002Fserver-github` MCP server.\n\n## Available Tools\n\n### MCP Tools (read operations)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__issue_read` | Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) |\n| `mcp__github__list_issues` | List and filter repository issues by state, labels, date |\n| `mcp__github__search_issues` | Search issues across repos using GitHub search syntax |\n| `mcp__github__projects_list` | List projects, project fields, project items, status updates |\n| `mcp__github__projects_get` | Get details of a project, field, item, or status update |\n| `mcp__github__projects_write` | Add\u002Fupdate\u002Fdelete project items, create status updates |\n\n### MCP Tools (write operations)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__issue_write` | Create or update an issue (methods: create, update). Supports title, body, type, labels, assignees, milestone, and issue fields |\n| `mcp__github__add_issue_comment` | Add a comment or a reaction to an issue |\n| `mcp__github__sub_issue_write` | Add, remove, or reprioritize a sub-issue |\n\n### CLI \u002F REST API (write operations)\n\n`gh api` performs the same writes and is the form used in the examples below. Reach for it when the MCP server is not connected, or when you need a REST field the MCP tools do not expose.\n\n| Operation | Command |\n|-----------|---------|\n| Create issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues -X POST -f title=... -f body=...` |\n| Update issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} -X PATCH -f title=... -f state=...` |\n| Add comment | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number}\u002Fcomments -X POST -f body=...` |\n| Close issue | `gh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} -X PATCH -f state=closed` |\n| Set issue type | Include `-f type=Bug` in the create call (REST API only, not supported by `gh issue create` CLI) |\n\n**Note:** `gh issue create` works for basic issue creation but does **not** support the `--type` flag. Use `gh api` when you need to set issue types.\n\n## Workflow\n\n1. **Determine action**: Create, update, or query?\n2. **Gather context**: Get repo info, existing labels, milestones if needed\n3. **Structure content**: Use appropriate template from [references\u002Ftemplates.md](references\u002Ftemplates.md)\n4. **Execute**: Use MCP tools for reads, `gh api` for writes\n5. **Confirm**: Report the issue URL to user\n\n## Creating Issues\n\nUse `gh api` to create issues. This supports all parameters including issue types.\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fissues \\\n  -X POST \\\n  -f title=\"Issue title\" \\\n  -f body=\"Issue body in markdown\" \\\n  -f type=\"Bug\" \\\n  --jq '{number, html_url}'\n```\n\n### Optional Parameters\n\nAdd any of these flags to the `gh api` call:\n\n```\n-f type=\"Bug\"                    # Issue type (Bug, Feature, Task, Epic, etc.)\n-f 'labels[]=bug'                # Labels (repeat for multiple)\n-f 'assignees[]=username'        # Assignees (repeat for multiple)\n-f milestone=1                   # Milestone number\n```\n\n**Quote the whole `name[]=value` pair.** `[]` is a glob pattern in zsh, the default shell\non macOS, so an unquoted `-f labels[]=bug` never reaches `gh`:\n\n```\nzsh: no matches found: labels[]=bug\n```\n\n**Issue types** are organization-level metadata. To discover available types, use:\n```bash\ngh api graphql -f query='{ organization(login: \"ORG\") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name'\n```\n\n**Prefer issue types over labels for categorization.** When issue types are available (e.g., Bug, Feature, Task), use the `type` parameter instead of applying equivalent labels like `bug` or `enhancement`. Issue types are the canonical way to categorize issues on GitHub. Only fall back to labels when the org has no issue types configured.\n\n### Title Guidelines\n\n- Be specific and actionable\n- Keep under 72 characters\n- When issue types are set, don't add redundant prefixes like `[Bug]`\n- Examples:\n  - `Login fails with SSO enabled` (with type=Bug)\n  - `Add dark mode support` (with type=Feature)\n  - `Add unit tests for auth module` (with type=Task)\n\n### Body Structure\n\nAlways use the templates in [references\u002Ftemplates.md](references\u002Ftemplates.md). Choose based on issue type:\n\n| User Request | Template |\n|--------------|----------|\n| Bug, error, broken, not working | Bug Report |\n| Feature, enhancement, add, new | Feature Request |\n| Task, chore, refactor, update | Task |\n\n## Updating Issues\n\nUse `gh api` with PATCH:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fissues\u002F{number} \\\n  -X PATCH \\\n  -f state=closed \\\n  -f title=\"Updated title\" \\\n  --jq '{number, html_url}'\n```\n\nOnly include fields you want to change. Available fields: `title`, `body`, `state` (open\u002Fclosed), `labels`, `assignees`, `milestone`.\n\n## Examples\n\n### Example 1: Bug Report\n\n**User**: \"Create a bug issue - the login page crashes when using SSO\"\n\n**Action**: \n```bash\ngh api repos\u002Fgithub\u002Fawesome-copilot\u002Fissues \\\n  -X POST \\\n  -f title=\"Login page crashes when using SSO\" \\\n  -f type=\"Bug\" \\\n  -f body=\"## Description\nThe login page crashes when users attempt to authenticate using SSO.\n\n## Steps to Reproduce\n1. Navigate to login page\n2. Click 'Sign in with SSO'\n3. Page crashes\n\n## Expected Behavior\nSSO authentication should complete and redirect to dashboard.\n\n## Actual Behavior\nPage becomes unresponsive and displays error.\" \\\n  --jq '{number, html_url}'\n```\n\n### Example 2: Feature Request\n\n**User**: \"Create a feature request for dark mode with high priority\"\n\n**Action**:\n```bash\ngh api repos\u002Fgithub\u002Fawesome-copilot\u002Fissues \\\n  -X POST \\\n  -f title=\"Add dark mode support\" \\\n  -f type=\"Feature\" \\\n  -f 'labels[]=high-priority' \\\n  -f body=\"## Summary\nAdd dark mode theme option for improved user experience and accessibility.\n\n## Motivation\n- Reduces eye strain in low-light environments\n- Increasingly expected by users\n\n## Proposed Solution\nImplement theme toggle with system preference detection.\n\n## Acceptance Criteria\n- [ ] Toggle switch in settings\n- [ ] Persists user preference\n- [ ] Respects system preference by default\" \\\n  --jq '{number, html_url}'\n```\n\n## Common Labels\n\nUse these standard labels when applicable:\n\n| Label | Use For |\n|-------|---------|\n| `bug` | Something isn't working |\n| `enhancement` | New feature or improvement |\n| `documentation` | Documentation updates |\n| `good first issue` | Good for newcomers |\n| `help wanted` | Extra attention needed |\n| `question` | Further information requested |\n| `wontfix` | Will not be addressed |\n| `duplicate` | Already exists |\n| `high-priority` | Urgent issues |\n\n## Tips\n\n- Always confirm the repository context before creating issues\n- Ask for missing critical information rather than guessing\n- Link related issues when known: `Related to #123`\n- For updates, fetch current issue first to preserve unchanged fields\n\n## Extended Capabilities\n\nThe following features require REST or GraphQL APIs beyond the basic MCP tools. Each is documented in its own reference file so the agent only loads the knowledge it needs.\n\n| Capability | When to use | Reference |\n|------------|-------------|-----------|\n| Advanced search | Complex queries with boolean logic, date ranges, cross-repo search, issue field filters (`field.name:value`) | [references\u002Fsearch.md](references\u002Fsearch.md) |\n| Sub-issues & parent issues | Breaking work into hierarchical tasks | [references\u002Fsub-issues.md](references\u002Fsub-issues.md) |\n| Milestones | Create, read, update, close, reopen, delete milestones and manage milestone issues | [references\u002Fmilestones.md](references\u002Fmilestones.md) |\n| Labels | Discover, create, rename, recolor, and delete repository labels; add or replace labels on an issue | [references\u002Flabels.md](references\u002Flabels.md) |\n| Issue dependencies | Tracking blocked-by \u002F blocking relationships | [references\u002Fdependencies.md](references\u002Fdependencies.md) |\n| Issue types (advanced) | GraphQL operations beyond MCP `list_issue_types` \u002F `type` param | [references\u002Fissue-types.md](references\u002Fissue-types.md) |\n| Projects V2 | Project boards, progress reports, field management | [references\u002Fprojects.md](references\u002Fprojects.md) |\n| Issue fields | Custom metadata: dates, priority, text, numbers (private preview) | [references\u002Fissue-fields.md](references\u002Fissue-fields.md) |\n| Images in issues | Embedding images in issue bodies and comments via CLI | [references\u002Fimages.md](references\u002Fimages.md) |\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fgithub-issues",5340,"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 13:41:32",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add github\u002Fawesome-copilot --skill github-issues",{"tool":68,"command":69},"bunx","bunx skills add github\u002Fawesome-copilot --skill github-issues",{"tool":71,"command":72},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill github-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002FSKILL.md",true,[76,82,86,90,94,98,102,106,110,114,118,122,126],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"AGENT-BRIEF.md","REFERENCE","参考文档",7942,"https:\u002F\u002Fgithub.com\u002FHasarAli\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot-agents\u002Fskills\u002Ftriage\u002FAGENT-BRIEF.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"agents\u002Fopenai.yaml",135,"https:\u002F\u002Fgithub.com\u002FHasarAli\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot-agents\u002Fskills\u002Ftriage\u002Fagents\u002Fopenai.yaml",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"OUT-OF-SCOPE.md",4667,"https:\u002F\u002Fgithub.com\u002FHasarAli\u002Fdotfiles\u002Fblob\u002Fmain\u002Fdot-agents\u002Fskills\u002Ftriage\u002FOUT-OF-SCOPE.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdependencies.md",1887,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fdependencies.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fimages.md",4769,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fimages.md",{"path":99,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fissue-fields.md",7822,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fissue-fields.md",{"path":103,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fissue-types.md",1741,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fissue-types.md",{"path":107,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Flabels.md",5299,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Flabels.md",{"path":111,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fmilestones.md",2469,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fmilestones.md",{"path":115,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fprojects.md",8609,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fprojects.md",{"path":119,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fsearch.md",7261,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fsearch.md",{"path":123,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fsub-issues.md",3720,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Fsub-issues.md",{"path":127,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ftemplates.md",1384,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-issues\u002Freferences\u002Ftemplates.md",[131,161,188,217,250,267],{"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":141,"publishedAt":47},"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",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,145,146,26,147,148,149,150,151,152,153,154,155,156,157,158,159,160],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":47},"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",[167],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[169,170,171,38,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187],"distribution","skill distribution audit","audit","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":200,"publishedAt":47},"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",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":198,"taxonomyTypeDesc":199},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[201,202,203,204,205,206,174,146,207,208,209,210,211,212,213,157,214,215,216,46],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":47},"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",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":196,"categoryName":197,"taxonomyType":198,"taxonomyTypeDesc":199},[229,230,231,232,233,234,235,236,237,41,238,239,240,241,242,26,243,244,245,246,247,174,248,249],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":251,"name":252,"nameZh":6,"description":253,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":254,"licenseFileUrl":255,"sourceHtmlUrl":256,"categories":257,"keywords":263,"publishedAt":47},"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",[258,259,262],{"categoryNo":225,"categoryName":226,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":260,"categoryName":261,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[264,38,41,265,266],"resemble detect","https","identity",{"skillNo":268,"name":269,"nameZh":6,"description":270,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":254,"licenseFileUrl":271,"sourceHtmlUrl":272,"categories":273,"keywords":278,"publishedAt":47},"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",[274,277],{"categoryNo":275,"categoryName":276,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[279,280,281,282,202,147,9,171,283,284,265,285,286,287,288,289,290,291,36,292,293,294,155,295,296,297,298],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","verified","multi-model","three","coverage","model","regression","structural"]