risk-classification
/risk-classification
Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.
- Author
- athola ↗
- Repository
- claude-night-market ↗
- Licence
- MIT
- Last repository change
- 01.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.
Original author description
Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.
How it works
- Overview
- When To Use
- When NOT To Use
- 4-Tier Risk Model
- Hybrid Routing
- Task Metadata Extension
- Readiness Levels
- Graduated Autonomy
- Module Reference
- Integration Pattern
SKILL.md preview
---
name: risk-classification
description: Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.
alwaysApply: false
category: infrastructure
tags:
- risk
- classification
- safety
- verification
- gates
dependencies:
- error-patterns
provides:
infrastructure:
- risk-tier-classification
- verification-gates
- heuristic-classifier
patterns:
- risk-aware-coordination
- tier-based-verification
usage_patterns:
- task-risk-assessment
- verification-gate-routing
- parallel-safety-validation
complexity: intermediate
model_hint: standard
estimated_tokens: 500
progressive_loading: true
modules:
- modules/tier-definitions.md
- modules/heuristic-classifier.md
- modules/verification-gates.md
- modules/readiness-levels.md
- modules/automation-tiers.md
role: library
---
# Risk Classification
## Overview
Provides inline risk classification for agent tasks using a 4-tier model (GREEN/YELLOW/RED/CRITICAL). Uses fast heuristic file-pattern matching for low-risk tiers and delegates to `Skill(attune:war-room-checkpoint)` for high-risk tiers requiring full reversibility scoring.
## When To Use
- Assessing risk of tasks before agent assignment
- Determining verification requirements for task completion
- Deciding parallel execution safety between tasks
- Adding risk markers to task checklists
## When NOT To Use
- Single-file trivial changes (assume GREEN)
- Strategic architecture decisions (use full `Skill(attune:war-room)` instead)
- Non-code tasks (documentation-only, configuration comments)
## 4-Tier Risk Model
| Tier | Color | Scope | Example | Verification |
|------|-------|-------|---------|-------------|
| **GREEN** | Safe | Single file, trivial revert | Test files, docs, utils | None required |
| **YELLOW** | Caution | Module-level, user-visible | Components, routes, views | Conflict check and test pass |
| **RED** | Danger | Cross-module, security/data | Migrations, auth, database schema | War-room RS, full test, and review |
| **CRITICAL** | Stop | Irreversible, regulated | Data deletion, production deploy | War-room RS and human approval |
## Hybrid Routing
```
Task received
|
v
Heuristic classifier (file patterns)
|
├── GREEN/YELLOW → Apply tier, continue
|
└── RED/CRITICAL → Invoke Skill(attune:war-room-checkpoint)
for reversibility scoring (RS)
|
└── RS confirms or adjusts tier
```
**Why hybrid**: GREEN/YELLOW classification is fast and deterministic (file pattern matching). RED/CRITICAL tasks warrant the overhead of full reversibility analysis because the cost of getting them wrong is high.
## Task Metadata Extension
Add risk tier to task metadata for downstream consumption:
```json
{
"id": "5",
"subject": "Add user authentication",
"metadata": {
"risk_tier": "YELLOW",
"risk_reason": "Modifies src/components/LoginForm.tsx (user-visible component)",
"classified_at": "2026-02-07T22:00:00Z"
}
}
```
Tasks without `risk_tier` metadata default to **GREEN** (backward compatible).
## Readiness Levels
The 4-tier Readiness Levels system provides clear risk
classification with required controls per tier:
| Level | Name | When | Required Controls |
|-------|------|------|-------------------|
| 0 | Routine | Low blast radius, easy rollback | Basic validation, rollback step |
| 1 | Watch | User-visible changes | Review, negative test, rollback note |
| 2 | Elevated | Security/compliance/data | Adversarial review, risk checklist |
| 3 | Critical | Irreversible, regulated | Human confirmation, two-step verification |
See `modules/readiness-levels.md` for full level definitions,
selection decision tree, and integration guidance.
## Graduated Autonomy
Risk classification sets how carefully a change is verified.
Automation tiers set how autonomously the agent acts and when it
must hand control back. Each risk tier carries a default automation
tier (GREEN to A3 autonomous, CRITICAL to A0 manual), and a
pre-licensed downgrade trigger drops the agent one tier on repeated
failure, confidence loss, a stakes spike, or repo-state mismatch
rather than re-prompting at the same level. See
`modules/automation-tiers.md` for the tier table and the downgrade
trigger, and `imbue:assisted-mastery` for the explain/produce mode
selection that reads from it.
## Module Reference
- **tier-definitions.md**: Detailed tier criteria, boundaries, and override mechanism
- **heuristic-classifier.md**: File-pattern rules for automated classification
- **verification-gates.md**: Per-tier verification requirements and parallel safety matrix
- **readiness-levels.md**: 4-tier risk system with required controls per level
- **automation-tiers.md**: Per-tier autonomy defaults and the downgrade trigger
## Integration Pattern
```yaml
# In your skill's frontmatter
dependencies: [leyline:risk-classification]
```
### For Task Generators
Append `[R:TIER]` marker to task format:
```markdown
- [ ] T012 [P] [US1] [R:YELLOW] Create LoginForm component in src/components/LoginForm.tsx
```
### For Orchestrators
Check risk tier before task assignment:
```
if task.risk_tier in ["RED", "CRITICAL"]:
invoke Skill(attune:war-room-checkpoint) for RS scoring
if CRITICAL: require human approval before proceeding
```
## Exit Criteria
- Every task has a risk tier assigned (explicit or default GREEN)
- RED/CRITICAL tasks have war-room-checkpoint RS scores
- Verification gates passed for the assigned tier
- No parallel execution of prohibited tier combinations
- Each task carries an automation tier; downgrades are recorded
with a reason when a trigger fires
Files in this package (6)
- SKILL.md 6 KB
- modules/automation-tiers.md 3 KB
- modules/heuristic-classifier.md 4 KB
- modules/readiness-levels.md 8 KB
- modules/tier-definitions.md 3 KB
- modules/verification-gates.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · athola/claude-night-market | 100 | MIT |
| SimonFoote-greensparx/CopilotForge | 100 | CC-BY-4.0 |
Database snapshot: 13.11.2026 · package version b9e183d5aa9a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100token-budget-gate
Estimates token cost before a multi-step task and outputs a 4-tier Green/Yellow/Orange/Red gate verdict. Records actual vs. estimated after completion when a mechanical usage source exists. Triggers on "token budget", "how much will this cost", "will this be expensive",… - 85symptom_scorer
Use this skill during pre-diagnosis triage (clinic_agent) to assign a structured severity score (0–100) and triage colour (RED/YELLOW/GREEN) to the user's reported symptoms. Invoke automatically when the user has described at least one symptom. The score drives urgency… - 100nda-triage
Rapid NDA screening with GREEN/YELLOW/RED classification. 10-point checklist for incoming NDAs. Use when triaging NDAs, screening non-disclosure agreements, or routing NDAs for approval. - 100task-classification
This skill should be used when classifying tasks, routing to agents, determining complexity, or handling task routing, agent selection, verification requirements, and multi-component changes. - 100quick-recap
Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions. - 100pa-workflow-transactional-nda-triage-red-yellow-green
Use when a transactional lawyer or in-house team needs to rapidly triage an incoming NDA and assign a red / yellow / green approval status before investing full review time. Produces a structured triage report with a three-color risk rating, flagged issues by severity, and a…