Assess exposure and impact
Prioritize a vulnerability using actual asset exposure and impact. Use when versions, reachability, prerequisites, privileges, data, exploit maturity, mitigations, detection, business criticality, and urgency matter beyond CVSS.From its SKILL.md
npx -y skills add gaelic-ghost/socket --skill assess-exposure-and-impactAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, as published. Nobody here has run it
Assess Exposure And Impact
Overview
Translate a technical finding into asset-specific risk and action. Treat CVSS as one technical severity input and current exploitation intelligence as another; neither replaces deployed context.
Read references/exposure-impact-model.md for the decision factors.
Workflow
- Confirm finding confidence and exact affected/fixed versions.
- Inventory affected assets.
- Record internet/internal/local reachability, environment, owner, business function, data, users, privileges, and compensating controls.
- Model attacker requirements.
- Record access position, authentication, user interaction, configuration, chaining, reliability, and detection likelihood.
- Check current intelligence.
- Review vendor advisory, fixed release, exploit maturity, CISA KEV/ransomware status, ecosystem advisories, and known active campaigns; date sources.
- Evaluate consequence.
- Assess confidentiality, integrity, availability, privilege, blast radius, persistence, recovery difficulty, safety/legal/privacy obligations, and business interruption.
- Evaluate mitigations.
- Test whether configuration, network controls, feature disablement, isolation, monitoring, or virtual patching actually blocks the validated path.
- Prioritize action.
- Recommend patch, mitigate, isolate, monitor, accept temporarily with owner/expiry, or investigate further; include retest criteria.
Output
Return affected assets, exposure path, impact, current exploitation context, mitigations, priority/rationale, action owner/deadline, and residual uncertainty.
What ships with it: 2 files
1.0 KB alongside SKILL.md
agents/
- openai.yaml247 B
references/
Gives 0 of the 12 instructions most security skills give
Counted across 666 of the 889 authors here whose files we hold, read 2026-09-06
- Use parameterized queries for database accessin 82 of 666, across 79 files
- Hash passwords with BCryptin 55 of 666, across 39 files
- Implement rate limiting for public endpointsin 48 of 666, across 34 files
- Use environment variables for secretsin 35 of 666
- Scan dependencies for vulnerabilitiesin 35 of 666, across 24 files
- Validate and sanitize all user inputin 35 of 666, across 32 files
- Add security headers to all responsesin 34 of 666, across 20 files
- Validate all external input at the system boundaryin 26 of 666, across 25 files
- Use parameterized queries to prevent SQL injectionin 25 of 666, across 13 files
- Store secrets in Vault or environment variablesin 25 of 666, across 10 files
- Run containers as a non-root userin 21 of 666, across 18 files
- Validate all input using Bean Validationin 19 of 666, across 5 files
Said here and by no other author read
- Confirm finding confidence and affected versions
- Inventory affected assets and reachability
- Model attacker requirements and access position
- Review current threat intelligence and exploit maturity
- Evaluate consequence and business impact
- Test effectiveness of existing mitigations
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.