Artifacts & Version Control¶
One collection, every agent surface. Add, version, and deploy skills, commands, agents, MCP
servers, and other agent artifacts across .claude, .codex, .gemini, and beyond — without
copy-pasting config folders between repos.
Who it's for: individual developers building a reusable library, and teams who want a single source of truth their whole toolchain deploys from.
Your collection lives in SQLite plus your own filesystem — there's no external database to stand up for local use. See Collection Init & Config for how a collection is structured on disk.
How to read the tags
Local — shipped in the local edition, no flag needed. Enterprise — shipped in enterprise, no launch-blocking gate. Gated — shipped, but behind a feature flag, auth wall, or readiness gate (see the caveat in each row). Future — roadmap only; not available today.
What you can do today¶
| Capability | Availability | Learn more |
|---|---|---|
| Full artifact lifecycle: initialize a collection, add from GitHub or local disk, deploy to a project, sync back from upstream | Local | Adding Artifacts, Deploying Artifacts |
| 21 artifact types across 4 capability tiers, all sharing universal collection membership and versioning | Local | See Guides for type-specific how-tos |
| Deploy an artifact straight to a GitHub branch via pull request | Local | Deploy to GitHub via PR |
| Scan an existing project and import artifacts already living in it | Local | Scan & Import Existing |
| Bundle multiple artifacts into a composite unit (bundles, deployment sets) for one-shot install | Local | Bundle & Composite Authoring |
Cross-instance artifact portability — export and import a .skillmeat-pack between SkillMeat instances |
Gated — behind portable_bundle_v2_enabled / enterprise_portability_enabled, both default OFF |
Team Sharing Guide |
Who owns what: collection scope¶
Every surface — API, web app, and CLI — defaults to your personal collection unless you explicitly switch to a team or admin scope. Nothing you add is silently shared. See Collection Init & Config for how scope and precedence work day to day.
Go deeper¶
- Adding Artifacts — bring artifacts in from GitHub, local disk, or the marketplace.
- Deploying Artifacts — push a collection artifact into a project.
- Assembly Authoring — compose artifacts into reusable assemblies.
- Version History & Restore — inspect and roll back artifact history.
- Next: Sync & Versioning for keeping artifacts current after they're deployed.