Introducing org skills in Dropway

Most teams already have a few good skills sitting around. The problem is they never leave whoever wrote them. Someone has a solid PR review skill in a local folder. Someone else keeps a launch checklist in a doc. Another person pastes the same brief into chat every week.

Writing the first SKILL.md is easy. Getting the rest of the team onto the same version, in Cursor and Claude and wherever else they work, is not. So people quietly fork the prompt, and a month later you have four almost identical skills and no one knows which one is current.

Dropway already helps you share the finished artifact. Skills were the missing piece: the playbook that produced it. Org skills give that playbook a real home. We store and distribute the files. We do not run them. Your agents keep doing what they do. Your team stops starting from scratch.

Skills live in an org library. Anyone can publish. Admins manage folders (engineering, product, and marketing to start) and can mark a few as presets for new folks. Skills can show up in the org feed too, next to sites.

Free workspaces get up to 10 skills. Paid plans are unlimited. If you self host, there is no cap.

Open Skills. Drag in a skill folder, or write one in the editor with a live preview. Choose folders when you publish so it shows up in the right place.

From there you can preview files, download a zip, or edit and save a new version. Real content changes bump the version number, so people can tell when their local copy is behind.

If you already have a directory with SKILL.md, push it up. Use --folder on first publish if you want folders set right away.

dropway skills push ./my-skill --folder engineering
dropway skills list
dropway skills pull my-skill

dropway skills pull lands in .claude/skills/ by default and writes a small .dropway.json sidecar with the skill id and version. Run dropway skills check --update later to refresh anything that changed in the library.

dropway skills check
dropway skills check --update

Connected to the Dropway MCP server, an assistant can list skills, download one into .claude/skills/, pull a whole folder, or check for updates. Uploads go through upload_skill. Reads go through list_skills, download_skill, download_skill_folder, and check_skill_updates.

So someone can ask Cursor or Claude to install the PR review checklist and get the same files everyone else is using, without leaving the chat.

• Keep SKILL.md short. Put long examples in supporting files.
• Use folders so people can browse. Save presets for the starter set you want every new member to see.
• Run skills check now and then so local agents do not drift from the org copy.

If you already have a skill that works, publish it and let the team install it where they already work.