DEV Community

Cover image for Stop copy-pasting prompts: give your AI agent installable skills (quickstart OSM)
OpenSkill.md profile image Tieu Philippe KHIM
Tieu Philippe KHIM for OpenSkill.md

Posted on • Edited on

Stop copy-pasting prompts: give your AI agent installable skills (quickstart OSM)

#ai #skills #openskillmd #osm

TL;DR

  • AI agents like Claude Code and Codex can load skills — markdown files that teach them expertise — but finding good ones means digging through scattered repos.
  • OpenSkill.md (OSM) is an open-source registry + CLI: search, install, and score agent capabilities in one command.
  • The whole loop: npm i -g @openskillmd/osm → osm search → osm add. Done in under a minute.

The problem

If you use an AI coding agent daily, you have probably built a private stash of prompts: your testing conventions, your commit style, your framework quirks. And you paste them. Again. And again.

Skills fixed part of this. A skill is just a SKILL.md file — instructions your agent loads automatically when the task matches. Write once, reuse forever. The ecosystem took off fast: Anthropic ships official skills, and hundreds of community skills live on GitHub.

Which created the next problem: discovery. Skills are scattered across repos with no central index, no search, and no way to tell a great skill from a broken one before installing it.

That is exactly the gap package managers filled for code. So we built one for agent capabilities.

The quickstart

1. Install the CLI

npm i -g @openskillmd/osm
Enter fullscreen mode Exit fullscreen mode

2. Search the registry

osm search testing
Enter fullscreen mode Exit fullscreen mode

You get a ranked list of skills matching your query, with quality scores.

3. Inspect before you install

osm info <slug>
Enter fullscreen mode Exit fullscreen mode

For any skill backed by a source repo, the output hands you the exact install command, ready to paste.

4. Install it

osm add anthropics/skills@frontend-design
Enter fullscreen mode Exit fullscreen mode

osm add pulls the skill straight from its source repo and drops it where your agent expects it — it is agent-aware, so Claude Code, Codex and Cursor each get the right location. Installing one skill from a multi-skill repo? The @skill suffix handles it.

5. Check what's installed

osm list
Enter fullscreen mode Exit fullscreen mode

That's it. Your agent picks the skill up on its next run. No config, no copy-paste.

Going further

  • Let your agent shop for itself — osm router install drops a meta-skill that teaches your agent to discover and install skills on demand from the registry.
  • Score your own skills — osm score SKILL.md evaluates a local skill for quality before you share it.
  • Beyond skills — the registry also covers blueprints (output quality enforcement), MCP servers (osm mcp setup prints the config for Claude/Cursor), and full plugin bundles (osm plugin install).

What's next

Authenticated publishing (osm login / osm publish) is on the roadmap — we are building this in public, and the whole thing is MIT-licensed.

Try it, break it, tell us what's missing: openskill.md · GitHub

What skill would you publish first? 👇

https://openskill.md/

Top comments (0)