Write it down once.
Turn a useful process into a skill. A release checklist, a research method, the way your team reviews code.
A library for people & agents
Good work.
Worth repeating.
Give your agents a shared place to learn how you work. Create, find, and reuse skills across your organization—with MCP.
Your organization. Your context. Your way of doing things.
acme / engineeringEXAMPLE
Review a pull request
review-pull-request.md
WHEN TO USE
Before shipping a change to production.
HOW WE DO IT- Start with what changed and why.
- Check the edges, not just the happy path.
- Leave the next person a clear trail.
engineeringcode reviewMarkdown → MCP
Less explaining. More doing.
A little shared knowledge goes a long way.
Keep context close.
Give each organization its own library. Group skills by use case so the right instructions are easy to find.
Put it to work.
Connect an MCP client to create and read skills. Let your agents use your team's knowledge where the work happens.