Distribute Skills

Distributing skills across repositories involves pulling the latest skill definitions from a Supabase rule ledger into a local cache, then copying real directories into each repository's git-tracked skills/ folder for automatic discovery.

Skill synchronization explicitly uses real copied directories instead of symlinks to ensure all propagated skills are properly git-tracked and maintain their structure within every repository's skills/ folder.

When new repositories are added to the skill map, running the distribution workflow pulls the latest skills from Supabase and copies the real directories into the new repositories' skills/ folders to enable immediate skill discovery.

Yes, Supabase serves as the centralized source of truth for skill distribution. The workflow pulls from the rule_ledger.skills table in Supabase to synchronize and propagate all skill directories across mapped repositories.

To verify the health of synchronized skills, the distribution process performs automatic health checks on every repository to ensure each one contains valid, real skill directories after the synchronization workflow completes.

A repository requires a refreshed skills directory when new skills are added or existing ones are updated in the Supabase source. The synchronization workflow pulls these changes and copies the updated directories to maintain valid skill discovery.