Skills are becoming the source code of how your company runs.
What SkillRepo does today
Publish once
A permanent home for your skills, tied to your GitHub identity.
A graded, versioned library
Curate what your team runs — every skill scored A–F.
Synced to your agents
One curated library across all 7 supported dev environments — Claude Code, Cursor, and more.
The way companies run is being rewritten.
For two years, agents mostly wrote code. Now they're starting to do the work the code was for — triaging support, reconciling invoices, running onboarding, checking compliance. The agent doesn't just help build the tool; it operates the function.
When an agent runs an operation, something has to tell it how your company does that operation.
When an agent does the work, the work becomes a skill.
A skill is that instruction set: the procedure, the policy, the steps your company follows to do one thing — packaged so an agent can load it and execute. Refunds over $500 need a manager. Onboarding provisions these six systems in this order. The know-how that used to live in a runbook, a senior engineer's head, or a buried Slack thread becomes something an agent runs.
Put together, your skills describe how the company works.
Stack enough of them and the picture changes. The set of skills an organization runs is a description of how that organization works — versioned, reviewable, and improvable like any other source. Change the skill, and you change how the business does that thing, everywhere at once.
Agents reach skills over MCP.
An agent needs two things to run an operation: a connection to your systems, and the skill that says what to do with them. MCP — the Model Context Protocol — is the connection. SkillRepo exposes your library over a remote MCP endpoint, so an agent can discover and read the skills it's entitled to, on demand, read-only.
This isn't theoretical. We run our own operations this way today — agent routines connect to SkillRepo over MCP and read the skills they need, on demand, with no copy-paste and no stale local files. Point any MCP-capable agent at the connector and it's working in a minute.
The SDLC didn't go away. Its output changed.
Skills don't escape software discipline — they need it more. Where did this skill come from? Who reviewed it? Is it the current version? Is it safe to run? That's versioning, review, provenance, and grading — the software development lifecycle, pointed at a new artifact.
That's what SkillRepo is, concretely, today: a graded, versioned, attributed library, distributed to every agent that needs it. The vision above is where it leads; this is the part you can use now.
Skills and MCP, untangled.
- Is MCP dead?
- No. MCP is the connection layer — how an agent reaches your tools and data. Skills are the instruction layer — what the agent should do once it's connected. They solve different problems, and an agent running real operations needs both.
- Skills vs MCP — when do I use which?
- Use MCP to give an agent access to a system. Use a skill to tell it the procedure to follow. MCP without a skill is an agent with hands and no playbook; a skill without access is a playbook it can't act on.
- What is an agent skill?
- A packaged, versioned set of instructions — plus any scripts or reference files it needs — that an agent loads to perform a specific task. On SkillRepo every skill is graded, attributed to its author, and reachable by your agents.
Put your skills where your agents can run them.
Publish and grade your skills today; connect an agent over MCP and it can find and read them on demand. The operating layer starts with the library.