Skills
Share the practices your agents should follow, alongside the projects where they apply.
What a skill is.
A skill contains a name, a description of when to use it, a Markdown SKILL.md, and optional supporting text files. Agents see its 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 skills 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 |
Agents discover different skills for each context:
- General work: organization, personal, and your teams' skills.
- Team: organization and that team's skills.
- Project: organization, owning team, and project skills.
Skills with the same name in different places stay separate. Copy to copies a skill to another place you manage.
Skills and Venom's own guidance.
Venom's workflow guidance doesn't live in a skill. Agents get it from the MCP server's instructions, Venom Full's hooks in Claude Code and Codex, and short reminders in tool responses for other clients. New organizations start with no skills.
Publish organization skills for your own conventions, such as how your team reviews a change, so people don't need to copy them into local agent configs. Organizations that already published a session-start skill keep it as an ordinary organization skill.
Write, import, publish.
On the Skills page:
- Choose New skill or Import a skill. Imports accept pasted or uploaded files, folders, ZIP archives, and public GitHub repositories or skill folders.
- Edit and Save draft. Agents continue receiving the published version.
- Publish the package as a new revision.
GitHub imports copy files from a pinned commit. They don't run scripts or pull later upstream changes.
Withdraw prevents new loads of all revisions. It can't remove instructions already loaded into a conversation.
Turn skills off for yourself.
Published skills start enabled. Turning one off disables it for your agents; other people keep their own settings. Your choice survives new publications and takes effect when your client refreshes its tools or reconnects.
How agents load skills.
list_skillsdiscovers skills;read_skillloads them.create_skillandedit_skilluse the same editing permissions as the Skills page. Personal skills publish immediately. Team and project skills remain drafts unless an authorized user requests publication. Organization skills require a person to publish them in the web app.- Clients with native MCP skills support receive the organization skills you have enabled directly. Other clients receive a loader for each of those skills, such as
venom_skill_release_notesfor a skill namedrelease-notes.
Skills guide behavior. They don't grant access or override Venom's permission checks.