Skip to content

zwright8/OpenClaw-Code / skills/generated/0098-memory-memory-consolidation-pipeline

u0098-memory-memory-consolidation-pipeline

Verified

Build and operate the "Memory Memory Consolidation Pipeline" capability for Memory and Knowledge Operations. Trigger when this exact capability is needed in mission execution.

Memory Memory Consolidation Pipeline

Why This Skill Exists

We need this skill because agents lose performance when lessons are not retained and reused. This specific skill turns raw logs into durable reusable memory.

When To Use

Use this skill when the request explicitly needs "Memory Memory Consolidation Pipeline" outcomes in the Memory and Knowledge Operations domain.

Step-by-Step Implementation Guide

  1. Define the scope and success metrics for Memory Memory Consolidation Pipeline, including at least three measurable KPIs tied to repeated mistakes and context loss.
  2. Design and version the input/output contract for episodic logs, knowledge nodes, and retrieval metadata, then add schema validation and failure-mode handling.
  3. Implement the core capability using episodic-to-semantic consolidation, and produce consolidated memory snapshots 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 repeated mistakes and context loss, 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: general-capability using episodic-to-semantic consolidation to produce consolidated memory snapshots.
  • Orchestration integration: memory-and-knowledge-operations:general-capability routing, approval gates, retries, and rollback controls.
  • Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.

Operational Runbook

Preflight

  • Confirm the Memory Memory Consolidation Pipeline request scope, source evidence, and measurable success criteria before execution.
  • Verify feature flag skill_0098_memory-memory-consolidation-pipe, approval gates, and rollback owner before autonomous use.

Execution

  • Execute episodic-to-semantic consolidation with deterministic scoring and reproducible trace capture.
  • Produce consolidated memory snapshots 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 consolidated memory snapshots, 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.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall