Agent skill
skills-broadcast
Sync skills across all IDEs (Pi, Codex, Claude Code, Antigravity) using the canonical agent-skills repo. Use "sync skills", "broadcast skills", or "pull skills".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/skills-broadcast
Metadata
Additional technical details for this skill
- short description
- Sync skills across all IDEs via agent-skills repo
SKILL.md
Skills Broadcast Skill
Synchronize skills across all IDEs and projects using a central canonical repository.
Architecture
┌─────────────────────────────────────────────────────────────────────┐
│ CANONICAL REPO (Source of Truth) │
│ ~/workspace/experiments/agent-skills/skills │
└─────────────────────────────────────────────────────────────────────┘
│
skills-broadcast push
│
┌──────────────────────────┼──────────────────────────┐
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Pi Agent │ │ Codex │ │ Claude Code │
│ ~/.pi/agent │ │ ~/.codex │ │ ~/.claude │
│ /skills │ │ /skills │ │ /commands │
└─────────────┘ └─────────────┘ └─────────────┘
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Antigravity │ │ pi-mono │ │ memory │
│ ~/.gemini │ │ .pi/skills │ │.agents/skill│
│ /skills │ │ │ │ │
└─────────────┘ └─────────────┘ └─────────────┘
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ KiloCode │ │ │ │ │
│ ~/.kilocode │ │ │ │ │
│ /skills │ │ │ │ │
└─────────────┘ └─────────────┘ └─────────────┘
Quick Start
# Add to PATH (one-time)
echo 'export PATH="$HOME/workspace/experiments/agent-skills:$PATH"' >> ~/.zshrc
source ~/.zshrc
# Check current sync status
skills-broadcast status
# Edit skill anywhere, then broadcast to all IDEs
skills-broadcast push
# Pull latest skills into current project
skills-broadcast pull
Commands
| Command | Description |
|---|---|
skills-broadcast push |
Push local → canonical → all targets |
skills-broadcast push --from PATH |
Push from specific location |
skills-broadcast pull |
Pull canonical → current project |
skills-broadcast status |
Show all targets and sync state |
skills-broadcast register [PATH] |
Register a project for fanout |
skills-broadcast unregister [PATH] |
Remove a project from fanout |
skills-broadcast targets |
List all registered projects |
skills-broadcast info |
Show current paths and config |
Supported IDEs
| IDE | Skill Location | Status |
|---|---|---|
| Pi | ~/.pi/agent/skills |
✓ Supported |
| Codex | ~/.codex/skills |
✓ Supported |
| Claude Code | ~/.claude/commands |
✓ Supported |
| Antigravity | ~/.gemini/skills |
✓ Supported |
| KiloCode | ~/.kilocode/skills |
✓ Supported |
Workflow: Edit Anywhere
- Edit skill in any IDE or project
- Run
skills-broadcast pushfrom that location - Changes flow: Local → agent-skills repo → All registered targets
# Example: Edit assess skill in pi-mono, broadcast to all
cd ~/workspace/experiments/pi-mono
vim .pi/skills/assess/SKILL.md
skills-broadcast push
# Or specify source explicitly
skills-broadcast push --from ~/.codex/skills
Configuration
Override defaults via environment variables:
# Custom canonical repo location
export SKILLS_CANONICAL_REPO="$HOME/my-skills-repo"
# Custom broadcast targets (colon-separated)
export SKILLS_BROADCAST_TARGETS="$HOME/.pi/agent/skills:$HOME/.codex/skills"
# Auto-commit to canonical repo after push
# Auto-commit to canonical repo after push
export SKILLS_SYNC_AUTOCOMMIT=1
Registering Projects
To include a new project in the broadcast list, add its absolute path to ~/.agent_skills_targets:
echo "/home/user/workspace/my-new-project" >> ~/.agent_skills_targets
The tool will verify if the directory exists and automatically sync to any supported agent skill directory (.pi/skills, .agent/skills, etc.) found within it.
Alternatively, you can set SKILLS_FANOUT_PROJECTS="/path/to/proj:/path/to/proj2" in your environment.
Legacy: skills-sync (Deprecated)
The old skills-sync script is still available but superseded by skills-broadcast:
# Old way (still works)
.agents/skills/skills-sync/skills-sync push --fanout
# New way (recommended)
skills-broadcast push
Conflict Detection
The tool uses a Time-Based "Winner Takes All" strategy to detect the source of truth:
- Scans all local agent directories:
.pi/skills,.agent/skills,.codex/skills,.claude/skills. - Compares modification times: Finds the directory containing the most recently modified file.
- Selects the newest: The directory with the latest changes is automatically selected as the source for the
push.
This ensures that if you edit a skill in any agent environment, skills-broadcast naturally respects that edit as the latest version.
[skills-broadcast] Found skills with DIFFERENT content across targets:
⚠ memory: 2 different versions exist
a1b2c3d4: /home/user/.codex/skills /home/user/.claude/commands
e5f6g7h8: /home/user/workspace/pi-mono/.pi/skills
→ Newest file found in: /home/user/workspace/pi-mono/.pi/skills
→ Selected Source: /home/user/workspace/pi-mono/.pi/skills
Troubleshooting
Target directory missing?
- The script creates missing directories automatically
- Parent directory must exist
Changes not appearing in IDE?
- Some IDEs cache skills; restart the IDE
- Check
skills-broadcast statusto verify sync
Conflicts between IDEs?
- The tool now detects actual content differences (not just timestamps)
- It suggests which location has the newest git commit
- Use
--forceto override if you know your version is correct
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?