Skill Registry Sync
Automatically register new skills in your owner agent’s SOUL.md from skill frontmatter so shipped skills show up without manual edits.
Overview
Skill Registry Sync is an MCP server for the Build phase that auto-wires newly shipped skills into owner-agent SOUL.md using `owner_agent` frontmatter and AUTO-GENERATED-SKILLS markers.
What is this MCP server?
- Reads `owner_agent:` frontmatter on newly shipped skills
- Rewrites only the AUTO-GENERATED-SKILLS block in SOUL.md
- Removes hand-edit-or-silently-fail when catalogs grow
- Scheduled cron every 6 hours (0 */6 * * * CT)
- Federation telemetry to Daily AI Agents hub (MIT, spec 1.0)
- Cron schedule: every 6 hours (0 */6 * * * CT)
- Server version 0.1.0, MIT license, federation spec_version 1.0
- Capability tags: agent, registry, skill, sync
What problem does it solve?
Every new skill used to require a fragile manual SOUL.md edit, so agents often shipped skills that never appeared in the live registry.
Who is it for?
Solo builders maintaining a growing skill repo with owner-agent SOUL.md and federation-style Daily AI OS workflows.
Skip if: Teams without SOUL.md markers, single static skill sets, or anyone who only needs a public skills.sh listing with no local agent manifest.
What do I get? / Deliverables
After install, SOUL.md stays current on a schedule and your owner agent’s skill list matches what you actually shipped.
- Updated SOUL.md skill block per owner agent
- Consistent owner_agent routing from frontmatter
- Telemetry events to hub.dailyaiagents.com when configured
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the job is wiring skills into agent runtime configuration right after you ship or add skills to the repo. Agent-tooling fits SOUL.md marker blocks and owner_agent frontmatter—the control plane for what your coding agent can invoke.
How it compares
Agent registry MCP automation—not a skill marketplace browser or a one-off Claude skill file.
Common Questions / FAQ
Who is skill-registry-sync for?
Builders who run Daily AI OS–style owner agents and need SOUL.md to reflect new skills without manual marker edits.
When should I use skill-registry-sync?
Use it when you regularly ship skills with `owner_agent` frontmatter and want the builder (or other owner) agent to pick them up within hours.
How do I add skill-registry-sync to my agent?
Register the MCP server from the Daily AI Agents registry entry, point it at your dailyai-os skills path, and ensure SOUL.md includes AUTO-GENERATED-SKILLS markers.