How to share your custom Swarmbot app skill with a teammate

Swarmbot can turn a locally created or imported app skill into a time-limited share link. A teammate opens the link, reviews the package in the desktop client, and installs the same workflow without rebuilding it by hand.

You can share a custom Swarmbot app skill directly from My App Skills. Swarmbot creates a link, and your teammate opens that link to review and install the skill in the desktop client. This is useful when you want to hand over a working automation without passing ZIP files through chat or asking someone to rebuild every script, prompt, and resource manually. Start at App Skills → My App Skills → choose your skill → Share skill.

This guide was checked against the public Swarmbot 1.2.144 release. View the current public release manifest. 阅读中文版

Which skills can be shared?

Share links are available for content whose origin you control:

  • a local draft created in Swarmbot;
  • an app skill explicitly imported from a local ZIP package.

A skill installed from Skill Market cannot be re-shared from My App Skills. Market distribution and updates belong to the original publisher, so the recipient should find that skill in the market instead. Older installed items with no reliable origin also do not get a share action. If the package is genuinely yours, export a backup and import it again from the local ZIP so that Swarmbot can establish its origin.

The three delivery methods serve different jobs:

  • Share link: hand a snapshot of your own skill to a specific teammate;
  • Skill Market: publish to a wider audience and maintain versions as the publisher;
  • Cloud Sync: carry your own skills between computers signed in to the same Swarmbot account.

For a ready-made market skill, use the Swarmbot Skill Market import checklist. When you are simply moving to another computer, Swarmbot Cloud Sync is the better fit.

Create a share link in four steps

  1. Open App Skills and switch to My App Skills.
  2. Select Share skill in the target skill's actions.
  3. Choose an expiry: 1 day, 7 days, 30 days, or forever.
  4. Select Create share link, then copy it to your teammate.

One or seven days is usually enough for a team handoff. Use a permanent link only when you deliberately need a long-lived entry point. A shared package can be up to 64 MiB, so remove unused images, documents, or other large resources before sharing.

Creating another link for the same skill immediately invalidates the previous one. That is useful after sending a link to the wrong place, but it also means you should not casually regenerate a link while teammates are still using the old one.

What the recipient does

The recipient does not need a ZIP file. The normal flow is:

  1. Open the share link in a browser.
  2. Review the skill name and expiry on the landing page, then select Open client.
  3. Sign in with the local Swarmbot administrator account.
  4. Let the client download the snapshot and run the standard package preview and security validation.
  5. Review the resources and any reported risks before confirming installation.
  6. After installation, check the enabled state and AI visibility in My App Skills.

If validation finds risks that require a decision, Swarmbot pauses and asks the user to review them. A package that is blocked by validation is not installed. If an app with the same ID already exists, the shared package does not silently overwrite it; Swarmbot reports a conflict instead. Export important existing work before replacing or upgrading it.

A share link is a snapshot, not collaborative editing

The link points to a complete installable snapshot captured when you created it. Editing the skill on your computer later does not update an existing link. To distribute a newer version, create a new link; the old one becomes invalid.

After installation, the skill belongs to the recipient's local Swarmbot workspace. If the recipient signs in to a Swarmbot account, their own Cloud Sync can carry the installed skill to their other computers. It does not continue mirroring edits from the sender's computer.

This makes share links a good fit for three common situations:

  • handing a proven daily workflow to a new teammate;
  • sending a complete package of scripts, prompts, and resources to a remote collaborator;
  • asking a small group to review a skill before publishing it to Skill Market.

Treat the link like an access credential

Anyone who holds the link can download its skill snapshot, so do not post it in a public group, forum, or indexable web page. Microsoft's official guidance for general “anyone with the link” sharing makes the same practical point: recipients can forward a link, and anyone who receives it may gain access to the content. Read the Microsoft Support guidance.

For a Swarmbot skill, also check the package itself:

  • never place passwords, API keys, or access tokens in skill files or example configuration;
  • keep customer lists, device addresses, device-share codes, and other private data out of packaged resources;
  • prefer an expiring link for temporary collaboration;
  • if a link goes to the wrong recipient, generate a new one to invalidate the old link;
  • recipients should still read the installation preview rather than accepting everything just because the sender is familiar.

The landing page shows the skill name, expiry, and the Open client action. It should not be treated as identity verification for the sender or recipient.

Troubleshooting

There is no Share skill action

Check the source. Market-installed skills and older installed items with an unknown origin cannot be re-shared from My App Skills. For your own package, export it and import the local ZIP explicitly.

The link is expired or invalid

Ask the sender to generate a new link. Reopening the old URL will not help after its expiry or after a replacement link has invalidated it.

Open client does nothing

Make sure the current Swarmbot desktop client is installed, then open the link again. If the browser asks for permission to launch Swarmbot, the user must approve that handoff.

Swarmbot reports an app ID conflict

This protects the existing installation from a silent overwrite. Decide whether the current version must be kept, export a backup if needed, and handle the existing app before importing again.

The AI cannot see the skill after installation

Open My App Skills and check both the enabled state and the AI visibility scope. Successful installation and permission for a particular AI to use the skill are separate settings.

Choose the right path

Use an expiring share link to hand your own skill to a teammate. Use Cloud Sync to move your work between computers under the same account. Use Skill Market when you want to publish and maintain a skill for a wider audience. Choosing the right route avoids repeated setup without turning a temporary handoff link into an accidental public distribution channel.

参考来源