explore
Browse skills available in the registry. With no arguments, lists all skills. Use explore show to see details about a specific skill.
Synopsis
Section titled “Synopsis”skillsctl explore [--tag TAG] [--source all|internal|external]skillsctl explore show NAME [--verbose]Subcommands
Section titled “Subcommands”| Subcommand | Description |
|---|---|
show NAME | Show details for a named skill |
| Flag | Default | Description |
|---|---|---|
--tag TAG | Filter by tag. Can be specified multiple times. | |
--source VALUE | all | Filter by source: all, internal, or external. |
--verbose | false | (show only) Print the full skill content. |
Examples
Section titled “Examples”List all skills:
skillsctl exploreNAME VERSION SOURCE DESCRIPTIONgit-conventional 1.2.0 internal Enforce conventional commit messagespython-docstrings 0.4.1 internal Generate Google-style Python docstringsk8s-yaml-lint 0.1.0 external Lint Kubernetes YAML manifestsFilter by tag:
skillsctl explore --tag gitNAME VERSION SOURCE DESCRIPTIONgit-conventional 1.2.0 internal Enforce conventional commit messagesFilter by source:
skillsctl explore --source externalNAME VERSION SOURCE DESCRIPTIONk8s-yaml-lint 0.1.0 external Lint Kubernetes YAML manifestsShow details for a skill:
skillsctl explore show git-conventionalName: git-conventionalDescription: Enforce conventional commit messagesOwner: aliceTags: git, commitsVersion: 1.2.0Installs: 85Source: internal
Versions: 1.2.0 1.1.0 1.0.0Show details including the full skill content:
skillsctl explore show git-conventional --verboseThe output adds a --- Content --- section after the version list with the raw skill markdown.
Common errors
Section titled “Common errors”No skills found.
The registry is empty, or no skills match the given filters. Try skillsctl explore without filters to confirm connectivity.
Error: failed to connect to registry: …
The CLI cannot reach the server. Check skillsctl config get api_url and verify the server is running.