Skip to content
Docs: Overview

Start here

Skillify docs

How to keep the agent skills in every repository your team owns in one place: shared, tailored per repo, reviewed and measured.

On this page

Agent skills are folders with a SKILL.md that teach an agent how your team works: how to review a pull request, how to write tests, how to triage an issue. They are easy to write and hard to keep straight once a team has more than a few repositories. Skillify keeps them in one library and writes the right ones into each repo.

What Skillify does

  • Three ways to have a skill. Import one from GitHub and use it as-is or add your team's notes; write a team skill for any repo; or write one for a single repo. Every edit is a new version, and imported sources are checked for upstream changes every day.
  • Global skills. Make a skill global and every repo gets it, including new ones. Repos can opt out unless it is required.
  • Tailored per repo. Add skills to a repo, add an overlay with notes only that repo needs, or pin a version.
  • Installed as files. One command writes the skills, an AGENTS.md block and a small CLI into the repo. You commit them, so every clone, CI job and agent session has them without signing in to anything.
  • Changes by review. Edits go through proposals. A person other than the author approves; agents can propose but never approve.
  • Drift and usage. Each sync reports what is on disk, so you see which repos are behind or edited by hand. An optional hook counts how often each skill is used.
  • An MCP server. Agents can browse the library, add skills to a repo and propose edits from inside a session.

Who does what

Most of the team never opens Skillify: they clone a repo and their agent finds the skills. The people who look after standards use the dashboard to choose skills, review proposals and see usage. Anyone can run sync.

Where to start