[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGSSTX01K1SF73VTW372Z3":3,"skill-same:01M7BGSSTX01K1SF73VTW372Z3":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},"01M7BGSSTX01K1SF73VTW372Z3","repository-health-review",null,"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.","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\u002Frepository-health-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: repository-health-review\ndescription: \"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.\"\n---\n\n# Assessing repository health\n\nProduce an evidence-backed picture of how a repository is doing across a few\nindependent dimensions.\n\n**This workflow makes no changes.** Every tool it uses is read-only. If a specific\nissue, alert or pull request needs action, that is separate work — name it and hand it\nover rather than starting it here.\n\n## Sequence\n\nGather each dimension independently, so one unavailable source does not sink the\nreport.\n\n1. **Activity.** `list_commits` with `since` set to ninety days ago gives commit\n   volume and who is contributing. `list_releases` gives cadence — the gaps between\n   `published_at` values say more than the count.\n2. **Branch hygiene.** `list_branches`, then check the age of each branch's head\n   commit. Many long-untouched branches usually mean the project does not prune, which\n   is a mild signal on its own and a stronger one alongside slow pull request flow.\n3. **Flow.** `list_pull_requests` with `state: open`, `sort: created` and\n   `direction: asc` puts the oldest first; the age of the oldest and the shape of the\n   distribution are the numbers worth reporting. `list_issues` with `state: OPEN`,\n   `orderBy: CREATED_AT` and `direction: ASC` does the same for issues.\n4. **CI reliability.** `actions_list` with `method: list_workflow_runs`, filtered to\n   the default branch, over a recent window. The ratio of `conclusion: success` to\n   failures on the default branch is the signal; failures on feature branches are\n   expected and are not.\n5. **Maintainer coverage.** `list_repository_collaborators` shows how many people can maintain\n   the repository. One active committer is a risk worth naming plainly.\n6. **Outstanding risk.** `list_code_scanning_alerts` and `list_dependabot_alerts` with\n   `state: open`, **counted by severity only**. Do not open individual alerts here.\n7. **Report per dimension**, each with the numbers behind it, and state which\n   dimensions could not be assessed.\n\n## Decision points\n\n- **Absent history is not poor health.** A repository with few commits, no releases\n  and no alerts may be new. Say *insufficient history* rather than scoring it.\n- **Low activity is not decay.** A stable, finished library should look quiet. Weigh\n  activity against open issues and unanswered pull requests, not on its own.\n- **What counts as stale** depends on the project's own cadence. Derive the threshold\n  from its release and merge intervals rather than importing a fixed number, and state\n  the threshold you used.\n- **When to stop.** This produces an assessment. If it surfaces something urgent — a\n  critical alert, a default branch that has been failing for weeks — name it clearly\n  and hand it over.\n\n## Fields that matter\n\n- `published_at` across releases — the intervals are the cadence.\n- The head commit date per branch — branch names carry no age.\n- `created_at` on the oldest open pull request — a single number that captures review\n  responsiveness better than a count.\n- `conclusion` and `head_branch` on workflow runs — filter to the default branch, or\n  the failure rate is meaningless.\n- `state` on alerts — count `open` only; `dismissed` and `fixed` are noise here.\n- `affiliation` on collaborators — `direct` and `outside` answer different questions\n  about who really maintains the repository.\n\n## Confirm before changing anything\n\nNothing here changes anything, so no confirmation is needed to run it. If the\nassessment leads to a proposal — pruning branches, closing stale issues, upgrading a\ndependency — that proposal is a separate decision that needs its own agreement before\nanyone acts.\n\n## Empty and failure cases\n\n- **A dimension cannot be assessed** — mark it *not assessed* and name the reason.\n  Never infer health from a missing signal, and never let one unavailable source\n  suppress the rest of the report.\n- **No releases** — report no release history rather than a bad cadence; plenty of\n  repositories legitimately never release.\n- **No open issues or pull requests** — that is a clean result for flow, but check\n  activity before calling it healthy, since it also describes an abandoned repository.\n- **Alert sources unavailable** — say the risk dimension was not assessed. An empty\n  result and a disabled feature are different answers.\n- **A very large repository** — page rather than raising limits, and if a dimension is\n  too large to sample fairly, say the number is approximate and how it was derived.\n","# Assessing repository health\n\nProduce an evidence-backed picture of how a repository is doing across a few\nindependent dimensions.\n\n**This workflow makes no changes.** Every tool it uses is read-only. If a specific\nissue, alert or pull request needs action, that is separate work — name it and hand it\nover rather than starting it here.\n\n## Sequence\n\nGather each dimension independently, so one unavailable source does not sink the\nreport.\n\n1. **Activity.** `list_commits` with `since` set to ninety days ago gives commit\n   volume and who is contributing. `list_releases` gives cadence — the gaps between\n   `published_at` values say more than the count.\n2. **Branch hygiene.** `list_branches`, then check the age of each branch's head\n   commit. Many long-untouched branches usually mean the project does not prune, which\n   is a mild signal on its own and a stronger one alongside slow pull request flow.\n3. **Flow.** `list_pull_requests` with `state: open`, `sort: created` and\n   `direction: asc` puts the oldest first; the age of the oldest and the shape of the\n   distribution are the numbers worth reporting. `list_issues` with `state: OPEN`,\n   `orderBy: CREATED_AT` and `direction: ASC` does the same for issues.\n4. **CI reliability.** `actions_list` with `method: list_workflow_runs`, filtered to\n   the default branch, over a recent window. The ratio of `conclusion: success` to\n   failures on the default branch is the signal; failures on feature branches are\n   expected and are not.\n5. **Maintainer coverage.** `list_repository_collaborators` shows how many people can maintain\n   the repository. One active committer is a risk worth naming plainly.\n6. **Outstanding risk.** `list_code_scanning_alerts` and `list_dependabot_alerts` with\n   `state: open`, **counted by severity only**. Do not open individual alerts here.\n7. **Report per dimension**, each with the numbers behind it, and state which\n   dimensions could not be assessed.\n\n## Decision points\n\n- **Absent history is not poor health.** A repository with few commits, no releases\n  and no alerts may be new. Say *insufficient history* rather than scoring it.\n- **Low activity is not decay.** A stable, finished library should look quiet. Weigh\n  activity against open issues and unanswered pull requests, not on its own.\n- **What counts as stale** depends on the project's own cadence. Derive the threshold\n  from its release and merge intervals rather than importing a fixed number, and state\n  the threshold you used.\n- **When to stop.** This produces an assessment. If it surfaces something urgent — a\n  critical alert, a default branch that has been failing for weeks — name it clearly\n  and hand it over.\n\n## Fields that matter\n\n- `published_at` across releases — the intervals are the cadence.\n- The head commit date per branch — branch names carry no age.\n- `created_at` on the oldest open pull request — a single number that captures review\n  responsiveness better than a count.\n- `conclusion` and `head_branch` on workflow runs — filter to the default branch, or\n  the failure rate is meaningless.\n- `state` on alerts — count `open` only; `dismissed` and `fixed` are noise here.\n- `affiliation` on collaborators — `direct` and `outside` answer different questions\n  about who really maintains the repository.\n\n## Confirm before changing anything\n\nNothing here changes anything, so no confirmation is needed to run it. If the\nassessment leads to a proposal — pruning branches, closing stale issues, upgrading a\ndependency — that proposal is a separate decision that needs its own agreement before\nanyone acts.\n\n## Empty and failure cases\n\n- **A dimension cannot be assessed** — mark it *not assessed* and name the reason.\n  Never infer health from a missing signal, and never let one unavailable source\n  suppress the rest of the report.\n- **No releases** — report no release history rather than a bad cadence; plenty of\n  repositories legitimately never release.\n- **No open issues or pull requests** — that is a clean result for flow, but check\n  activity before calling it healthy, since it also describes an abandoned repository.\n- **Alert sources unavailable** — say the risk dimension was not assessed. An empty\n  result and a disabled feature are different answers.\n- **A very large repository** — page rather than raising limits, and if a dimension is\n  too large to sample fairly, say the number is approximate and how it was derived.\n",{"name":5,"description":7},"main","0663b830582af923e30fb14cb2e10dd3248baa86","pkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frepository-health-review",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 repository-health-review",{"tool":39,"command":40},"bunx","bunx skills add github\u002Fgithub-mcp-server --skill repository-health-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add github\u002Fgithub-mcp-server --skill repository-health-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server\u002Fblob\u002Fmain\u002Fpkg\u002Fskills\u002Fcatalog\u002Fskills\u002Frepository-health-review\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},"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":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},"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":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},"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":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},"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",[],[]]