agentsclimarketplace

Triage

Skill stevennitesh/programming-agent-skills/skills/custom/triage

Practical workflow skills for coding agents: scope, debugging, cleanup, subagents, GitHub tracking, and verification.

Install
npx -y skills add stevennitesh/programming-agent-skills --skill triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Triage raw tracker issues and configured external PR requests through maintainer-approved states and Codex-ready handoffs.

SKILL.md

2.6 KB, 564 tokens by cl100k_base, as published. Nobody here has run it

Triage

Move raw tracker requests to a maintainer-approved state and handoff. Triage owns classification, verification, shaping, approved state transitions, briefs, and rejected-enhancement memory. Tracker docs own transport, label mappings, the Ready-for-agent contract, and Mutation read-back. $implement and $parallel-implement own code changes and implemented closeout.

Spine

  1. Load. Read docs/agents/issue-tracker.md and docs/agents/triage-labels.md before tracker access. If either is absent or incompatible with triage, recommend $repo-bootstrap and stop. Follow docs/agents/domain.md for codebase context and read docs/agents/engineering-contract.md before reproduction, checkout, or executable validation. Triage PRs only when the tracker enables them. A named PR bypasses only external-author discovery; a PR is an issue with attached code.

  2. Choose. Read one branch completely:

    Read AGENT-BRIEF.md only when preparing a ready-for-agent or ready-for-human brief. Read OUT-OF-SCOPE.md only when screening, rejecting, or reconsidering an enhancement.

  3. Run. Follow only the selected branch; its helper owns branch-specific discovery, sequence, and completion criterion. Treat valid $to-tickets output as ready; re-enter triage only for an explicit state or brief correction.

    For any mutation branch, keep exactly one mapped category role and one mapped state role; surface missing or conflicting roles before mutation. Mutate only an explicitly approved packet; any packet change requires fresh approval. A ready-for-agent outcome satisfies the tracker's Ready-for-agent contract and adds verification evidence.

    Prefix every posted issue or comment with:

    > *This was generated by AI during triage.*

  4. Prove. Complete at the selected branch's criterion. An Attention Scan ends after its read-only criterion with tracker state unchanged. A mutation branch ends only after the approved packet is applied, read back, and returned as a triage packet confirming role invariants, disclaimer, required brief or rejected-enhancement record, shaping domain deltas, partial failures, skipped checks, and blockers.

What ships with it: 7 files

11.4 KB alongside SKILL.md

agents/

Gives 0 of the 12 instructions most debug triage skills give in 564 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • read tracker and triage label docs before tracker access
  • recommend repo bootstrap and stop if required docs are absent
  • follow domain and engineering contract docs before validation
  • read exactly one triage branch completely
  • follow only the selected branch
  • surface missing or conflicting roles before mutation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.