Assess exposure and impact
The Source for macOS Agent Workflows
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
- 6 stars6 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.
What its author says it does
Copied from the file, not written here
Prioritize a validated or plausible vulnerability using actual asset exposure and impact. Use when affected versions, deployment reachability, attacker prerequisites, privileges, sensitive data, exploit maturity, CISA KEV status, vendor guidance, mitigations, detection, business criticality, CVSS, and remediation urgency must be combined without relying on a severity score alone.
SKILL.md
2.0 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.