Skip to main content

u02186-tool-health-monitoring-for-remote-team-collaboration

Build and operate the "Tool Health Monitoring for remote team collaboration" capability for remote team collaboration. Use when this exact capability is required by autonomous or human-guided missions.

Aller à l'installation

Informations de source

Dépôt
zwright8/OpenClaw-Code
Dernière activité de la source
18 juin 2026 à 22:48
Langue détectée de SKILL.md
anglais
Étoiles
0
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
u02186-tool-health-monitoring-for-remote-team-collaboration
description
Build and operate the "Tool Health Monitoring for remote team collaboration" capability for remote team collaboration. Use when this exact capability is required by autonomous or human-guided missions.
# Tool Health Monitoring for remote team collaboration ## Why This Skill Exists Use tool health monitoring in remote team collaboration with emphasis on evidence quality, falsifiability, and calibration. ## When To Use Use this skill when the request explicitly needs "Tool Health Monitoring for remote team collaboration" outcomes in the remote team collaboration domain. ## Step-by-Step Implementation Guide 1. Define measurable outcomes for Tool Health Monitoring for remote team collaboration, including baseline and target metrics for remote team collaboration. 2. Specify structured inputs/outputs for tool health monitoring and validate schema contract edge cases. 3. Implement the core tool health monitoring logic with deterministic scoring and reproducible execution traces. 4. Integrate orchestration policy, routing, approval gates, retries, and rollback for autonomous execution. 5. Run unit, integration, simulation, and regression suites for Tool Health Monitoring for remote team collaboration under maximally truth-seeking conditions. 6. Roll out behind a feature flag, monitor telemetry, and refine thresholds using observed operational outcomes. ## Required Deliverables - Capability contract: input schema, deterministic scoring, output schema, and failure modes. - Runtime profile: monitoring-engine using tool health monitoring to produce tool-health-monitoring-artifact-remote-team-collaboration. - Orchestration integration: remote-team-collaboration:monitoring-engine routing, approval gates, retries, and rollback controls. - Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry. ## Operational Runbook ### Preflight - Validate mission scope, contracts, and required inputs. - Verify feature flag posture, dependencies, and approval prerequisites. ### Execution - Execute tool health monitoring workflow with deterministic scoring and trace capture. - Track posture transitions and preserve reproducible evidence artifacts. ### Recovery - Apply rollback strategy if posture is critical or guardrails fail. - Escalate blocked execution to oversight with incident packet and trace references. ### Handoff - Publish outcome report, scorecard, and telemetry links. - Queue follow-up tasks for unresolved risks, approvals, or optimization work. ## Guardrails - [quality] Require unit and integration validations before promoting Tool Health Monitoring for remote team collaboration. -> `run-validation:unit+integration+simulation+regression-baseline` - [reliability] Trigger rollback on critical posture or repeated failures. -> `rollback:rollback-to-last-stable-baseline` - [cost] Respect bounded resource pressure and execution budget during scaling. -> `budget-guard:resource-pressure-cap`
Voir sur GitHub