risk-assessor
Skill8 starsChanged 10 months agoMITView on GitHub
Perform comprehensive risk assessments on OSCAL systems including threat modeling, vulnerability analysis, risk scoring, and POA&M generation. Use this skill to evaluate security posture and prioritize remediation efforts.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Rifteo/skillstheir own version, first seen Jun 17, 2026
- GustavoGutierrez/engineering-skillstheir own version, first seen Jun 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Rifteo/skills★ 37same name
- GustavoGutierrez/engineering-skills★ 0same 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 repository15 other files it gives its agents.
- advanced-oscal-validatorSkill
- compliance-report-generatorSkill
- component-definition-builderSkill
- control-implementation-generatorSkill
- control-mapperSkill
- controls-extractorSkill
- evidence-collectorSkill
- oscal-catalog-providerSkill
- oscal-control-mapperSkill
- oscal-parserSkill
- oscal-ssp-validatorSkill
- oscal-text-converterSkill
- oscal-validatorSkill
- oscal-visualizerSkill
- workflow-orchestratorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when you need to:
- Distinctive: line 234
When asked "Assess the security risks in this SSP":
≈ “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 Assessor Skill
Perform comprehensive risk assessments based on OSCAL data, including threat identification, vulnerability analysis, risk scoring, and remediation recommendations.
When to Use This Skill
Use this skill when you need to:
- Assess overall security risk posture
- Identify and score individual risks
- Generate risk-based POA&M items
- Prioritize remediation efforts
- Perform threat modeling
- Analyze vulnerability impact
⛔ Authoritative Data Requirement
Risk assessment requires user-provided documents — not training knowledge.
What You MUST Have
| Data Type | Source | Why Required |
| Control baseline | User's profile/catalog | Defines what controls are required |
| SSP or control inventory | User-provided | Shows what's implemented |
| Vulnerability data | User's scan results | Actual findings, not assumed |
| Asset information | User-provided | System boundaries and data types |
What You Can Provide (Methodology)
- Risk calculation formulas (Likelihood × Impact)
- Scoring frameworks (the process)
- Report templates and formats
- General threat categories (STRIDE, etc.)
- Prioritization methodologies
What You CANNOT Provide
- Specific control requirements (must come from catalog)
- Baseline comparisons without the baseline document
- Gap analysis without both baseline AND SSP
- Vulnerability details without scan data
If Missing Required Data
I cannot assess risks without:
• Your SSP or control implementation inventory
• The baseline profile your system must meet (e.g., FedRAMP Moderate)
• [For gap analysis] Both documents to compare
Please provide these documents. I will not guess at control
requirements or make assumptions about your implementation status.Risk Levels
| Level | Score Range | Description | Response Time |
| Very Low | 0-10 | Minimal risk | Monitor |
| Low | 11-30 | Minor risk | 90 days |
| Moderate | 31-60 | Significant risk | 60 days |
| High | 61-80 | Serious risk | 30 days |
| Very High | 81-100 | Critical risk | Immediate |
Risk Calculation
Risk = Likelihood × Impact
Likelihood Factors
- Threat source capability
- Attack complexity
- Existing controls
- Historical incidents
- Exposure level
Impact Factors
- Confidentiality impact
- Integrity impact
- Availability impact
- Financial impact
- Regulatory impact
Threat Sources
| Source | Category | Examples |
| Adversarial | External attackers | Nation states, criminals, hacktivists |
| Accidental | Human error | Misconfigurations, mistakes |
| Structural | System failures | Hardware, software, dependencies |
| Environmental | External events | Natural disasters, power loss |
Risk Assessment Process
Step 1: Inventory Assets
Identify system components and data:
- System boundaries
- Data types and sensitivity
- Critical functions
- Dependencies
Step 2: Identify Threats
For each asset, identify potential threats:
- Who might attack?
- What methods would they use?
- What's their motivation?
Step 3: Identify Vulnerabilities
Analyze weaknesses:
- Missing or weak controls
- Configuration issues
- Known CVEs
- Process gaps
Step 4: Assess Current Controls
Review implemented controls:
- Are controls in place?
- Are they operating effectively?
- What gaps exist?
Step 5: Calculate Risk Scores
For each threat-vulnerability pair:
- Estimate likelihood (1-10)
- Estimate impact (1-10)
- Calculate: Risk = Likelihood × Impact
- Determine risk level
Step 6: Prioritize Risks
Rank risks by:
- Risk score (highest first)
- Ease of exploitation
- Asset criticality
- Regulatory requirements
Step 7: Generate Recommendations
For each risk:
- Identify mitigation options
- Estimate effort and cost
- Recommend actions
- Set target dates
Control Gap Analysis
Baseline Comparison
Compare implemented controls against baseline:
- Required controls (from profile)
- Implemented controls (from SSP)
- Gap = Required - Implemented
Effectiveness Assessment
For implemented controls:
- Fully effective
- Partially effective
- Not effective
- Not assessed
Risk Report Format
RISK ASSESSMENT REPORT
======================
System: [System Name]
Assessment Date: [Date]
Assessor: [Name/AI]
EXECUTIVE SUMMARY
-----------------
Overall Risk Level: [LEVEL]
Critical Risks: X
High Risks: Y
Moderate Risks: Z
TOP RISKS
---------
1. [RISK-001] Unauthorized Access via Weak Authentication
Likelihood: High (8/10)
Impact: High (9/10)
Risk Score: 72 (HIGH)
Affected Controls: IA-2, IA-5
Recommendation: Implement MFA within 30 days
2. [RISK-002] Data Exposure from Misconfigured Storage
Likelihood: Moderate (6/10)
Impact: Very High (10/10)
Risk Score: 60 (MODERATE)
Affected Controls: SC-28, AC-3
Recommendation: Enable encryption, restrict access
CONTROL GAPS
------------
Missing Controls: 5
- CM-6: Configuration settings not documented
- SI-4: No automated monitoring
...
POA&M ITEMS
-----------
1. Implement multi-factor authentication
Milestone: Complete by [date]
Resources: IAM team, 40 hours
2. Configure storage encryption
Milestone: Complete by [date]
Resources: Cloud team, 20 hoursPOAM Generation
For each identified risk, generate POA&M item:
poam_item:
id: POAM-2024-001
title: Implement Multi-Factor Authentication
description: Address IA-2 weakness in user authentication
risk_level: HIGH
weakness: Lack of MFA exposes accounts to credential theft
remediation: Deploy MFA for all privileged accounts
milestone: 2024-03-01
resources:
- IAM Administrator
- 40 hours effort
dependencies:
- Identity provider upgrade
status: plannedExample Usage
When asked "Assess the security risks in this SSP":
- Parse the SSP document
- Extract system characteristics
- List implemented controls
- Identify control gaps vs baseline
- For each gap, assess risk
- Calculate risk scores
- Rank by severity
- Generate remediation recommendations
- Produce POA&M items for high risks
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.

