Before you can publish a skill, you need a display name. Set it with ap profile --set:
ap profile # View your current profileap profile --set # Interactively set your display name and bio
View shows your display name, email, bio, and join date. If no display name is set, a hint is shown.Set prompts for display name and bio. Press Ctrl-C to cancel.
ap publish will automatically prompt you to set a display name inline if you haven’t done so yet — no need to run ap profile --set separately.
Returns a unified table with columns: Slug, Title, Source, Type, Price, Security, Installed. Results are sectioned by source — AgentPowers native skills appear first, followed by external sources like ClawHub. Install counts and star ratings are shown inline in the Title column when available. The Installed column shows Yes (green), Edited (yellow for locally modified skills), or No.Options:
Install skills from external sources like ClawHub:
ap install ontology --source clawhub
External skills are downloaded to a sandbox, hashed, scanned through the full security pipeline, and only installed if they pass. See the External Skills guide for details.
Every ap install requires an explicit install scope — there is no default.
ap install my-skill --scope user # → ~/.claude/skills/my-skill/ (available everywhere)ap install my-skill --scope project # → ./.claude/skills/my-skill/ (only this project)
--scope user — installs to ~/.claude/skills/. The skill is available in every project you launch Claude Code from. Use this for general-purpose tools.
--scope project — installs to <cwd>/.claude/skills/. The skill is only available when Claude Code is launched inside this project (or any subdirectory). Commit .claude/skills/<slug>/ with your repo to share with your team.
If you omit --scope in an interactive terminal, the CLI prompts:
Install scope? [u] user — ~/.claude/skills (available everywhere) [p] project — ./.claude/skills (only this project)>
In non-interactive contexts (scripts, CI), omitting --scope exits 1 with an actionable error.The legacy --global flag still works as an alias for --scope user.
ap loginap publish ./my-skill # Free skill (default)ap publish ./my-skill --price 5.00 # Paid skill at $5.00
The CLI packages your directory as a ZIP, creates the skill record, and uploads the package. Your skill enters the security review pipeline automatically.
ap publish ./my-skill --bump patch # Default: patch bumpap publish ./my-skill --bump minor # Minor version bumpap publish ./my-skill --bump major # Major version bumpap publish ./my-skill --version 2.0.0 # Explicit versionap publish ./my-skill --changelog "Bug fixes and performance improvements"ap publish ./my-skill --bump patch --price 9.99 # Update version + change price
The --bump and --version flags are mutually exclusive. The previous version stays live while the new version undergoes security review.Price behavior on updates: Omitting --price preserves the current price. Only pass --price when you want to change it. Use --price 0 to switch a paid skill to free.
Keep installed skills up to date — works for both native and external (e.g., ClawHub) skills:
ap update # Check all installed skills (native + external)ap update my-skill # Update a single skillap update --force # Skip confirmation prompt
For external skills, updates go through the full sandboxed security pipeline (download → hash → scan → install), the same as the initial install.Locally edited skills prompt before overwriting (default No):
# When a newer version is available:my-skill has been locally edited.Update my-skill anyway? Local changes will be overwritten [y/N]:# When already at the latest version:my-skill has been locally edited.Restore my-skill to original? Local changes will be overwritten [y/N]:
Press Enter to skip, or y to overwrite. Use --force to bypass the prompt entirely. When updating all skills, each edited skill is prompted individually. The Installed column in ap search shows Edited (yellow) for modified skills.
Preview a skill’s security status without installing it:
ap scan ontology --source clawhub
This downloads the skill to a temporary sandbox, uploads it for a full security scan, displays the results, and cleans up. Nothing is installed.If the source is omitted, the CLI auto-detects it:
External skills (from ClawHub and other sources) are pinned by content to protect against supply chain attacks. To verify that all installed skills match their recorded pins:
ap verify
This checks each installed skill’s current content hash against the recorded pin and alerts you to any mismatches.
