From wiz-inspector
Use `wiz-inspector` when Wiz CNAPP is the source of cloud posture, vulnerability, toxic-combination, or inventory evidence.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wiz-inspector:wiz-inspector-expertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `wiz-inspector` when Wiz CNAPP is the source of cloud posture, vulnerability, toxic-combination, or inventory evidence.
Use wiz-inspector when Wiz CNAPP is the source of cloud posture, vulnerability, toxic-combination, or inventory evidence.
Inputs:
WIZ_CLIENT_IDWIZ_CLIENT_SECRETWIZ_API_URL, for example https://api.<region>.app.wiz.io/graphqlWIZ_AUTH_URL, defaulting to https://auth.app.wiz.io/oauth/tokenWIZ_PROJECT_ID to constrain collection to a Wiz projectread:projects, read:issues, read:vulnerabilities, read:inventoryRun /wiz-inspector:setup, then /wiz-inspector:collect. Findings are emitted using schemas/finding.schema.json and can feed GRC Engineering gap assessments, OSCAL exports, workpaper generation, and remediation workflows.
The collector handles cursor pagination, project scoping, Wiz severity/status normalization, and partial results. If a GraphQL resource query fails, it emits an inconclusive Finding for that endpoint and continues collecting the remaining resource types.
4plugins reuse this skill
First indexed Jul 18, 2026
Guides 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.
npx claudepluginhub vantainc/claude-grc-engineering --plugin wiz-inspector