Skip to content
Agentmart
Submit a tool

structured-labels

Defines the standard structured label conventions used across all analytical, planning, and debugging agents — REQ, RISK, BS, HYP, EV identifiers with…

Skill by MoltenRuby

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moltenruby-structured-labels

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Defines the standard structured label conventions used across all analytical, planning, and debugging agents — REQ, RISK, BS, HYP, EV identifiers with ordering and formatting rules

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/structured-labels

What's inside

Skill name
structured-labels
Description
Defines the standard structured label conventions used across all analytical, planning, and debugging agents — REQ, RISK, BS, HYP, EV identifiers with ordering and formatting rules
License
MIT
Compatibility
opencode
Instructions
42 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## Structured label conventions

Use these labels consistently across all output. Never use free-form labels in place of these.

### Label types

| Label | Format | Used for |
|---|---|---|
| Requirement | `REQ-{id}` (e.g. `REQ-1`) | A stated or elicited requirement |
| Risk | `RISK-{id}` (e.g. `RISK-1`) | A known concern with assessable likelihood and impact |
| Blind Spot | `BS-{id}` (e.g. `BS-1`) | An area of uncertainty where information is incomplete |
| Hypothesis | `HYP-{id}` (e.g. `HYP-1`) | A candidate explanation under investigation |
| Evidence | `EV-{id}` (e.g. `EV-1`) | A captured, verifiable piece of supporting data |
| Deviation | `DEVIATION-{id}` (e.g. `DEVIATION-1`) | A deviation from a prescribed plan |

### Ordering rule

**Risks and blind spots must always be listed from most severe to least severe.** Never list them in discovery order.

### Risk format

Each `RISK-{id}` entry must include:
- Description
- Likelihood: `High / Medium / Low`
- Impact: `High / Medium / Low`
- Proposed mitigation strategy

### Blind spot format

Each `BS-{id}` entry must include:
- Description of what is unknown
- What additional investigation or information would resolve it

### Acceptance protocol

After presenting risks and blind spots, ask the user:
1. Do you accept each risk? (If not, the mitigation strategy must be incorporated before proceeding.)
2. Do you accept each blind spot? (If not, it must be investigated and resolved before proceeding.)

**Do not proceed until all risks and blind spots are either accepted or resolved.**

From MoltenRuby/MrSmith, MIT.

More from MoltenRuby/MrSmith

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Mar 21, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MoltenRuby

Cite this page

structured-labels skill. Agent Mart. https://agentmart.dev/skills/moltenruby-structured-labels (last updated 2026-10-24)