One library. Every agent.
Fork the repo, add your markdown skills, deploy, point your agents at it. Claude, Cursor, anything that speaks MCP — same source, every project.
https://agent-skills-mcp.alibugatekin.com/mcp2 skillsSkills, but global
Three MCP tools — list_skills, get_skill, read_skill_file — and a REST view at /skills if you want to poke at it. Spin up your own instance and every agent in every project pulls from the same library.
One library, every agent
Same skills feed Claude, Cursor, anything that speaks MCP. Write a skill once and every agent gets it. No per-tool drift, no scattered copies.
Your skills, your server
Self-hosted on your own domain. Your skills stay yours — no SaaS lock-in, nothing leaves your server.
Cheap on tokens
Built on the same skills pattern Anthropic uses inside Claude. Agents pull only what they need, only when they need it.
What a live instance looks like
These are the skills the demo instance is serving right now (at agent-skills-mcp.alibugatekin.com). Fork the template, deploy your own — your skills show up here instead of mine.
Make it yours
Here’s the playbook. Fork the repo, fill it with your skills (markdown files), deploy wherever Node runs. ~5 minutes from clone to live URL.
Fork the template
One click on GitHub. The repo comes with a sample skill, the MCP server, and a deploy-ready setup.
Add your skills
Drop markdown files in skills/. One folder per skill. Name + description in the YAML frontmatter.
Deploy anywhere
Railway, Render, Fly, Coolify, your own VPS — anywhere a long-running Node process runs. The URL you get back is your global skill library.