Share skills with your team
Publish a skill once to a project, team or organization, and your teammates' agents read it from Venom.
To share agent skills with your team, publish the skill in Venom to a project, a team or your organization. A teammate's agent, in Claude Code, Codex, Cursor or another connected client, lists the skills that apply to its context and loads the one it needs through MCP. Nobody has to copy instruction files between machines.
What is a skill?
A skill has a name, a description of when to use it, a Markdown SKILL.md, and optional supporting text files. Agents see the name and description first, then load the instructions when needed. Use skills for practices such as reviewing a migration, running an experiment, or writing release notes.
Where should it live?
| Place | Who gets it | Who can publish |
|---|---|---|
| Yours | Only you | You |
| Team | Team members and the team's projects | Team maintainers and organization admins |
| Project | People working in the project | Maintainers of the owning team and organization admins |
| Organization | Everyone in the organization | Organization owners and admins |
Pick the smallest place that fits. A review checklist for checkout belongs in that project. A release-notes format everyone follows belongs in the organization.
How do you publish one?
Write or import it.
On the Skills page, choose New skill or Import a skill. If you already have a skill folder with a SKILL.md, import it. You can import pasted or uploaded files, folders, ZIP archives, and public GitHub repositories or skill folders. GitHub imports copy files from a pinned commit. They don't run scripts or pull later upstream changes.
Save a draft and publish.
Edit and Save draft. Agents keep receiving the published version. When you are ready, Publish the package as a new revision.
An agent can also draft a skill with create_skill and edit_skill. It uses the same editing permissions as the Skills page. Personal skills publish right away. Team and project skills stay drafts unless an authorized user requests publication. Organization skills must be published by a person in the web app.
How does a teammate's agent read it?
The agent calls list_skills for its context and read_skill to load one:
- General work: organization, personal, and your teams' skills.
- Team: organization and that team's skills.
- Project: organization, owning team, and project skills.
Clients with native MCP skills support receive the organization skills you have enabled directly. Other clients get a loader for each, such as venom_skill_release_notes for a skill named release-notes. Agents are told to load relevant skills at the start of a session. Your client's own settings still apply.
Can people opt out?
Published skills start enabled. Anyone can turn one off for their own agents without affecting others. The setting takes effect when the client refreshes its tools or reconnects.
To remove a skill, Withdraw it. That prevents new loads, but it can't remove instructions already loaded into a conversation.
Skills guide behavior. They don't grant access or override Venom's permission checks.