Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From tenable-inspector
Interpret Tenable vulnerability-management findings for scan coverage, credentialed scans, vulnerability age, and scan access visibility.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tenable-inspector:tenable-inspector-expertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when reviewing `tenable-inspector` output.
Use this skill when reviewing tenable-inspector output.
Findings are written to ~/.cache/claude-grc/findings/tenable-inspector/<run_id>.json.
Key mappings:
VPM-02: vulnerability scan coverageVPM-03: credentialed/authenticated scan evidenceVPM-04: vulnerability remediation timelinessTreat inconclusive credentialed-scan signals as a coverage gap that should be verified in Tenable.
npx claudepluginhub vantainc/claude-grc-engineering --plugin tenable-inspectorGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 18, 2026