Skip to main content

u0605-security-confidence-calibration-engine

Build and operate the "Security Confidence Calibration Engine" capability for Security and Privacy. Trigger when this exact capability is needed in mission execution.

Source facts

Repository
zwright8/OpenClaw-Code
Last source activity
June 18, 2026 at 22:48
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
u0605-security-confidence-calibration-engine
description
Build and operate the "Security Confidence Calibration Engine" capability for Security and Privacy. Trigger when this exact capability is needed in mission execution.
# Security Confidence Calibration Engine ## Why This Skill Exists We need this skill because production autonomy must default to least privilege and strong privacy. This specific skill aligns reported confidence with actual uncertainty. ## When To Use Use this skill when the request explicitly needs "Security Confidence Calibration Engine" outcomes in the Security and Privacy domain. ## Step-by-Step Implementation Guide 1. Define the scope and success metrics for `Security Confidence Calibration Engine`, 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 calibration curves and error bins, and produce calibrated confidence scores with deterministic scoring. 4. Integrate the skill into swarm orchestration: task routing, approval gates, retry strategy, and rollback controls. 5. Add unit, integration, and simulation tests that explicitly cover breach, exfiltration, and over-privileged actions, then run regression baselines. 6. Deploy behind a feature flag, monitor telemetry/alerts for two release cycles, and iterate thresholds based on observed outcomes. ## Required Deliverables - Capability contract: input schema, deterministic scoring, output schema, and failure modes. - Runtime profile: optimization-engine using calibration curves and error bins to produce calibrated confidence scores. - Orchestration integration: security-and-privacy:optimization-engine routing, approval gates, retries, and rollback controls. - Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry. ## Operational Runbook ### Preflight - Confirm the Security Confidence Calibration Engine request scope, source evidence, and measurable success criteria before execution. - Verify feature flag skill_0605_security-confidence-calibration-, approval gates, and rollback owner before autonomous use. ### Execution - Execute calibration curves and error bins with deterministic scoring and reproducible trace capture. - Produce calibrated confidence scores plus scorecard, assumptions, and unresolved-risk notes. ### Recovery - Fail closed when required signals, evidence, or approval gates are missing. - Rollback to the last stable baseline when posture is critical or validation fails. ### Handoff - Publish calibrated confidence scores, validation evidence, and telemetry links to downstream owners. - Queue follow-up tasks for unresolved risks, threshold tuning, or approval review. ## Guardrails - [quality] Require deterministic scoring and validation evidence before promotion. - [reliability] Preserve retries, rollback controls, and failure-mode evidence for every run. - [safety] Route critical posture or missing approval gates to human review before autonomous action.
View on GitHub