bootstrap

Bootstrap host projects to Yoke v2.0.0 by configuring canonical_memory.provider in .yoke/config.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initial setup for a host project that wants to use Yoke. At v2.0.0, /yoke:bootstrap is the single entry point through which a host project's .yoke/config.yaml :: canonical_memory.provider lands. Two flows are supported: Flow A migrates from Yoke v1.x by detecting legacy configuration or memories.json and migrating to the v2.0.0 schema; Flow B performs a fresh bootstrap by loading providers.yaml, selecting a provider (interactive or via --provider), and writing the v2.0.0 config. It also creates .yoke/runtime/ and .yoke/.gitignore and guides the user to the next step.

Core Features & Use Cases

  • Migrate existing v1.x setups or bootstrap a new Yoke v2.0.0 environment by configuring canonical_memory.provider in .yoke/config.yaml.
  • Support both interactive provider selection via providers.yaml and non-interactive mode with --provider, plus the ability to auto-select when only one provider exists.
  • Create required .yoke runtime artifacts (.yoke/runtime/ and .yoke/.gitignore) and guide the user to next steps, including /yoke:discover and CLAUDE.md handling.

Quick Start

Run /yoke:bootstrap in the host project root to bootstrap Yoke v2.0.0 and configure the initial .yoke/config.yaml.

Frequently Asked Questions about bootstrap

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

FAQPage Schema
How do I migrate my existing Yoke v1.x configuration to v2.0.0?

Yoke bootstrap is the single entry point for initial host project setup, configuring the canonical_memory.provider in .yoke/config.yaml. It handles both fresh project initialization and migration from legacy v1.x memories.json files.

How do I set up a fresh Yoke v2.0.0 environment for a new project?

To set up Yoke v2.0.0, run the bootstrap command in your project root. It loads providers.yaml, supports interactive provider selection or non-interactive mode with --provider, writes .yoke/config.yaml, and creates runtime scaffolds like .yoke/runtime/ and .yoke/.gitignore.

Can I configure Yoke provider selection non-interactively in an automated pipeline?

Yes, Yoke bootstrap supports non-interactive provider selection via the --provider flag, allowing automated pipeline integration. It also auto-selects when only one provider exists in providers.yaml, streamlining headless configuration.

What files and directories are created during Yoke project initialization?

Yoke bootstrap creates the .yoke/config.yaml file defining the canonical_memory.provider, the .yoke/runtime/ directory for operational scaffolding, and a .yoke/.gitignore file to exclude runtime artifacts from version control.

Do I need a providers.yaml file to bootstrap Yoke?

Yes, a providers.yaml file is required for fresh Yoke bootstrap to define available providers for selection. For v1.x migrations, the process detects legacy configuration or memories.json instead, loading existing settings into the v2.0.0 schema.

What should I do after completing the Yoke bootstrap process?

After Yoke bootstrap configures .yoke/config.yaml and creates runtime scaffolds, it directs you to the next steps including running /yoke:discover and handling CLAUDE.md configuration to complete the host project integration.