risk-score
Skill2 starsChanged 8 months agoMITView on GitHub
Calculate and display the composite SQWR Risk Score — weighted average across 8 audit domains producing a single 0-100 health indicator
2 other projects use a version of this.
Adopted by
Most recently taken up by
- stevepolitodesign/skillstheir own version, first seen Nov 8, 2026
- thoughtbot/rails-consultanttheir own version, first seen Nov 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- thoughtbot/rails-consultant★ 29same name
- stevepolitodesign/skills★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- contract-lookupSkill
- monthly-reviewSkill
- new-featureSkill
- pre-deploymentSkill
- project-setupSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
If "full" → run full recalculation
- Very specific: line 43
If "quick" or empty → check .sqwr-last-state.sh for cached scores
- Very specific: line 49
Read .sqwr-last-state.sh. If scores exist and SQWR_LAST_AUDIT_DATE is today or yesterday, use them.
- Very specific: line 56
Run agents/AGENT-RISK-SCORE.md with argument "full".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/risk-score — Composite Risk Score
Usage: /risk-score [mode]
Calculates the composite SQWR Risk Score using the weighted formula across all 8 audit domains.
Modes:
quick— Uses cached scores from.sqwr-last-state.sh(default if < 24h old)full— Reruns all 8 audit agents for fresh scores
Weighted Formula
Risk Score = (Security × 0.22) + (Performance × 0.18) + (Code Quality × 0.18)
+ (Observability × 0.12) + (Accessibility × 0.12) + (Design × 0.08)
+ (AI Governance × 0.05) + (Deployment × 0.05)Step 1 — Determine Mode
Parse $ARGUMENTS:
- If "full" → run full recalculation
- If "quick" or empty → check
.sqwr-last-state.shfor cached scores
Step 2a — Quick Mode (cached scores)
Read .sqwr-last-state.sh. If scores exist and SQWR_LAST_AUDIT_DATE is today or yesterday, use them.
Otherwise, warn user and switch to full mode.
Step 2b — Full Mode (rerun audits)
Run agents/AGENT-RISK-SCORE.md with argument "full".
This agent will orchestrate all 8 domain audits and compute the composite score.
Step 3 — Display Results
Apply the weighted formula and display the risk score report:
╔══════════════════════════════════════╗
║ SQWR RISK SCORE ║
╚══════════════════════════════════════╝
[Domain scores table]
COMPOSITE RISK SCORE: [X]/100 — [Level]Scoring levels:
- 85-100: Excellent — Ready for production
- 70-84: Good — Minor improvements recommended
- 50-69: Warning — Address before next release
- 0-49: Critical — BLOCKING — fix before any deployment
Observable truth: Risk Score displayed with domain breakdown and actionable recommendations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.