How do I install the Triage Sweep skill?

Run npx skillmds@latest add rlaope/triage-sweep in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Triage Sweep safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Triage Sweep?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Triage Sweep free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Triage Sweep?

rlaope (@rlaope) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Triage Sweep by rlaope — Agent Skill

Name: Triage Sweep
Rating: 4.5 (4 reviews)
Author: rlaope

Triage Sweep

Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by area.

rlaope f53e2bf 1.5 KB Updated Sep 9, 2026

File contents

Triage sweep

The procedure lives in docs/TRIAGE-SWEEP.md. Read that file and follow it.

It is kept there rather than here because Codex, Hermes handoffs, and generic executor profiles run the same sweep, and AGENTS.md requires that no single executor own a shared surface. This file exists so the procedure is reachable as /triage-sweep; it deliberately holds no rules of its own, so there is nothing here to drift out of sync with the real one.

Start by reading, in this order:

cat docs/TRIAGE-SWEEP.md
cat .github/labels.yml

Two things worth knowing before you open the procedure, because they are what the sweep gets wrong most often:

.github/labels.yml is the entire allowlist. Never apply a label that is not in it, and never create one on the fly.
The default is a dry run. Print the plan and stop for confirmation unless the invocation carried --apply.

Arguments pass through verbatim: a bare number triages one item, sync-labels reconciles the repository against the manifest, --closed widens the sweep, --apply writes.

Frequently asked questions