U0614 Security Tool Health Monitor

Security Tool Health Monitor

Why This Skill Exists

We need this skill because production autonomy must default to least privilege and strong privacy. This specific skill detects tool flakiness before it impacts mission outcomes.

When To Use

Use this skill when the request explicitly needs "Security Tool Health Monitor" outcomes in the Security and Privacy domain.

Step-by-Step Implementation Guide

1. Define the scope and success metrics for Security Tool Health Monitor, including at least three measurable KPIs tied to breach, exfiltration, and over-privileged actions.
2. Design and version the input/output contract for permissions, sensitive data flows, and threat events, then add schema validation and failure-mode handling.
3. Implement the core capability using telemetry aggregation and SLO checks, and produce tool reliability scores with deterministic scoring.