Skip to main content

u0145-tooling-uncertainty-communicator

Build and operate the "Tooling Uncertainty Communicator" capability for Tool Reliability and Execution Quality. 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
u0145-tooling-uncertainty-communicator
description
Build and operate the "Tooling Uncertainty Communicator" capability for Tool Reliability and Execution Quality. Trigger when this exact capability is needed in mission execution.
# Tooling Uncertainty Communicator ## Why This Skill Exists We need this skill because automation collapses when tools are flaky and failure modes are opaque. This specific skill prevents overstatement by explicitly framing uncertainty. ## When To Use Use this skill when the request explicitly needs "Tooling Uncertainty Communicator" outcomes in the Tool Reliability and Execution Quality domain. ## Step-by-Step Implementation Guide 1. Define the scope and success metrics for `Tooling Uncertainty Communicator`, including at least three measurable KPIs tied to silent failures and cascading retries. 2. Design and version the input/output contract for tool runs, error signatures, and retry outcomes, then add schema validation and failure-mode handling. 3. Implement the core capability using confidence-bound communication templates, and produce uncertainty briefs 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 silent failures and cascading retries, 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: communication-engine using confidence-bound communication templates to produce uncertainty briefs. - Orchestration integration: tool-reliability-and-execution-quality:communication-engine routing, approval gates, retries, and rollback controls. - Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry. ## Operational Runbook ### Preflight - Confirm the Tooling Uncertainty Communicator request scope, source evidence, and measurable success criteria before execution. - Verify feature flag skill_0145_tooling-uncertainty-communicator, approval gates, and rollback owner before autonomous use. ### Execution - Execute confidence-bound communication templates with deterministic scoring and reproducible trace capture. - Produce uncertainty briefs 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 uncertainty briefs, 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