Stats
Actions
Tags
From audit-fleet
This skill should be used when findings need evidence quality control, confidence grading, and strict mapping to audit-fleet finding keys and severity enum.
How this skill is triggered — by the user, by Claude, or both
Slash command
/audit-fleet:audit-fleet-evidence-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ensure every finding is verifiable, traceable, and decision-ready.
Ensure every finding is verifiable, traceable, and decision-ready.
All audit-fleet outputs must preserve this exact section order:
All Findings entries must include these keys exactly:
Severity enum is strict: critical | warning | info.
Reject any Findings row that misses required keys or uses severity outside critical | warning | info.
npx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin audit-fleetGenerates professional audit findings in Condition-Criteria-Cause-Effect (CCCE) format with severity levels, management letter comments, remediation recommendations, and risk assessments.
Consolidates outputs from all detect skills into a unified scored index with risk heatmap and unknowns backlog. Invoke after running multiple detect audits.
Guides privacy audit findings remediation: prioritizes by severity (critical, high, medium, low), assigns owners, tracks deadlines, verifies fixes, applies closure criteria, and escalates overdue items.