Share Claude Skills by Update Owner

Share a Claude Skill by choosing who should control its next update. Use a personal upload for an individual handoff, organization provisioning for client-managed rollout, a Claude Code marketplace for developer teams, or a consultant-run application when the client should receive results without receiving the package.

Give a single client a handoff they can repeat

Use a ZIP handoff when one client operator wants to run the Skill in Claude and can take responsibility for future uploads. Provide the package, a version label, a sample input, and an expected output. Have the operator confirm that code execution is enabled, upload the Skill in Customize > Skills, and run the sample from their own account. Agree on where they will obtain a replacement package if the workflow changes.

For an illustrative handoff, give a bookkeeper a synthetic invoice with three line items totaling $240 and an expected summary showing $240. The operator passes when they can reproduce the summary without your help. If the Skill is unavailable, check code execution before revising its instructions. Make sure the client can receive every file in the package before sending it.

Use aliases instead of customer account details when sharing a rollout report. Keep the mapping in the delivery system that already manages access.

Use skills in Claude | Claude Help Center

Test who can see a client-managed release

For a Claude Team or Enterprise client, ask the organization owner to choose the intended audience before uploading. The owner checks Cloud code execution and file creation and Skills in the Policy tab under Organization settings > Plugins & skills. An organization-wide upload makes the Skill available to everyone in Customize > Skills. If only a specific group should receive it, ask the owner to scope it through plugins.

In an illustrative rollout, eight finance operators should receive a close checklist while a sales test account should have no access. Have one finance operator confirm they can find and run the Skill, and have the sales account check visibility. If the sales account can see a restricted release, revisit the distribution scope before using client data. Record which owner will approve the next version.

A missing report has a different remedy from a stale release. Ask for an install receipt in the first case and a controlled update in the second.

Provision and manage skills for your organization | Claude Help Center

Put recurring developer releases in a catalog

If the client already works in Claude Code, use a plugin directory for a small handoff or a marketplace when you expect repeat releases. A marketplace is a Git-hosted directory or repository with a catalog that lists plugins and where to fetch them. Give a client maintainer access, have them register the marketplace and install the plugin, and ask them to document which release they validated.

Test initial installation and a subsequent update on a clean checkout. For example, change an illustrative release checklist to include a documentation check, then have the maintainer install that release and confirm the new check appears on the same fixture. If they can see the catalog but cannot install the plugin, verify that their account can also reach the location the catalog uses to fetch it.

Create a marketplace - Claude Code Docs

Keep the package on your side of the handoff

When the client should receive only an interface and its output, keep the package in a workspace you control and invoke it from your application through the Claude Messages API. Specify the Skill identifier, type, and intended version in the container configuration and include the code execution tool. Your application owns access to the interface, customer support, and the decision to move users to a newer release.

Before choosing a hosted vendor, verify who controls the runtime workspace, which users can retrieve the package, and whether releases can be pinned. Compare the vendor with your API implementation using the same synthetic input and two test accounts. Check whether the customer account can complete the job, whether it receives any package files, and whether your operator can replay the tested version. Treat any unexpected file delivery as a failed handoff.

Using Agent Skills with the API - Claude Platform Docs

Sources