---
name: publish-skill
description: Package a tested original Skill with samples and a license, publish it to an authorized site or repository, and verify the public page and download. Use when a learner is ready to share a working version rather than merely create a local ZIP.
---

# Publish a version people can use

Main quest 4-4. A local page is a preview; publication needs a publicly reachable result.

## Prepare the release

Choose the learner's original Skill, version and actual publication destination.
Inspect the full package, source rights, runtime dependencies, examples and test evidence.
Keep secrets, private client inputs and unrelated files out of the release.
State a license matching the owner's intent; do not silently choose open source when resale restrictions exist.
For newbieskill original packages, personal/commercial use is allowed and complete-package resale is excluded.
Preserve licenses and notices of any dependency actually redistributed.
Read `references/release-check.md` for the compact release record.

## Stage and check

Build a complete archive retaining relative references and scripts.
Extract it in a new directory and compare included files to the manifest.
Use a new input with the installed package and retain the actual result.
Ensure the page explains required material, useful output, known limits and a path back to learning.
Show actual samples and recorded checks; do not invent ratings, sales or downloads.
Keep price, beta state and payment claims consistent with the actual product.
Do not call a placeholder checkout a functioning purchase flow.

## Publish within authority

If the user has already authorized this exact site/repository release, finish it without asking again.
Otherwise prepare the concrete release and ask for the destination/publication decision before the final external mutation.
Do not send messages, post to communities or contact creators as a side effect of publishing a package.
Use the existing hosting/repository workflow and retain the previous release as a rollback reference.
Never bypass a missing login, budget or provider approval with invented credentials.

## Verify the public result

Open the actual public URL and follow its download link.
Compare downloaded Skill/rules and license to the intended version.
Check public samples, next-step links and mobile layout on the deployed page.
Record deployment identity, time, URL, downloaded hash and any known limitation.
If verification fails, report the actual failed step; a successful upload alone is not a completed release.

## Self-tests and failure criteria

1. Release a complete foundational Skill page containing its actual sample, checks, LICENSE and complete download; verify the deployed URL and downloaded files.
2. Verify a second different package through its own public route and archive, not a copied hash or screenshot.
3. A staged package missing LICENSE or real sample evidence must be blocked before publishing.
4. A local-only URL, an inaccessible page or an archive missing required references fails the release claim.

## Continue

Return `/path/publish-skill/` or `/skills/` to choose a task-related branch.
Completing the learning trunk is not evidence of revenue; measure actual usage and payments separately.
Original free workflow. No complete-package resale.