Enterprise Distribution & Marketplace

~12 min · skills, marketplace, enterprise, distribution

Level 0🌱 Novice

0 XP0/70 lessons0/11 achievements

0/120 XP to next level120 XP to go0% complete

Ship Skills the same way you ship libraries

Inside an organization, Skills become as important as shared libraries. Standardize how teams find, install, version, and update them. The patterns: (1) monorepo of Skills with versioned releases, (2) private marketplace served from internal infra, (3) plugin packaging for skills + agents + assets together.

For Anthropic's public marketplace, the bar is higher: clear docs, no secrets in paths:, well-described invocation intent, eval harness committed alongside. Marketplace publishing is reviewable; private distribution is your responsibility.

Code

Internal Skills monorepo layout·text

org-skills/
├── README.md
├── package.json          ← versioning + scripts
├── skills/
│   ├── sql-perf-advisor/
│   ├── pr-summary/
│   ├── changelog-writer/
│   ├── security-audit/
│   └── brand-rewrite/
├── plugins/
│   └── analyst-toolkit/   ← bundles 3 of the skills above
└── tests/
    └── run-all-evals.sh

# Versioning: tag releases (v1.4.0)
# Distribution: install from internal git url

Plugin manifest bundling skills·json

{
  "name": "analyst-toolkit",
  "version": "1.4.0",
  "description": "Skills + agents the analyst team uses every day",
  "skills": ["pr-summary", "changelog-writer", "brand-rewrite"],
  "agents": ["research-coordinator"],
  "permissions": {
    "fileAccess": "working-folder",
    "webFetch": false
  }
}

External links

Anthropic skills marketplace

Exercise

Stand up an internal Skills monorepo (a single Git repo with a skills/ folder, a README, a tests/ folder). Move two of your Skills into it. Tag a v1.0.0 release. Install it on a different machine to verify the distribution flow.