Agent skill marketplace: install capabilities, not whole agents
SKILL.md bundles you browse, paste from GitHub or skills.sh, or upload as zip — install onto any Neuro OS role without cloning a new agent.
Discuss this post in AI
Send a pre-filled prompt to ChatGPT, Claude, Gemini, or Perplexity — get a summary, ask follow-ups, or compare ideas from this guide.
Skills vs whole projects
On Neuro OS, you can install a full working project in one session — or add a skill into a project you already run. A skill is a SKILL.md bundle that teaches a role a specialized capability: a research workflow, a writing pattern, outbound playbooks, finance reconciliation, and more.
The marketplace is the open library. Skills are first-class objects — not buried config files you hunt across repos.
What you can do
Browse and search
Discover bundles others published. Filter by source — Neuro OS, community, your org — and pick the capability you need.
Install on any role
Add a skill to any role you own: your personal agent, a cloned specialist, or a connected coding agent. The bundle lands in the role’s skills folder in git and is available on the next run.
Share with the team
Forward a skill reference in a task thread. Teammates install the same bundle onto their roles — one pattern, many agents, no copy-paste prompts.
Bring your own
Four sources:
- Marketplace card — pick from the catalog
- Public URL — GitHub, clawhub.ai, skills.sh
- Zip upload — drop a bundle you received
- Author inline — write
SKILL.mdfrom scratch in your repo
How it differs from the agent library
| Agent library | Skill marketplace |
|---|---|
| Whole role to clone | Capability to add |
| New org-chart member | Teach an existing role |
| Full job description + connectors | Focused workflow package |
| Heavier onboarding | Lightweight upgrade |
Clone when you need a new persona. Install a skill when you need a new trick on someone already on the org chart.
Typical flow
- Find — search marketplace or paste URL from a colleague
- Install — choose which role receives the bundle
- Run — @mention the role; skill sits beside existing tools and job description
- Iterate — corrections update the skill in git; version history like any other change
Stack skills on a team
Install different skills onto different roles, then run them in one shared task thread:
- Research role gets deep research skill
- Draft role gets voice guide skill
- Reviewer gets compliance checklist skill
Coordinator sequences; Ask gates external sends. Skills do not replace the collaboration protocol — they specialize each role inside it.
Neuro OS vs single-machine setups
With Neuro OS:
- Shared library inside ops, not scattered repos
- Skills versioned in git per role
- Team can install the same bundle from a thread
- Reuse across agents under connector policy
Without:
- Manual filesystem copy per machine
- No audit trail when skills change
- Teammates re-discover the same prompt hacks
- Hard to know which role has which capability
FAQ
Is a skill the same as a prompt? No — it packages prompts, tool scopes, examples, and evaluation rubrics so the role gains durable domain behavior.
Does install replace existing skills? No — bundles stack; job description + skills compose.
Who can publish? Your org publishes internal skills to git; public marketplace entries follow your release process.
Related: What is a skill marketplace? · Marketplace · First AI hire blueprint