Skip to content

Registry & publishing (zero-ops)

SkillFoundry has no server. "The registry" is just JSON, which means discovery and sharing work through ordinary git/GitHub workflows.

Sources

forge search / forge add combine three sources, in priority order:

  1. starter — the 15 skills bundled with the package (always available).
  2. local — your personal registry.json at ~/.config/skillfoundry/registry.json.
  3. community — an optional cache (~/.config/skillfoundry/community.json) populated by forge publish --registry community.

Local registry

forge publish ./my-skill --registry local

Writes the skill entry into your local registry.json so forge search and forge add can resolve it immediately.

Community registry

forge publish ./my-skill --registry community --dry-run   # preview the entry
forge publish ./my-skill --registry community             # record + PR steps

This records the entry locally and, when the GitHub CLI (gh) is installed, prints the exact steps (and PR body) to contribute it to the public skillfoundry/registry repo. No backend to host, no account system to build.

Install

forge add my-skill --client all          # every detected client
forge add my-skill --client claude-code  # a single client

Installs are idempotent: re-installing overwrites. The same skill directory is written unchanged to each targeted client's skills/ folder.