L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Données et recherche · SKILL.md

openclaw-0150-policy-scoped-data-mediation

openclaw-0150-policy-scoped-data-mediation

Tooling Privacy Preserving Data Broker. Use when work requires policy-scoped data mediation for Tool Reliability and Execution Quality with guardrails, traceable execution, and measurable outcomes.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: openclaw-0150-policy-scoped-data-mediation description: Tooling Privacy Preserving Data Broker. Use when work requires policy-scoped data mediation for Tool Reliability and Execution Quality with guardrails, traceable execution, and measurable outcomes.

Tooling Privacy Preserving Data Broker

Mission

We need this skill because automation collapses when tools are flaky and failure modes are opaque. This specific skill enables collaboration while minimizing raw data exposure.

Activation Cues

  • Task requires policy-scoped data mediation in Tool Reliability and Execution Quality.
  • Task needs explicit risk controls, approval gates, and traceable outcomes.
  • Task output must include artifact handoff for humans and agents.

Execution Plan

  1. Define the scope and success metrics for Tooling Privacy Preserving Data Broker, 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 policy-scoped data mediation, and produce privacy-scoped exchanges 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.

Runbook

Preflight:

  • None specified.

Execution:

  • None specified.

Recovery:

  • None specified.

Handoff:

  • None specified.

Guardrails

  • [quality] Require validations before promoting outputs.

Success Metrics

  • Primary metric: silent failures
  • Secondary metrics: cascading retries, decision drift
  • Review cadence: weekly

Output Contract

  • Return a concise execution summary with key decisions.
  • Return risk and mitigation notes with unresolved blockers.
  • Return artifact target: privacy-scoped exchanges.
  • Return recommended follow-up tasks for next wave execution.
Skills enregistrées