sync-skills

Sync enabled skills from the Supabase rule ledger to local skills directories.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill sync-skills-bedabeda-growth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-skills
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/sync-skills
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill sync-skills-bedabeda-growth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates keeping local agent skill directories in sync with the canonical Supabase rule ledger, ensuring skills are available and up-to-date across environments.

Core Features & Use Cases

  • Syncs enabled skills from the Supabase rule_ledger.skills table to local skills/ directories, ensuring agents have access to the latest capabilities.
  • Validates the availability of pulled skills across multiple repositories (e.g., scceo-1, kai-agent, freely, rocket, ~/.agents) and automatically updates local copies when changes occur.
  • Use cases include onboarding new agents, refreshing stale skills, and guaranteeing consistent skill availability across distributed projects.

Quick Start

Run the local sync script to pull all enabled skills from the Supabase rule ledger into your repository's skills directory.

Frequently Asked Questions about sync-skills

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

FAQPage Schema
How do I sync local agent skills from a Supabase registry across multiple repositories?

Sync local agent skills by running the sync_skills.py script, which pulls enabled skills from the Supabase rule_ledger.skills table and writes them directly to the local skills/ directories across your repositories. This ensures all development environments have available and up-to-date capabilities.

What is the best way to keep local skills directories updated across distributed development environments?

Keeping local skills directories updated requires using a centralized rule ledger as the single source of truth. This skill validates pulled skills across multiple repositories and automatically updates local copies when changes occur, guaranteeing consistent skill availability for distributed projects.

Can I validate skill availability across multiple repositories like scceo-1 and kai-agent?

Validating skill availability across multiple repositories like scceo-1, kai-agent, freely, and rocket is supported. The sync process checks these local directories against the Supabase rule ledger and automatically pulls missing or out-of-date skills to ensure consistency.

Does this skill synchronization approach rely on a specific database table format?

This skill synchronization relies specifically on the rule_ledger.skills table in Supabase as the single source of truth. It queries this database table to determine which skills are enabled and then writes the validated copies to local agent repositories.

Why are my local agent skills out of date when pulling from the global registry?

Local agent skills become out of date when the global Supabase rule ledger is updated but local repositories are not synced. Running the sync_skills.py script resolves this by checking the rule ledger and overwriting stale local copies with the latest versions.

When do I need to sync skills from a rule ledger to local repositories?

You need to sync skills from a rule ledger when onboarding new agents, refreshing stale skills, or ensuring consistent skill availability across distributed projects. It handles missing or out-of-date skills by pulling directly from the global registry.