We're excited to announce Share Links—a simple, safe way to share a skill outside your workspace with a single URL.

The Problem: Skills Were Locked In

A great skill you built was trapped in your workspace. Want to send it to a friend, another team, or a client? Your only options were awkward: copy-paste the instructions into a message, or export and email a JSON file. There was no clean way to say "here, try this skill" and have someone actually use it.

A share link lets you hand out one skill via a single URL at /s/<token>. Anyone with the link can preview the skill, and once signed in, import it as their own independent copy.

It's the easiest way to spread a skill—and it's built to be safe.

"Unlisted," Not "Secret"

The link's token is server-side, unguessable, and not derived from the skill's ID (so no one can enumerate your skills). It's unlisted, not secret—but the guarantees are real: links are revocable and can expire or be capped. You stay in control.

Only Stable Skills Are Shareable

You can only share a skill once it has a promoted stable release. A share link always hands out a frozen, released snapshot—never your live draft, never a half-finished edit.

This is an intentional, higher bar than internal serving: sharing requires a deliberate stable release before anything reaches an outsider. If you hit Share on a skill that isn't stable yet, you'll get a one-click "Publish & share" that promotes your draft to stable and then creates the link.

Pinned vs Live

When you create a link, you choose how it tracks your releases:

ModeRecipients getBehavior
Pinned (default)a specific frozen releaseFrozen to whatever was stable when you made the link. Your later releases don't change it.
Live (opt-in)your current stableNew visitors always get your latest release.

Pinned is the default because it's predictable: your future edits won't silently change what a recipient sees. Choose Live when you want the link to always serve your newest stable version.

Either way, the link always resolves to a released snapshot—never a draft.

Optional Expiry & Import Cap

When you create a link, you can optionally set:

  • Expiry — a date after which the link stops working.
  • Max imports — a cap on total imports; once it's hit, the link stops importing.

And you can revoke any link at any time, which kills it immediately. Mix and match: a link that expires in 7 days, caps at 10 imports, and can be pulled the moment you change your mind.

The Recipient Flow

Sharing is safe by design—nothing runs on anyone's machine without a clear preview and a sign-in:

  1. The recipient opens your link and sees a preview: the skill's name, description, the full instructions that would run in their Claude Code, the format, who shared it, and which version. They see exactly what they'd be importing.
  2. To import, they sign in and pick a target workspace. (Viewing is link-gated; importing requires auth, so identity is captured and rate-limited.)
  3. SuperClawd creates a brand-new, independent copy of the skill in their workspace—fresh, fully their own. There's no link back to your workspace data.

Because the import is a real skill in their workspace, it counts against their tier's skill limits, just like any skill they'd create.

You Stay in Control

From the share UI you can see each link's activity counts—for example, "14 opens · 3 imports across 2 workspaces"—and a Revoke button per link. It's counts only; we don't surface who imported your skill beyond that. No surveillance.

Each imported skill also records lineage (which skill and version it came from), so attribution is preserved.

Why This Is the Safe Default

A shared skill is executable instructions—it's supply-chain shaped. Two guardrails keep it honest:

  • Preview before import. Recipients always see the exact instructions before accepting.
  • Auth to import. Anonymous browsing is fine; importing requires signing in.

Together, nothing surprising ever lands in someone's Claude Code.

Use Cases

  • Help a teammate on another team adopt a skill you built—send the link, they import their copy.
  • Share with a client or contractor without giving them access to your workspace.
  • Time-boxed sharing—set an expiry for a trial or a workshop.
  • Capped distribution—limit a link to a known number of imports.

Get Started

Share links are available now in all SuperClawd workspaces.

  1. Go to app.superclawd.com
  2. Open a skill with a promoted stable release (or use Publish & share)
  3. Click Share, pick pinned or live, set any expiry or cap
  4. Copy the link and send it

Want the full details on link modes, expiry, and the recipient flow? Read the docs at docs.superclawd.com.

Pro tip: Keep your link pinned when you want recipients to get a known-good version, and switch to live for a skill you're actively improving and want everyone to follow.