How do I install the Triage Scout skill?

Run npx skillmds@latest add tonbistudio/triage-scout 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 Scout safe to use?

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

Which AI agents work with Triage Scout?

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 Scout free to use?

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

Who published Triage Scout?

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

Triage Scout by tonbistudio — Agent Skill

Name: Triage Scout
Author: tonbistudio

Triage Scout

Scout skill template for the Hermes Multi-Agent Workflow. Runs on a cron under a source profile, searches for candidate items in your domain, writes a report to the intake vault, and creates one `intake` Kanban task on the triage board. COPY this per source (e.g. triage-scout-x, triage-scout-web) and fill the TODOs.

tonbistudio Updated Sep 17, 2026

File contents

Triage scout

For the adapting agent: this is a TEMPLATE. Make one copy per sources[] entry in triage.yaml (e.g. triage-scout-x, triage-scout-web), give each the matching name, and paste that source's query into "What to look for". Install each copy on the profile named in that source. See docs/04-adapting-to-your-domain.md and docs/05-pipeline-stages.md.

Want a worked example? examples/ai-agent-pain-points/reference-skills/pain-point-scout-x/SKILL.md is a real, filled-in copy of this template from the live system.

When to use

Fired hourly by cron (the schedule in triage.yaml). Also runnable by hand for a smoke test:

<profile> chat --skills <this-skill-name> -q "Run one sweep now, following this skill exactly."

Prerequisite (read once)

This skill runs via cron, not the dispatcher, so HERMES_KANBAN_TASK is unset and kanban tools are NOT auto-enabled. The scout profile MUST list kanban in its toolsets: or kanban_create silently does nothing. (The scaffolder sets this; verify it.)

What to look for

Procedure

Search your assigned surface for candidate items matching the query above.
For each distinct candidate, capture: a one-line claim, source URLs (every claim traceable to a primary source), a verbatim quote where possible, and one line on why it may matter.
Drop low-signal noise — vague hype, single-person rants with no corroboration.
Write the full report to: ${HERMES_PROFILE_DIR}/vault/intake/<UTC-timestamp>-<source-id>.md in the format below.

Create ONE intake Kanban task on the triage board:

kanban_create(
  board: "<board from triage.yaml>",
  title: "intake: <source-id> <UTC-date>",
  assignee: "orchestrator",
  body: "<path to the report file you just wrote>",
)   # no parents → lands `ready`; the orchestrator picks it up

Report format (contract with engine/intake_parser.py)

source: <source-id>
captured_at: <UTC timestamp>

## Candidate: <title>
Claim: <one-line claim>
Sources:
  - url: https://...
    quote: "verbatim"
Why it may matter: <one line>

## Candidate: <title>
...

If you change these fields, update item_schema in triage.yaml AND engine/intake_parser.py to match.

Don't

Don't dedup, score, or route — that's the orchestrator's job. You only detect.
Don't post anywhere except the intake vault + the one intake task.
Don't fabricate sources. No URL → don't include the claim.

---name: triage-scoutdescription: Scout skill template for the Hermes Multi-Agent Workflow. Runs on a cron under a source profile, searches for candidate items in your domain, writes a report to the intake vault, and creates one `intake` Kanban task on the triage board. COPY this per source (e.g. triage-scout-x, triage-scout-web) and fill the TODOs.---# Triage scout> **For the adapting agent:** this is a TEMPLATE. Make one copy per `sources[]`> entry in `triage.yaml` (e.g. `triage-scout-x`, `triage-scout-web`), give each> the matching `name`, and paste that source's `query` into "What to look for".> Install each copy on the profile named in that source. See> `docs/04-adapting-to-your-domain.md` and `docs/05-pipeline-stages.md`.>> **Want a worked example?** `examples/ai-agent-pain-points/reference-skills/pain-point-scout-x/SKILL.md`> is a real, filled-in copy of this template from the live system.## When to useFired hourly by cron (the `schedule` in `triage.yaml`). Also runnable by hand fora smoke test:```<profile> chat --skills <this-skill-name> -q "Run one sweep now, following this skill exactly."```## Prerequisite (read once)This skill runs via **cron, not the dispatcher**, so `HERMES_KANBAN_TASK` isunset and kanban tools are NOT auto-enabled. The scout profile MUST list `kanban`in its `toolsets:` or `kanban_create` silently does nothing. (The scaffolder setsthis; verify it.)## What to look for<your domain search instructions here>## Procedure1. Search your assigned surface for candidate items matching the query above.2. For each distinct candidate, capture: a one-line **claim**, **source URLs** (every claim traceable to a primary source), a verbatim quote where possible, and one line on **why it may matter**.3. Drop low-signal noise — vague hype, single-person rants with no corroboration.4. Write the full report to: `${HERMES_PROFILE_DIR}/vault/intake/<UTC-timestamp>-<source-id>.md` in the format below.5. Create ONE intake Kanban task on the triage board: ``` kanban_create( board: "<board from triage.yaml>", title: "intake: <source-id> <UTC-date>", assignee: "orchestrator", body: "<path to the report file you just wrote>", ) # no parents → lands `ready`; the orchestrator picks it up ```## Report format (contract with engine/intake_parser.py)```source: <source-id>captured_at: <UTC timestamp>## Candidate: <title>Claim: <one-line claim>Sources: - url: https://... quote: "verbatim"Why it may matter: <one line>## Candidate: <title>...```If you change these fields, update `item_schema` in `triage.yaml` AND`engine/intake_parser.py` to match.## Don't- Don't dedup, score, or route — that's the orchestrator's job. You only detect.- Don't post anywhere except the intake vault + the one intake task.- Don't fabricate sources. No URL → don't include the claim.

Frequently asked questions