[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGRD47NY0N4KYYZMFJSGTR":3,"skill-same:01M7BGRD47NY0N4KYYZMFJSGTR":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BGRD47NY0N4KYYZMFJSGTR","label-scheme-management",null,"USE FOR: curating the label vocabulary a repository uses — adding ones it lacks, auditing which are actually applied, renaming and recolouring them, merging overlapping ones, and tidying away the unused. NOT FOR: applying an existing label to an issue, or deciding which issues matter.","github\u002Fgithub-mcp-server","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M7BGQFA8MGC5Z2H648SBHW0V",34465,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Flabel-scheme-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: label-scheme-management\ndescription: \"USE FOR: curating the label vocabulary a repository uses — adding ones it lacks, auditing which are actually applied, renaming and recolouring them, merging overlapping ones, and tidying away the unused. NOT FOR: applying an existing label to an issue, or deciding which issues matter.\"\n---\n\n# Curating what a repository's labels mean\n\nLabels are a shared vocabulary, and every change to one changes the meaning of every\nissue already carrying it. This is a repository-wide edit dressed up as a small one.\n\n## Sequence\n\n1. **See the whole set at once.** `list_label` returns every label ordered by issue\n   count, most used first. That ordering is the audit: the tail is where the dead\n   vocabulary lives.\n2. **Find out what is actually in use.** For anything you are considering changing,\n   `list_issues` filtered by that label, omitting `state` to include open and closed issues, shows what carries\n   it. A label with no issues has no cost to retire; one with two hundred is load-bearing.\n3. **Read the one you are about to change.** `get_label` returns its exact name, colour\n   and description. Names are case-sensitive in ways that are easy to get wrong, and the\n   description is often the only record of what the label was meant to distinguish.\n4. **Make the change.** `label_write` with `method` set to `create`, `update` or\n   `delete`. Renaming is `update` with `new_name`.\n5. **Report what moved**, including how many issues were affected by each change.\n\n## Decision points\n\n- **Retire or leave?** A label unused for a long time is clutter; a label used once a\n  year is a category someone will look for. Check the age of the issues carrying it\n  before calling it dead.\n- **Rename or create-and-migrate?** `update` with `new_name` carries every existing\n  issue with it, keeping the history intact. Creating a second label and applying it by\n  hand splits the set in two, and the older issues stop appearing in the filter people\n  use. Rename unless the meaning is genuinely changing.\n- **Merging two overlapping labels is not one call.** The issues on the losing label\n  have to be moved before it is removed, and moving them is issue-by-issue work that\n  belongs to whoever is triaging. Say that rather than removing the label and orphaning\n  the classification.\n- **Colour carries meaning.** Projects usually encode severity or kind in hue. Read the\n  existing set before picking; a new colour that clashes with an established convention\n  is worse than a dull one that fits.\n- **Descriptions are worth writing.** A label whose meaning has to be inferred from its\n  name gets applied inconsistently, and that is the actual cause of most label sprawl.\n\n## Fields that matter\n\n- `name` — required for every operation, and it is the identifier. For a rename it is\n  the *current* name; `new_name` is the target.\n- `color` — six hex characters with no leading marker. Required when creating.\n- `description` — optional, and the difference between a scheme people follow and one\n  they guess at.\n- `method` — `create`, `update`, `delete`. There is no bulk form; each label is its own\n  call and its own decision.\n\n## Confirm before changing the scheme\n\n- **Present the full intended set of changes before the first call** — every label, what\n  happens to it, and how many issues it currently carries. These changes are visible to\n  everyone using the repository immediately.\n- **Removing a label removes it from every issue that had it.** The issues survive; the\n  classification does not, and it cannot be restored by recreating the label. State the\n  issue count and get explicit agreement naming that label.\n- **Renaming is safer but not invisible** — saved filters, automation and templates that\n  reference the old name stop matching. Say so when the label is one of the heavily used\n  ones.\n- **Never infer the set from a pattern.** \"Clean up the unused labels\" is an instruction\n  to produce a list with counts and ask, not an instruction to remove anything.\n- **Creating labels wholesale is also a scheme change.** Importing a standard set into a\n  repository that already has its own convention is a bigger change than it looks;\n  propose it as one.\n\n## Empty and failure cases\n\n- **No labels at all** — a repository with an empty set has usually had them removed\n  deliberately, or is new. Ask which before proposing a scheme.\n- **A label is already present when creating** — names collide case-insensitively even\n  though they display with their original case. Read the existing one and decide whether\n  to update it rather than retrying.\n- **A rename is rejected because the target exists** — this is the merge case, not a\n  rename. Two labels cannot be collapsed by renaming one onto the other; the issues have\n  to be moved first.\n- **The account cannot write** — label administration usually needs more access than\n  commenting does. Report the intended changes as a list so someone else can apply them.\n- **A label appears unused but the count is from open issues only** — omit `state`\n  when checking before concluding. Closed issues carry labels too, and they are the\n  history.\n\n## Report coverage\n\nSay what was checked and what was not, so an unchecked label is not read as a clean one:\n\n| Label | Issues carrying it | Change | Result |\n| --- | --- | --- | --- |\n| bug | 214 | recoloured | ✅ applied |\n| wontfix | 0 | proposed for removal | ⚠️ awaiting agreement |\n| stale | not checked | none | ⚠️ usage not established |\n","# Curating what a repository's labels mean\n\nLabels are a shared vocabulary, and every change to one changes the meaning of every\nissue already carrying it. This is a repository-wide edit dressed up as a small one.\n\n## Sequence\n\n1. **See the whole set at once.** `list_label` returns every label ordered by issue\n   count, most used first. That ordering is the audit: the tail is where the dead\n   vocabulary lives.\n2. **Find out what is actually in use.** For anything you are considering changing,\n   `list_issues` filtered by that label, omitting `state` to include open and closed issues, shows what carries\n   it. A label with no issues has no cost to retire; one with two hundred is load-bearing.\n3. **Read the one you are about to change.** `get_label` returns its exact name, colour\n   and description. Names are case-sensitive in ways that are easy to get wrong, and the\n   description is often the only record of what the label was meant to distinguish.\n4. **Make the change.** `label_write` with `method` set to `create`, `update` or\n   `delete`. Renaming is `update` with `new_name`.\n5. **Report what moved**, including how many issues were affected by each change.\n\n## Decision points\n\n- **Retire or leave?** A label unused for a long time is clutter; a label used once a\n  year is a category someone will look for. Check the age of the issues carrying it\n  before calling it dead.\n- **Rename or create-and-migrate?** `update` with `new_name` carries every existing\n  issue with it, keeping the history intact. Creating a second label and applying it by\n  hand splits the set in two, and the older issues stop appearing in the filter people\n  use. Rename unless the meaning is genuinely changing.\n- **Merging two overlapping labels is not one call.** The issues on the losing label\n  have to be moved before it is removed, and moving them is issue-by-issue work that\n  belongs to whoever is triaging. Say that rather than removing the label and orphaning\n  the classification.\n- **Colour carries meaning.** Projects usually encode severity or kind in hue. Read the\n  existing set before picking; a new colour that clashes with an established convention\n  is worse than a dull one that fits.\n- **Descriptions are worth writing.** A label whose meaning has to be inferred from its\n  name gets applied inconsistently, and that is the actual cause of most label sprawl.\n\n## Fields that matter\n\n- `name` — required for every operation, and it is the identifier. For a rename it is\n  the *current* name; `new_name` is the target.\n- `color` — six hex characters with no leading marker. Required when creating.\n- `description` — optional, and the difference between a scheme people follow and one\n  they guess at.\n- `method` — `create`, `update`, `delete`. There is no bulk form; each label is its own\n  call and its own decision.\n\n## Confirm before changing the scheme\n\n- **Present the full intended set of changes before the first call** — every label, what\n  happens to it, and how many issues it currently carries. These changes are visible to\n  everyone using the repository immediately.\n- **Removing a label removes it from every issue that had it.** The issues survive; the\n  classification does not, and it cannot be restored by recreating the label. State the\n  issue count and get explicit agreement naming that label.\n- **Renaming is safer but not invisible** — saved filters, automation and templates that\n  reference the old name stop matching. Say so when the label is one of the heavily used\n  ones.\n- **Never infer the set from a pattern.** \"Clean up the unused labels\" is an instruction\n  to produce a list with counts and ask, not an instruction to remove anything.\n- **Creating labels wholesale is also a scheme change.** Importing a standard set into a\n  repository that already has its own convention is a bigger change than it looks;\n  propose it as one.\n\n## Empty and failure cases\n\n- **No labels at all** — a repository with an empty set has usually had them removed\n  deliberately, or is new. Ask which before proposing a scheme.\n- **A label is already present when creating** — names collide case-insensitively even\n  though they display with their original case. Read the existing one and decide whether\n  to update it rather than retrying.\n- **A rename is rejected because the target exists** — this is the merge case, not a\n  rename. Two labels cannot be collapsed by renaming one onto the other; the issues have\n  to be moved first.\n- **The account cannot write** — label administration usually needs more access than\n  commenting does. Report the intended changes as a list so someone else can apply them.\n- **A label appears unused but the count is from open issues only** — omit `state`\n  when checking before concluding. Closed issues carry labels too, and they are the\n  history.\n\n## Report coverage\n\nSay what was checked and what was not, so an unchecked label is not read as a clean one:\n\n| Label | Issues carrying it | Change | Result |\n| --- | --- | --- | --- |\n| bug | 214 | recoloured | ✅ applied |\n| wontfix | 0 | proposed for removal | ⚠️ awaiting agreement |\n| stale | not checked | none | ⚠️ usage not established |\n",{"name":5,"description":7},"main","0663b830582af923e30fb14cb2e10dd3248baa86","pkg\u002Fskills\u002Fcatalog\u002Fskills\u002Flabel-scheme-management",5349,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-14 04:25:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add github\u002Fgithub-mcp-server --skill label-scheme-management",{"tool":39,"command":40},"bunx","bunx skills add github\u002Fgithub-mcp-server --skill label-scheme-management",{"tool":42,"command":43},"pnpm","pnpm dlx skills add github\u002Fgithub-mcp-server --skill label-scheme-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Flabel-scheme-management\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BGT3EPF1HCGVD1FREPH341","workflow-failure-triage","USE FOR: diagnosing a failing GitHub Actions workflow run — a build gone red, which jobs failed, what their logs say, where the failing step is, and whether a rerun is justified. NOT FOR: judging long-term reliability trends across a repository, or deciding whether a change is ready to ship.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fworkflow-failure-triage\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BGSYRT2YATCHJVYG1HJV58","security-alert-triage","USE FOR: investigating GitHub security alerts — code scanning, Dependabot, secret scanning and advisories — and deciding what to fix now, schedule, dismiss, or escalate. NOT FOR: summarising overall repository health, or reviewing feedback on a pull request.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fsecurity-alert-triage\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BGSSTX01K1SF73VTW372Z3","repository-health-review","USE FOR: judging how well a repository is maintained overall — release cadence, branch and proposal age, issue inflow, build reliability, how many people can maintain it, and outstanding alert counts. NOT FOR: acting on any individual issue, alert or proposed change, or cutting a specific release.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frepository-health-review\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BGSN2K6WD9PP5YWGV5XX6G","repository-discovery","USE FOR: finding a library, tool or organisation you cannot yet name, judging whether a candidate project is worth depending on, and keeping a starred shortlist useful. NOT FOR: searching inside a repository you have already chosen, or setting one up.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frepository-discovery\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BGSGH96DJFA2VTSKS57CAJ","repository-content-changes","USE FOR: changing what a repository holds or whether it exists at all — opening a working branch, committing files remotely, deleting what should go, and creating, forking or removing the repository itself. NOT FOR: proposing those changes for review, or reading code you do not intend to touch.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frepository-content-changes\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BGSCD3HCWAG7NX35VT8XG2","release-preparation","USE FOR: cutting a release of a repository — picking the version, assembling the changelog since the last tag, confirming the branch is releasable, and drafting release notes. NOT FOR: assessing overall repository health, triaging security alerts, or working an issue backlog.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frelease-preparation\u002FSKILL.md",[],[]]