agentsclimarketplace

Triage

Skill taipt1504/agent-skills/skills/triage

Classify task scope. Routes to trivial / standard / high-stakes lane. Auto-fires SessionStart with user task description. Output decides which downstream gates are mandatory vs optional.From its SKILL.md

Install
npx -y skills add taipt1504/agent-skills --skill triage

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 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.

SKILL.md

3.8 KB, as published. Nobody here has run it

Triage — Route to Workflow Lane

Classify task. Choose depth, not skip phases — choose lane.

Decision tree

Is task ≤5 lines code AND no behavior change?
├── Yes → Trivial lane
│         (skip Align/Brainstorm/Plan/Spec, lighter Verify, Stage 2 review only)
│
└── No → Touches ANY of:
    ├── System architecture or design pattern? → High-stakes
    ├── DB migration / schema change? → High-stakes
    ├── Auth / secrets / security boundary? → High-stakes
    ├── Public API contract? → High-stakes
    ├── Breaking change to existing behavior? → High-stakes
    ├── New external dependency (library, service)? → High-stakes
    │
    └── None above → Standard lane
        (full reasoning gates, normal execution, two-stage review)

Lane summary

LaneCode changeBehavior changeNew depPublic APIPersistenceSkipped gates
Trivial≤5 linesNoNoNoNoAlign, Brainstorm, Plan, Spec, Review S1
StandardboundedpossibleNoNominorBrainstorm (if obvious solution)
High-stakesanyyespossiblepossibleyesnone

Output template

## Triage decision

**Lane:** [Trivial | Standard | High-stakes]
**Reasoning:** [1-2 sentences]
**Next gate:** [What runs next]
**Skipped gates:** [What's intentionally skipped]
**Override:** State "treat as [lane]" to force.

User override

  • "treat as high-stakes" → upgrade
  • "treat as trivial, just do it" → downgrade (warn first; agent acknowledges)

Edge cases

CaseDefault
Ambiguous task descriptionStandard + surface ambiguity for clarification
Multi-task requestTriage each sub-task; process highest-lane first
Hotfix under time pressureHigh-stakes by default; user can downgrade with explicit ack
Exploratory / prototypeStandard (skip Spec, keep Plan)

Examples

RequestLaneWhy
"Fix typo in error message"Trivial1 line, no behavior change
"Add pagination to user API"StandardFeature, bounded scope
"Migrate from MySQL to TigerBeetle"High-stakesNew tech, data layer
"Refactor PaymentService"StandardBounded refactor
"Update Spring Boot 3.1 → 3.2"High-stakesNew dep version, cluster impact
"Add Javadoc to method"TrivialNo behavior change
"Fix slow query in OrderRepository"StandardBounded perf fix
"Switch Redis → Hazelcast"High-stakesNew dep, ops change
"Rename internal method"TrivialIf not public API
"Add OAuth login"High-stakesSecurity boundary

Target: ≥9/10 on this set.

Integration

State file: .claude/memory/state/current-triage.json

{
  "lane": "standard",
  "task_description": "...",
  "timestamp": "ISO-8601",
  "reasoning": "...",
  "user_override": false
}

session-init.sh auto-invokes triage on fresh task. Downstream gates read TRIAGE_LANE env var or state file.

Related

  • rules/common/lanes.md — lane definitions
  • skills/preflight/SKILL.md — pre-flight artifact format per lane
  • commands/triage.md — manual override

Keep looking

Skills are one crate of 610,220. 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.