Skip to main content

u02139-tool-health-monitoring-for-scientific-publishing-pipelines

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

Ir a la instalación

Datos de origen

Repositorio
zwright8/OpenClaw-Code
Última actividad en el origen
18 de junio de 2026 a las 22:48
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
u02139-tool-health-monitoring-for-scientific-publishing-pipelines
description
Build and operate the "Tool Health Monitoring for scientific publishing pipelines" capability for scientific publishing pipelines. Use when this exact capability is required by autonomous or human-guided missions.
# Tool Health Monitoring for scientific publishing pipelines ## Why This Skill Exists Use tool health monitoring in scientific publishing pipelines with emphasis on throughput, reliability, leverage, and execution speed. ## When To Use Use this skill when the request explicitly needs "Tool Health Monitoring for scientific publishing pipelines" outcomes in the scientific publishing pipelines domain. ## Step-by-Step Implementation Guide 1. Define measurable outcomes for Tool Health Monitoring for scientific publishing pipelines, including baseline and target metrics for scientific publishing pipelines. 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 scientific publishing pipelines under hyper-productive autonomy 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-scientific-publishing-pipelines. - Orchestration integration: scientific-publishing-pipelines: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 scientific publishing pipelines. -> `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`
Ver en GitHub