plugins/leyline/skills/risk-classification/SKILL.md
Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.
npx skillsauth add athola/claude-night-market risk-classificationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Skill(attune:war-room) instead)| 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 |
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.
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).
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.
# In your skill's frontmatter
dependencies: [leyline:risk-classification]
Append [R:TIER] marker to task format:
- [ ] T012 [P] [US1] [R:YELLOW] Create LoginForm component in src/components/LoginForm.tsx
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
tools
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
testing
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
development
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
testing
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.