risk-classification
'Inline risk classification for agent tasks using a 4-tier model. Hybrid routing: GREEN/YELLOW use heuristic file-pattern matching, RED/CRITICAL escalate to war-room-checkpoint for full reversibility scoring.'
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-leyline-risk-classificationNight Market Skill — ported from claude-night-market/leyline. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Table of Contents
- Overview
- When to Use
- 4-Tier Risk Model
- Hybrid Routing
- Task Metadata Extension
- Module Reference
- Integration Pattern
- Exit Criteria
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 + test pass |
| RED | Danger | Cross-module, security/data | Migrations, auth, database schema | War-room RS + full test + review |
| CRITICAL | Stop | Irreversible, regulated | Data deletion, production deploy | War-room RS + 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:
{
"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:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-leyline-risk-classification": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
synthesize
>- Merge, deduplicate, rank, and format research findings from multiple channels into a coherent report. Use after research agents return their results
workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure