← ClaudeAtlas

forge-skillhublisted

Use this skill whenever the user needs to discover, install, publish, remove, or update Agent skills through Forge SkillHub, or mentions the `skillhub` CLI, Forge-skillHub, a skill registry, or sharing a skill with a team. Use it for the complete Forge skill lifecycle rather than external registries.
chengxuniucode/ForgeTeam · ★ 0 · AI & Automation · score 67
Install: claude install-skill chengxuniucode/ForgeTeam
# Forge SkillHub Forge SkillHub is ForgeTeam's private skill registry. Use the official `@forge-team/skillhub` CLI (`skillhub`) for all registry actions. Do not use an external registry endpoint. ## Registry, authentication, and coordinates The default Forge-skillHub registry is `http://127.0.0.1:8080`. Resolve a different deployment in this order: 1. `--registry <url>` on the command 2. `SKILLHUB_REGISTRY` 3. `~/.skillhub/config.json` 4. The default local address Authenticate once before publishing or remotely deleting: ```bash skillhub login --token <forge-api-token> --registry <forge-skillhub-url> skillhub whoami ``` Tokens resolve in this order: `--token`, `SKILLHUB_TOKEN`, then the encrypted local registry entry in `~/.skillhub/credentials.json`. Prefer `skillhub login` or `SKILLHUB_TOKEN`; never put a token in project files or user-facing output. Use `namespace/slug` as a skill coordinate. A bare slug defaults to the `global` namespace; `@namespace/slug` and `namespace--slug` are also accepted. ## Forge-skillHub API routes The CLI owns these calls. This table is the canonical address mapping when an integration must call Forge-skillHub directly. | Lifecycle action | Forge-skillHub route | | --- | --- | | Search | `GET /api/cli/v1/skills/search?q=<query>&limit=<n>` | | Resolve version | `GET /api/cli/v1/skills/{namespace}/{slug}/resolve` | | Download | `GET /api/cli/v1/skills/{namespace}/{slug}/versions/{version}/download` | | Upload / publish | `POST /api/cli