Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gofastskill.com/llms.txt

Use this file to discover all available pages before exploring further.

​
publish Command

Publish skill packages to a registry API or local folder.

​
Usage

fastskill publish [OPTIONS]

​
Options

OptionDescriptionDefault
--artifacts <PATH>Package file or directory containing ZIP artifacts./artifacts
--target <TARGET>API URL (for example https://registry.example.com) or local folder pathFASTSKILL_API_URL or http://localhost:8080
--waitWait for validation to completetrue
--no-waitDo not wait for validation (overrides --wait)false
--max-wait <SECONDS>Maximum wait time in seconds300

​
Examples

​
Publish to Local fastskill serve

fastskill publish \
  --artifacts ./artifacts \
  --target http://localhost:8080
Local fastskill serve publish endpoints do not require auth headers.

​
Publish to Remote Registry

fastskill auth login --registry https://registry.example.com
fastskill publish \
  --artifacts ./artifacts \
  --target https://registry.example.com
Remote registries may require authentication depending on server configuration.

​
Publish to Local Folder

fastskill publish \
  --artifacts ./artifacts \
  --target ./local-registry

​
Local Publish Identity

When publishing to local fastskill serve, identity is deterministic and anonymous:
  • uploaded_by = "anonymous"
  • publish scope = anonymous
  • returned skill id format = anonymous/<id>

​
API Mode Workflow

  1. Upload package using multipart form data
  2. Package is staged for validation
  3. Check status with /api/registry/publish/status/:job_id
  4. Accepted packages are written to configured outputs

​
Troubleshooting

  • “No artifacts found”: Verify --artifacts path points to a ZIP file or directory containing ZIP files
  • “Publish timeout”: Increase --max-wait or rerun with --no-wait
  • “Registry unavailable”: Check --target URL and network connectivity

​
See Also