Manage your team's agent skills in one place
Keep the Claude skills and SKILL.md agent skills your team writes in a private skill repository on Gitoro. Changes go through pull requests, access decides who gets which skill, and everyone uses them where they work: Claude, ChatGPT, Gemini, Claude Code, Codex or any MCP agent. On every plan, Free included.
---
name: release-notes
description: Drafts release notes from merged pull
requests. Use when asked for release notes, a
changelog or what changed since a version.
---
# Release notes
1. List the pull requests merged since the last tag.
2. Group them: new, improved, fixed.
3. Write one plain line per change, for customers.
4. Leave out internal refactors and test changes.
A skill is a folder with a SKILL.md
Agent Skills is an open format, first developed by Anthropic. A skill is instructions for a task, plus any scripts and reference files it needs. An agent reads only each skill's name and description until a task calls for it, so it can keep many skills at hand. The Claude app, Claude Code, Codex and many other agents read the same format.
Skill repository or code repository?
A skill repository is a Git repository like any other, so you clone it, branch, push and review in the same way. What changes is what Gitoro does with its default branch.
| Topic | Code repository | Skill repository |
|---|---|---|
| What it holds | Your source code | Your team's agent skills: folders with a SKILL.md |
| What it opens on | Its files and README | Its skills, with any that have a problem listed apart |
| The default branch | The latest version of your code | What's published: every skill on it goes to everyone who can read the repository |
| Skills inside it | Stay with that code: an agent working in a checkout can load them from there, for example .claude/skills. They aren't shared in the Library or over MCP | Shared with everyone who can read the repository: in the Library, over MCP and in the Claude Code plugin |
| When a change is merged | It's in the code | Changed skills are checked, scanned for secrets, filed by category and delivered to agents |
| What's in it | Code, issues, pull requests, pipelines and security | Skills, changes (pull requests) and files |
| Git, pull requests and access | Yes | Yes, the same branches, approvals, code owners and access rules |
Any repository can become a skill repository, and back again, in its settings. Nothing in the repository changes when it does.
Drafts release notes from merged pull requests.
Writes customer-facing text in the company voice.
Drafts a blameless postmortem from logs and notes.
Checks a migration for locks and data loss.
Every skill your team uses, in one library
A skill repository is a Git repository whose default branch publishes its skills. Keep one for the whole company, or one per team. The Library shows every skill you can read across them, filed by category and searchable, so people find a skill before writing it again.
SKILL.md is missing a description
Change skills the way you change code
What's on the default branch is published, so a change reaches everyone when it's merged. Protect the branch and require approvals, and every new or changed skill is reviewed first. Agents can improve skills too: they open a pull request like anyone else.
Repository access
The highest level from any source wins. Greyed-out sources are overridden by a higher one.
| Repository | Access | Comes from | Direct grant |
|---|---|---|---|
| api | maintain | Team: Platform · maintainAll workspace members · write | None⌄ |
| backend | write | All workspace members · write | None⌄ |
| billing | write | Direct grant · write | Write⌄ |
| web | write | All workspace members · writeDirect grant · read | Read⌄ |
1 unsaved change · the review shows the seat impact before anything is saved
DiscardReview changesWho gets a skill is who can read its repository
There's no separate list to keep up to date. Give a team read access to a skill repository and its members, and their agents, get its skills. Take the access away and the skills stop arriving. Copies already on someone's computer stay until they're removed there.
From a procedure to every agent, step by step
How a team goes from "we keep explaining this" to every agent knowing it.
- 1
Create a skill repository
In your workspace, choose New repository, then Skills. Tick Add the skill-writer skill to start with a skill that writes skills for you.
- 2
Write the skill
Add a folder with a SKILL.md, or ask your agent to turn what you just did into a skill. skill-writer checks the format and Gitoro's rules for it.
- 3
Review and publish
Open a pull request. Once it's reviewed and merged into the default branch, the skill is published to everyone who can read the repository.
- 4
Connect Claude Code
Gitoro builds a Claude Code plugin, skills, holding every skill you can read, and keeps it up to date. Paste the snippet from Connect your agent into Claude Code's settings once, and Claude Code installs it.
- 5
Or Claude, ChatGPT and Gemini, for everyone else
No terminal needed: add Gitoro as a connector in the app with one address, and sign in to Gitoro. The app reads your skills when a task needs them. Developers using Codex connect over MCP the same way.
- 6
Keep them up to date
Apps connected to Gitoro read the current version every time. Claude Code fetches changes with auto-update on, or /plugin marketplace update. A download stays as it is.
Where your skills go
Gitoro hands skills to your agents in several ways. None of them runs a skill for you: your agent does, on your machine.
| Agent | How it gets your skills |
|---|---|
| Claude Code | Gitoro builds a Claude Code plugin for you, called skills, that holds every skill you can read. Add your workspace to Claude Code's settings once (Connect your agent gives you the snippet) and Claude Code installs it. Changes arrive with auto-update or /plugin marketplace update. |
| Claude, ChatGPT and Gemini | Add Gitoro as a connector with one address and sign in to Gitoro. They read your skills from Gitoro when a task needs them, always the current version, and lose access the moment you disconnect them. |
| Codex | Gitoro's MCP server with the sync skill, or a download unzipped into ~/.agents/skills. |
| Any MCP agent | search_skills lists your skills with their versions, get_skill returns one with all its files. |
| Other Agent Skills tools | A zip with one folder per skill, or one skill at a time. |
| Agents that support MCP skills | Read straight from Gitoro with the MCP Skills Extension: nothing to install, and always the current version. Until your agent supports it, a few lines in CLAUDE.md or AGENTS.md do much the same. |
Gitoro serves skills with the MCP Skills Extension, the open standard for agents to load skills from an MCP server. As agents adopt it, they read your skills straight from Gitoro, with nothing to install or sync, and access checked on every read.