[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736QT6FT3NFEC3ZCJMTJC54":3,"skill-same:01M736QT6FT3NFEC3ZCJMTJC54":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M736QT6FT3NFEC3ZCJMTJC54","issue-triage",null,"Analyze open GitHub or GitLab issues from `forge-cli inbox`, classify readiness versus blockers, and recommend an execution order; read-only unless the user explicitly asks for follow-up.","graysurf\u002Fagent-runtime-kit","graysurf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10785178?v=4","01M736PQHYKHFMNBYF8BT93NM4","01M736PQJWYH7G046WAN7EQCHD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fclaude\u002Fplugins\u002Fissue\u002Fskills\u002Fissue-triage\u002Fexpected\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: issue-triage\ndescription: >\n  Analyze open GitHub or GitLab issues from `forge-cli inbox`, classify\n  readiness versus blockers, and recommend an execution order; read-only\n  unless the user explicitly asks for follow-up.\n---\n\n# Issue Triage\n\nRead-only issue work selection for deciding what an agent can do now, what is\nblocked, and what order to recommend.\n\n## Contract\n\nPrereqs:\n\n- Run inside the target provider-backed git repository, or pass explicit\n  `--repo` and `--provider` options to `forge-cli`.\n- `forge-cli >=1.11.2` is installed from the released nils-cli package and available on\n  `PATH`.\n- Provider authentication is available for non-dry-run inbox and issue reads.\n- For implementation handoff, the normal implementation, issue follow-up, or\n  PR\u002FMR workflow is available.\n- Shared close\u002Fcomment rules in\n  `..\u002Fissue-follow-up\u002Freferences\u002Fissue-lifecycle.md` are known for any handoff.\n\nInputs:\n\n- User request to review current open issues, choose what to work on next,\n  identify blocked items, or recommend execution order.\n- Optional provider, repository, kind, item-type, limit, or GitLab host.\n- Optional instruction to include PR\u002FMR work; otherwise focus on issues.\n\nOutputs:\n\n- A concise triage report with candidate issues grouped by readiness.\n- A recommended execution order with reason, risk, blocker, and first action\n  for each ranked issue.\n- Clear handoff suggestion when an issue should move into `issue-follow-up`,\n  implementation, PR\u002FMR delivery, or comment-only maintenance.\n\nFailure modes:\n\n- `forge-cli inbox` fails because provider auth, permissions, network, or host\n  configuration is unavailable.\n- Inbox data is too thin to classify an issue and issue detail reads fail.\n- Issue state is ambiguous enough that proceeding would risk wrong provider\n  comments, code changes, or prioritization.\n\n## Entrypoint\n\nStart with the normalized inbox issue surface:\n\n```bash\nforge-cli inbox list --item-type issue --format json\nforge-cli inbox next --item-type issue --format json\n```\n\nPass provider and repository selectors through when needed:\n\n```bash\nforge-cli inbox list --provider github --repo owner\u002Fname --item-type issue --format json\nforge-cli inbox list --provider gitlab --gitlab-host gitlab.example.com --item-type issue --format json\n```\n\nWhen the inbox record does not contain enough context to judge readiness, read\nissue detail before deciding:\n\n```bash\nforge-cli issue view \"$ISSUE\" --format json\n```\n\n## Workflow\n\n1. Determine scope:\n   - Default to open issues only: `--item-type issue`.\n   - Include PR\u002FMR only when the user asks for broader work inbox triage.\n   - Keep provider selection inbox-local; use `--provider` only when the user\n     or repository context narrows the target.\n2. Collect candidates:\n   - Run `forge-cli inbox list --item-type issue --format json`.\n   - Run `forge-cli inbox next --item-type issue --format json` for the CLI's\n     bounded ranking signal.\n   - If a provider partially fails, continue with successful providers and\n     report the failed provider as a data gap.\n3. Enrich only as needed:\n   - Read the top candidates or ambiguous items with\n     `forge-cli issue view \"$ISSUE\" --format json`.\n   - Inspect body, labels, assignees, latest comments when available, linked\n     PR\u002FMR references, and explicit blocker language.\n4. Classify each candidate:\n   - `ready-now`: scope and next action are clear; no external decision,\n     permission, CI, review, or missing-data blocker is visible.\n   - `needs-clarification`: outcome, acceptance, owner, or first action is\n     unclear enough that execution should not start yet.\n   - `blocked`: waiting on external decision, user input, provider access,\n     review, CI, release, upstream issue, credentials, or unavailable evidence.\n   - `stale-or-low-value`: old, low-signal, duplicate-looking, or weakly tied\n     to the current repo or user request.\n5. Rank recommendations:\n   - Prefer ready-now issues that are small, well-scoped, high-impact, and have\n     clear validation.\n   - Prefer unblocking comments before implementation when a blocker can be\n     resolved with one concise question or checkpoint.\n   - Deprioritize issues that require broad planning, destructive operations,\n     unavailable credentials, or multi-repo coordination unless the user asked\n     for that scope.\n6. Report with evidence discipline:\n   - Separate facts from issue data, inferences from those facts, assumptions,\n     and open questions.\n   - For each recommended issue, include the issue URL or number, readiness\n     bucket, why now, first action, and the next workflow to use.\n   - Do not post comments, close issues, create branches, or start\n     implementation unless the user explicitly asks.\n\n## Handoff\n\n- Use `issue-follow-up` when the next action is provider-visible issue\n  maintenance, a blocker checkpoint, or a durable follow-up comment.\n- Use normal implementation and PR\u002FMR workflows when a ready-now issue has a\n  clear code or docs change and validation path.\n- If the best next action is a broader plan bundle or dispatch lane, say that\n  explicitly instead of silently expanding triage into planning.\n\n## Boundary\n\n`issue-triage` is a read-only selection and recommendation workflow. It uses\n`forge-cli inbox` as the candidate source and `forge-cli issue view` as optional\ncontext enrichment. It does not replace `issue-follow-up`, mutate provider\nstate, or implement the selected issue unless the user explicitly asks for that\nnext step.\n\nShared rules for follow-up comments and closure live in\n`..\u002Fissue-follow-up\u002Freferences\u002Fissue-lifecycle.md`.\n","# Issue Triage\n\nRead-only issue work selection for deciding what an agent can do now, what is\nblocked, and what order to recommend.\n\n## Contract\n\nPrereqs:\n\n- Run inside the target provider-backed git repository, or pass explicit\n  `--repo` and `--provider` options to `forge-cli`.\n- `forge-cli >=1.11.2` is installed from the released nils-cli package and available on\n  `PATH`.\n- Provider authentication is available for non-dry-run inbox and issue reads.\n- For implementation handoff, the normal implementation, issue follow-up, or\n  PR\u002FMR workflow is available.\n- Shared close\u002Fcomment rules in\n  `..\u002Fissue-follow-up\u002Freferences\u002Fissue-lifecycle.md` are known for any handoff.\n\nInputs:\n\n- User request to review current open issues, choose what to work on next,\n  identify blocked items, or recommend execution order.\n- Optional provider, repository, kind, item-type, limit, or GitLab host.\n- Optional instruction to include PR\u002FMR work; otherwise focus on issues.\n\nOutputs:\n\n- A concise triage report with candidate issues grouped by readiness.\n- A recommended execution order with reason, risk, blocker, and first action\n  for each ranked issue.\n- Clear handoff suggestion when an issue should move into `issue-follow-up`,\n  implementation, PR\u002FMR delivery, or comment-only maintenance.\n\nFailure modes:\n\n- `forge-cli inbox` fails because provider auth, permissions, network, or host\n  configuration is unavailable.\n- Inbox data is too thin to classify an issue and issue detail reads fail.\n- Issue state is ambiguous enough that proceeding would risk wrong provider\n  comments, code changes, or prioritization.\n\n## Entrypoint\n\nStart with the normalized inbox issue surface:\n\n```bash\nforge-cli inbox list --item-type issue --format json\nforge-cli inbox next --item-type issue --format json\n```\n\nPass provider and repository selectors through when needed:\n\n```bash\nforge-cli inbox list --provider github --repo owner\u002Fname --item-type issue --format json\nforge-cli inbox list --provider gitlab --gitlab-host gitlab.example.com --item-type issue --format json\n```\n\nWhen the inbox record does not contain enough context to judge readiness, read\nissue detail before deciding:\n\n```bash\nforge-cli issue view \"$ISSUE\" --format json\n```\n\n## Workflow\n\n1. Determine scope:\n   - Default to open issues only: `--item-type issue`.\n   - Include PR\u002FMR only when the user asks for broader work inbox triage.\n   - Keep provider selection inbox-local; use `--provider` only when the user\n     or repository context narrows the target.\n2. Collect candidates:\n   - Run `forge-cli inbox list --item-type issue --format json`.\n   - Run `forge-cli inbox next --item-type issue --format json` for the CLI's\n     bounded ranking signal.\n   - If a provider partially fails, continue with successful providers and\n     report the failed provider as a data gap.\n3. Enrich only as needed:\n   - Read the top candidates or ambiguous items with\n     `forge-cli issue view \"$ISSUE\" --format json`.\n   - Inspect body, labels, assignees, latest comments when available, linked\n     PR\u002FMR references, and explicit blocker language.\n4. Classify each candidate:\n   - `ready-now`: scope and next action are clear; no external decision,\n     permission, CI, review, or missing-data blocker is visible.\n   - `needs-clarification`: outcome, acceptance, owner, or first action is\n     unclear enough that execution should not start yet.\n   - `blocked`: waiting on external decision, user input, provider access,\n     review, CI, release, upstream issue, credentials, or unavailable evidence.\n   - `stale-or-low-value`: old, low-signal, duplicate-looking, or weakly tied\n     to the current repo or user request.\n5. Rank recommendations:\n   - Prefer ready-now issues that are small, well-scoped, high-impact, and have\n     clear validation.\n   - Prefer unblocking comments before implementation when a blocker can be\n     resolved with one concise question or checkpoint.\n   - Deprioritize issues that require broad planning, destructive operations,\n     unavailable credentials, or multi-repo coordination unless the user asked\n     for that scope.\n6. Report with evidence discipline:\n   - Separate facts from issue data, inferences from those facts, assumptions,\n     and open questions.\n   - For each recommended issue, include the issue URL or number, readiness\n     bucket, why now, first action, and the next workflow to use.\n   - Do not post comments, close issues, create branches, or start\n     implementation unless the user explicitly asks.\n\n## Handoff\n\n- Use `issue-follow-up` when the next action is provider-visible issue\n  maintenance, a blocker checkpoint, or a durable follow-up comment.\n- Use normal implementation and PR\u002FMR workflows when a ready-now issue has a\n  clear code or docs change and validation path.\n- If the best next action is a broader plan bundle or dispatch lane, say that\n  explicitly instead of silently expanding triage into planning.\n\n## Boundary\n\n`issue-triage` is a read-only selection and recommendation workflow. It uses\n`forge-cli inbox` as the candidate source and `forge-cli issue view` as optional\ncontext enrichment. It does not replace `issue-follow-up`, mutate provider\nstate, or implement the selected issue unless the user explicitly asks for that\nnext step.\n\nShared rules for follow-up comments and closure live in\n`..\u002Fissue-follow-up\u002Freferences\u002Fissue-lifecycle.md`.\n",{"name":5,"description":7},"main","da7119f2ebece510d6955cea72743069f5496c73","tests\u002Fgolden\u002Fclaude\u002Fplugins\u002Fissue\u002Fskills\u002Fissue-triage\u002Fexpected","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit","https:\u002F\u002Fgithub.com\u002Fgraysurf","Building reliable tools for teams of AI coding agents · Rust \u002F TypeScript · @sympoies","2026-08-29 05:27:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add graysurf\u002Fagent-runtime-kit --skill issue-triage",{"tool":36,"command":37},"bunx","bunx skills add graysurf\u002Fagent-runtime-kit --skill issue-triage",{"tool":39,"command":40},"pnpm","pnpm dlx skills add graysurf\u002Fagent-runtime-kit --skill issue-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fclaude\u002Fplugins\u002Fissue\u002Fskills\u002Fissue-triage\u002Fexpected\u002FSKILL.md",true,[],[45,51,56,63,70,77],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M736XWK14DFRERMQ8RT3HS0Z","removable-skill","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fcodex\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":52,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M736XTPQEKAYESDM1REN2KAN","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fclaude\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M736XRMWHMJB4X563G9J6QYY","removable-project-skill","Fixture project-local skill used to prove remove-project-skill dry-run coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-project-skill\u002F.agents\u002Fskills\u002Fremovable-project-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M736XPT65YZMPCBD4K3RHV4P","project-sample-skill","Fixture project-local skill used to prove create-project-skill governance coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fcreate-project-skill\u002F.agents\u002Fskills\u002Fproject-sample-skill\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M736XKZVYWVQA1YB0P459WND","project-local-skill","Fixture project-local skill used by runtime-kit project-local smoke checks.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fprojects\u002Fproject-local-smoke\u002F.agents\u002Fskills\u002Fproject-local-skill\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M736XHA73KZ5G2TKWSED5P1B","topic-radar","Aggregate read-only AI and technology trend signals (Polymarket, Hacker News, GitHub, arXiv, Hugging Face, news search) into source-grounded Markdown or JSON; the lower-level data engine behind `daily-brief`.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Freporting\u002Fskills\u002Ftopic-radar\u002Fexpected\u002FSKILL.md",[],[]]