Should You Buy or Publish a Claude Skill?
Use Anthropic’s public skill catalog as a baseline, inspect the release you would install, and require the seller to pass a version-matched fixture in Claude Code or the Claude Messages API before paying.
Buy a release you can identify and retest
Claude Code marketplaces catalog plugins and identify where Claude Code fetches them. Anthropic documents private repositories, direct sharing of a directory or ZIP, and submission to its public directory. For a paid offer, ask the seller to tie the trial to the release you will receive. Record the plugin name, fetch location, and the commit or archive checksum you actually evaluated. If the catalog points to a moving branch, ask how a buyer can recover a known working release after an update. Sellers can use a private catalog when buyers need ongoing releases and a fixed archive when they need a repeatable review copy. A concrete release check is to have two reviewers retrieve the delivered package independently and compare the recorded identity before spending time on functional evaluation.
Create a marketplace - Claude Code DocsRequire both a useful result and safe abstention
The Claude Messages API attaches skills to a code execution container using a skill identifier, a type, and optionally a version. If the seller demonstrates a Claude Code plugin and sells an API workflow, ask for a trial in the API runtime with the tested skill version recorded. Build a fixture that exercises a real judgment. For a purchase-order extraction skill, provide a synthetic invoice with an explicit order number, one that contains a tempting reference number but no order number, and one with conflicting candidates. The expected outputs could be the exact order number, an empty field, and a review flag. Ask the seller to return the raw structured results for inspection. A polished summary gives you little evidence about whether the workflow fills missing fields with guesses.
Using Agent Skills with the API - Claude Platform DocsTurn a demo into a test
Start with a task you can judge from its output. Anthropic’s public skills repository contains examples intended for demonstration and education, making it a place to inspect how a skill is packaged. A community demo can help you find a candidate. Before relying on it, ask for the installable package or access to a trial, the exact version, and a list of required tools and data access.
For an illustrative trial, give a document-review skill three synthetic inputs: a complete purchase order, one with a missing currency, and one with conflicting totals. Define the expected fields and which cases must go to review. Run the same inputs twice on the same version. A pass means the required fields stay consistent and both exceptions reach review. A plausible answer that silently picks a currency is a failure.
GitHub - anthropics/skills: Public repository for Agent Skills · GitHubCheck what the buyer installs
A Claude Code plugin marketplace lists plugins and where Claude Code can fetch them. Use Anthropic’s directory as a public distribution candidate and a private Git-backed marketplace when you need to limit repository access. If you buy access to a private catalog, confirm whether the fee covers the current package, future releases, or support. Ask which repository permissions the buyer needs and what access ends when the agreement expires.
Before rollout, have a pilot user with ordinary buyer permissions register the catalog in Claude Code, install the listed plugin, and run its documented skill on a sample. Repeat with an account outside the intended group using the same catalog URL. The first account should complete the workflow and the second should be denied repository access. Repository access controls future downloads, so establish separately how you’ll handle copies already installed.
Create a marketplace - Claude Code DocsTest the hosted offer at its boundary
To sell access while keeping your skill package on your side, put a narrow application interface in front of the workflow and give customers access to that interface. If you use the Claude Messages API, custom skills run through its code execution tool. Specify the skill in the container with its type and ID, and set a version for the acceptance test so you can identify exactly what ran.
Give the buyer a trial with a normal input and an input the service should decline or refer to a person. Check that the buyer can retrieve the promised output, see why the exception stopped, and retry without creating duplicate deliverables. Before taking payment, define whether the billable unit is a submitted job or an accepted output and write down how you count retries and failures.
Using Agent Skills with the API - Claude Platform DocsChoose the scope of an internal rollout
For an internal Claude library, Team and Enterprise organization owners can provision skills for everyone. For a skill intended for a specific group, the organization management guide points to plugins. Before using the organization-wide route, check the code execution and Skills settings in the Policy tab. In Organization settings under Plugins & skills, select Add, choose Upload a skill, and select the ZIP containing SKILL.md.
Have a regular member find the uploaded skill in Customize > Skills and run a synthetic case. If it is missing, verify the organization policy and member toggle before repackaging the ZIP. If only one department should receive the workflow, use a group-scoped plugin and test with an account inside and outside the group. That second account is how you detect accidental organization-wide distribution.
Provision and manage skills for your organization | Claude Help Center