[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGSYRT2YATCHJVYG1HJV58":3,"skill-same:01M7BGSYRT2YATCHJVYG1HJV58":53},{"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},"01M7BGSYRT2YATCHJVYG1HJV58","security-alert-triage",null,"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.","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\u002Fsecurity-alert-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-alert-triage\ndescription: \"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.\"\n---\n\n# Triaging security alerts\n\nTurn four separate alert streams into one ordered list of decisions, each backed by\nevidence a maintainer can check.\n\n**This server reads alerts; it does not resolve them.** No tool here dismisses an\nalert, merges a fix, or revokes a credential. The output is a recommendation with\nevidence.\n\n## Sequence\n\n1. **Inventory every source that answers.** `list_code_scanning_alerts`,\n   `list_dependabot_alerts` and `list_secret_scanning_alerts` with `state: open`.\n   Enumerate `list_repository_security_advisories` separately: omit `state` for all\n   advisories, or use `triage`, `draft`, `published` or `closed`. Record which\n   sources answered and which did not — the difference matters, see the failure cases.\n   When the question spans an organisation rather than one repository,\n   `list_org_repository_security_advisories` with `org` gives the same advisory picture\n   across every repository in it, and is the right starting point before fanning out.\n2. **Handle secret scanning first**, ahead of any ordering by severity. A live\n   credential is the only alert type where delay keeps causing harm.\n3. **Order the rest by exploitability, not by count.** `severity` narrows the field;\n   whether the code is reachable decides it.\n4. **Read the individual alert** for anything you intend to recommend on:\n   `get_code_scanning_alert`, `get_dependabot_alert` or `get_secret_scanning_alert`\n   with the alert number. List responses are deliberately thin.\n5. **Ground it in the code.** For a code scanning alert, read the flagged location\n   with `get_file_contents`. For a dependency alert, `search_code` for the vulnerable\n   symbol to find out whether the project reaches the affected path at all.\n6. **Look up the advisory** behind a dependency alert with\n   `list_global_security_advisories` or `get_global_security_advisory` by GHSA or CVE\n   id. The advisory carries the patched versions and the real-world conditions.\n7. **Recommend**, using the decision points below, naming the evidence each\n   recommendation rests on.\n\n`references\u002Falert-sources.md` maps each source to its tools, its identifying fields,\nand what resolution means there.\n\n## Secret scanning comes first\n\nAn open secret scanning alert on a real credential means something is exposed right\nnow. The order is always: revoke, then rotate, then remove from history, then close\nthe alert. Revocation happens outside this server, so escalate to a person\nimmediately and name the credential type and where it appeared. Never recommend\ndismissing a secret alert as a false positive without someone who can check the\ncredential confirming it — a wrongly dismissed live key stays live.\n\n## Decision points\n\n- **Fix now** — reachable, exploitable, and a fix exists. For a dependency that means\n  `first_patched_version` is populated. Name the version to move to.\n- **Schedule** — real, but not reachable in this project, or the fix needs a major\n  upgrade. Give the reasoning and the trigger that would promote it.\n- **Recommend dismissal** — genuinely not applicable: test-only code, a pattern the\n  rule misreads, an unused path. State the rule, why it does not apply, and which\n  dismissal reason fits. A person makes the call.\n- **Escalate** — live credentials, anything already exploited, or anything you cannot\n  assess with the data available. Escalating is a valid outcome, not a failure.\n\nSeverity is an input, not the answer. A critical alert in code that never runs\noutranks nothing; a moderate one on a public entry point may outrank everything.\n\n## Fields that matter\n\n- `state` on alerts — `open` means outstanding. Advisory states are separate:\n  `triage`, `draft`, `published`, `closed`; publication does not mean a fix is shipped.\n- `rule.id` and `rule.security_severity_level` on a code scanning alert — the id lets\n  you compare like with like across repositories.\n- `most_recent_instance.location` — the file and line to actually read.\n- `dependency.package` with `security_vulnerability.first_patched_version` — the two\n  fields a dependency recommendation is built from.\n- `secret_type` — identifies what kind of credential leaked, which decides how it is\n  revoked and who owns the revocation.\n- `resolution` on a closed secret alert — `revoked` is the only value that means the\n  credential is dead.\n\n## Confirm before anything is acted on\n\nEvery action this workflow leads to happens elsewhere: dismissing, upgrading,\nrevoking. Present the ordered recommendations with their evidence and get explicit\nagreement before anyone acts. Never describe an alert as resolved on the strength of\na recommendation.\n\n## Empty and failure cases\n\n- **An empty list and a disabled feature look alike.** An empty result means no open\n  alerts. An error mentioning permissions, or a feature not being enabled, means the\n  source was not checked. Report those separately, and never fold an unchecked source\n  into a clean result.\n- **A source is unavailable** — name it as not assessed and continue with the rest.\n- **No open alerts anywhere** — say which sources were checked and that all were\n  clean. The list of sources is the useful part of that answer.\n- **An advisory lookup fails** — recommend on the alert data alone and say the\n  advisory could not be read.\n","# Triaging security alerts\n\nTurn four separate alert streams into one ordered list of decisions, each backed by\nevidence a maintainer can check.\n\n**This server reads alerts; it does not resolve them.** No tool here dismisses an\nalert, merges a fix, or revokes a credential. The output is a recommendation with\nevidence.\n\n## Sequence\n\n1. **Inventory every source that answers.** `list_code_scanning_alerts`,\n   `list_dependabot_alerts` and `list_secret_scanning_alerts` with `state: open`.\n   Enumerate `list_repository_security_advisories` separately: omit `state` for all\n   advisories, or use `triage`, `draft`, `published` or `closed`. Record which\n   sources answered and which did not — the difference matters, see the failure cases.\n   When the question spans an organisation rather than one repository,\n   `list_org_repository_security_advisories` with `org` gives the same advisory picture\n   across every repository in it, and is the right starting point before fanning out.\n2. **Handle secret scanning first**, ahead of any ordering by severity. A live\n   credential is the only alert type where delay keeps causing harm.\n3. **Order the rest by exploitability, not by count.** `severity` narrows the field;\n   whether the code is reachable decides it.\n4. **Read the individual alert** for anything you intend to recommend on:\n   `get_code_scanning_alert`, `get_dependabot_alert` or `get_secret_scanning_alert`\n   with the alert number. List responses are deliberately thin.\n5. **Ground it in the code.** For a code scanning alert, read the flagged location\n   with `get_file_contents`. For a dependency alert, `search_code` for the vulnerable\n   symbol to find out whether the project reaches the affected path at all.\n6. **Look up the advisory** behind a dependency alert with\n   `list_global_security_advisories` or `get_global_security_advisory` by GHSA or CVE\n   id. The advisory carries the patched versions and the real-world conditions.\n7. **Recommend**, using the decision points below, naming the evidence each\n   recommendation rests on.\n\n`references\u002Falert-sources.md` maps each source to its tools, its identifying fields,\nand what resolution means there.\n\n## Secret scanning comes first\n\nAn open secret scanning alert on a real credential means something is exposed right\nnow. The order is always: revoke, then rotate, then remove from history, then close\nthe alert. Revocation happens outside this server, so escalate to a person\nimmediately and name the credential type and where it appeared. Never recommend\ndismissing a secret alert as a false positive without someone who can check the\ncredential confirming it — a wrongly dismissed live key stays live.\n\n## Decision points\n\n- **Fix now** — reachable, exploitable, and a fix exists. For a dependency that means\n  `first_patched_version` is populated. Name the version to move to.\n- **Schedule** — real, but not reachable in this project, or the fix needs a major\n  upgrade. Give the reasoning and the trigger that would promote it.\n- **Recommend dismissal** — genuinely not applicable: test-only code, a pattern the\n  rule misreads, an unused path. State the rule, why it does not apply, and which\n  dismissal reason fits. A person makes the call.\n- **Escalate** — live credentials, anything already exploited, or anything you cannot\n  assess with the data available. Escalating is a valid outcome, not a failure.\n\nSeverity is an input, not the answer. A critical alert in code that never runs\noutranks nothing; a moderate one on a public entry point may outrank everything.\n\n## Fields that matter\n\n- `state` on alerts — `open` means outstanding. Advisory states are separate:\n  `triage`, `draft`, `published`, `closed`; publication does not mean a fix is shipped.\n- `rule.id` and `rule.security_severity_level` on a code scanning alert — the id lets\n  you compare like with like across repositories.\n- `most_recent_instance.location` — the file and line to actually read.\n- `dependency.package` with `security_vulnerability.first_patched_version` — the two\n  fields a dependency recommendation is built from.\n- `secret_type` — identifies what kind of credential leaked, which decides how it is\n  revoked and who owns the revocation.\n- `resolution` on a closed secret alert — `revoked` is the only value that means the\n  credential is dead.\n\n## Confirm before anything is acted on\n\nEvery action this workflow leads to happens elsewhere: dismissing, upgrading,\nrevoking. Present the ordered recommendations with their evidence and get explicit\nagreement before anyone acts. Never describe an alert as resolved on the strength of\na recommendation.\n\n## Empty and failure cases\n\n- **An empty list and a disabled feature look alike.** An empty result means no open\n  alerts. An error mentioning permissions, or a feature not being enabled, means the\n  source was not checked. Report those separately, and never fold an unchecked source\n  into a clean result.\n- **A source is unavailable** — name it as not assessed and continue with the rest.\n- **No open alerts anywhere** — say which sources were checked and that all were\n  clean. The list of sources is the useful part of that answer.\n- **An advisory lookup fails** — recommend on the alert data alone and say the\n  advisory could not be read.\n",{"name":5,"description":7},"main","0663b830582af923e30fb14cb2e10dd3248baa86","pkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fsecurity-alert-triage",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 security-alert-triage",{"tool":39,"command":40},"bunx","bunx skills add github\u002Fgithub-mcp-server --skill security-alert-triage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add github\u002Fgithub-mcp-server --skill security-alert-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fsecurity-alert-triage\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Falert-sources.md","REFERENCE","参考文档",3215,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fsecurity-alert-triage\u002Freferences\u002Falert-sources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BGS6SQB8WA0ZRKTDAT0YS1","pull-request-review-feedback","USE FOR: working through review feedback left on a pull request — reading each unresolved thread, deciding what to change, replying to the reviewer, and resolving threads. NOT FOR: producing a review of a pull request, merging one, or clearing a notification inbox.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Fpull-request-review-feedback\u002FSKILL.md",[],[]]