skill-registry-sync

Rebuild the local registry of skills, rules, agents, and instructions.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill skill-registry-sync-victorp1leon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-registry-sync
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/skill-registry-sync
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill skill-registry-sync-victorp1leon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a deterministic local registry of project operational assets (skills, rules, agents, and instructions) to prevent cross-session drift. Use when files are added, removed, or renamed under .codex/skills, .codex/rules, .github/agents, or .github/instructions, and before closing a collaboration session that changed these artifacts.

Core Features & Use Cases

  • Scans for all SKILL.md files to collect skill metadata and paths for rules, agents, and instructions.
  • Rebuilds a centralized registry file to ensure consistency across sessions and collaborators.
  • Performs drift checks to guarantee every discovered file is listed exactly once and all paths exist.

Quick Start

Run the registry sync to scan skills, rules, agents, and instructions and rebuild .codex/skill-registry.md.

Frequently Asked Questions about skill-registry-sync

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

FAQPage Schema
How do I prevent cross-session drift in .codex/skills and .github/agents?

To prevent cross-session drift, run a registry sync that scans SKILL.md frontmatter and asset paths to rebuild .codex/skill-registry.md. This ensures every collaborator references the exact same operational assets.

What is the best way to maintain a deterministic local registry of project assets?

The best way to maintain a deterministic local registry is to scan .codex/skills, .codex/rules, and .github/agents directories, extract metadata from SKILL.md frontmatter, and rebuild a centralized registry file.

How do I synchronize a local registry of project operational assets before ending a collaboration session?

You synchronize a local registry by scanning for added, removed, or renamed files under .codex and .github directories, then rebuilding .codex/skill-registry.md to reflect the current state before the session ends.

Does registry sync perform drift checks to guarantee every discovered file is listed exactly once?

Yes, registry sync performs drift checks to guarantee every discovered file is listed exactly once in .codex/skill-registry.md and validates that all listed paths actually exist in the repository.

When do I need to rebuild .codex/skill-registry.md for my project assets?

You need to rebuild .codex/skill-registry.md whenever files are added, removed, or renamed under .codex/skills, .codex/rules, .github/agents, or .github/instructions, and before closing collaboration sessions.

Can I use this registry sync tool to collect paths for rules, agents, and instructions?

Yes, you can use registry sync to collect paths for rules, agents, and instructions by scanning the .codex and .github directories, extracting metadata from SKILL.md files, and centralizing them into a single registry.