How to share a skill with a teammate who doesn't code

A skill is only useful to someone who can run it. When that someone is a teammate with their own agent but no appetite for a setup dance, the friction is the install — cloning a repo, pointing a tool at it, hoping the versions line up. The lowest-friction thing you can send another person’s agent is not a repo. It’s a URL.

Share creates a link, not a package

Publish your skill, then share it:

skillsafe publish ./my-skill --share

That returns a link like https://skillsafe.ai/share/shr_abc123def456. A share link is revocable and can be set to expire — it’s a Dropbox link for a skill, not a permanent public listing. --share keeps it link-only; add --public instead to also list it in the searchable registry. Either way, your teammate opens the link and sees what the skill is, its version, its trust verdict, and the install command.

But the real trick is one query parameter.

Append ?md and the link becomes agent-ready

Add ?md to any share URL:

https://skillsafe.ai/share/shr_abc123def456?md

and it returns a single self-contained plain-text document: the skill’s provenance, its tree hash, the install commands, and the complete SKILL.md body — everything an agent needs to use the skill, in one response. No second request to discover the instructions, no install to read them, no account to fetch them.

This is the part that makes it work for a non-coder. You send the link. Their agent fetches it, reads the whole skill, and can act on it immediately. There’s nothing for your teammate to configure — they paste a URL into their tool and the skill is available. If they later want it installed permanently, the same document tells their agent exactly how.

Reading a skill this way deliberately doesn’t count as an install, so it never inflates your numbers when a link gets opened, crawled, or previewed. And revoked or expired links return a clear “no longer available” rather than a dead page.

Why not just send the repo?

You can, and for another developer it’s fine. But a repo asks the recipient to do the assembling — clone, place, pin, verify. A share link with ?md inverts that: the assembling is already done, and the payload is one fetch away. For a teammate whose relationship with the terminal is “please, no,” that inversion is the whole difference between “I’ll get to it” and “done.”

The security is still there

A shared skill carries its scan report and tree hash. When someone installs from the link rather than just reading it, the files are verified against that hash — the same dual-side verification every SkillSafe install gets. Sharing widely doesn’t mean trusting blindly; it means the trust travels with the link.

Send a skill to a person who has an agent and this is the shortest path there is. Send it to a person who has no agent — someone who needs to click a button and get an answer — and a link to a skill isn’t enough. That person needs an app, which is a different post.

More ways to run a skill: on any machine · on a schedule · in a browser