canonize

Resolve the canonical-memory provider and dispatch the canonize skill.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/iurykrieger/claude-yoke --skill canonize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canonize
Source: https://github.com/iurykrieger/claude-yoke/tree/main/skills/canonize
Command: npx skills add https://github.com/iurykrieger/claude-yoke --skill canonize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provider-agnostic facade for the canonical-memory write hand-off. When /yoke:implement terminates and the working memory under .yoke/ carries the freshest signal the framework will ever have, this skill is the single verb that hands the directory to the configured canonical-memory provider. Resolves the provider via lib/canonical-memory/resolve-provider.sh, dispatches to the provider's pinned canonize skill (currently /yoke:teach while Bedrock is the in-Yoke seed; rewires to /bedrock:canonize in Sprint 2), and appends a single canonize: line to .yoke/runtime/progress.md. Never bundles, summarizes, or pre-processes the working memory; never classifies maturity (provider judgment); never silently swallows the provider's exit code. Use when: "canonize", "yoke canonize", "/yoke:canonize", "save working memory to canonical memory", or whenever /yoke:implement terminates.

Core Features & Use Cases

  • Dispatcher role: resolves provider, dispatches to the provider's canonize skill, and logs a minimal progress entry without altering memory.
  • End-to-end orchestration: handles provider resolution, dispatch, and exit-code propagation while preserving the working-memory state.
  • Use cases: during yoke runtime termination to hand memory to the canonical provider across different provider implementations.

Quick Start

Invoke /yoke:canonize to hand off the current working memory to the configured canonical-memory provider.

Frequently Asked Questions about canonize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off working memory to a canonical-memory provider during yoke runtime?

Canonical memory hand-off occurs when /yoke:implement terminates and the working memory under .yoke/ carries the freshest signal. The skill dispatches this directory to the configured provider without bundling or pre-processing the memory state.

How does provider resolution work for canonical memory dispatch?

Provider resolution uses lib/canonical-memory/resolve-provider.sh to identify the target provider, then dispatches the working memory to the provider's pinned canonize skill while propagating the exit code.

Does the canonize skill modify or summarize the working memory directory?

No, the skill never modifies, bundles, summarizes, or pre-processes the working memory directory. It acts as a provider-agnostic facade, preserving the exact memory state for the configured canonical-memory provider.

When should I invoke the canonize skill for memory hand-off?

Invoke canonize when /yoke:implement terminates or whenever the working memory under .yoke/ must be handed to a canonical provider across different provider implementations and environments.

What limitations apply to the canonical memory hand-off process?

The skill does not classify memory maturity, deferring all judgment to the provider, and never silently swallows the provider's exit code. It strictly preserves the working-memory state without altering the directory during the hand-off.