Skill Publish

Use the skill-cli command as the default control surface for publishing a skill and confirming the published result.

When to use

Use this skill when the user wants to:

• publish a skill
• publish a new version
• publish with a changelog
• retry a failed publish
• confirm the published result

Before you publish

Make sure the user has these inputs ready:

• the directory to publish
• the version number
• an optional changelog if they want to include one

Do not start with login by default.

Only move into login if the publish command fails because authentication is required.

Core workflows

Inspect for last published version

Run:

skill-cli inspect <slug>

Publish a skill

Decide a new version number that is higher than the last published version and matches semver standards, then run:

skill-cli publish <dir> --version <version>

Publish with a changelog

Run:

skill-cli publish <dir> --version <version> --changelog <text>

Retry after login

If publish fails because login is required, choose the login flow that fits the situation:

• If a token is already available, run skill-cli login --token <token>.
• If a user can help complete browser login, run skill-cli login.

After login finishes, rerun the same publish command.

Confirm the published result

Use skill-cli inspect as the standard confirmation step.

Run:

skill-cli inspect <slug>

If the user wants to confirm a specific version, run:

skill-cli inspect <slug> --version <version>

If the user wants to confirm the published file content, run:

skill-cli inspect <slug> --file SKILL.md

or:

skill-cli inspect <slug> --file SKILL.md --version <version>

Use skill-cli inspect when the result should come back in the command line for agent-facing confirmation.

Use skill-cli docs only when the user wants to open the page in the browser for user-facing viewing.

If a command fails

If publish fails because login is required, run one of these:

• skill-cli login --token <token>
• skill-cli login

Then rerun the original publish command.

If publish fails because inputs are incomplete, confirm the directory and version, then rerun the command.

If publish succeeds, follow up with skill-cli inspect instead of using browser output as the validation step.

Command patterns

Use these patterns when the user asks for a full publish flow:

1. Publish then confirm: skill-cli publish <dir> --version <version> -> skill-cli inspect <slug>
2. Publish with changelog then confirm version: skill-cli publish <dir> --version <version> --changelog <text> -> skill-cli inspect <slug> --version <version>
3. Publish then confirm file content: skill-cli publish <dir> --version <version> -> skill-cli inspect <slug> --file SKILL.md
4. Publish fails because login is required: skill-cli login or skill-cli login --token <token> -> rerun skill-cli publish ...

Prefer browser opening only when the user explicitly wants to view the published page.

See all available commands

Run:

skill-cli --help