← ClaudeAtlas

awesharelisted

Use when helping users configure or operate aweshare — producer agent setup (backends, offerings, secrets), hub admin (invites, limits, usage), and consumer SDK wiring. 中文触发词:aweshare、共享模型、配置agent、hub管理、consumer接入。
wehuman01/aweshare · ★ 9 · AI & Automation · score 67
Install: claude install-skill wehuman01/aweshare
# aweshare This skill covers **configuring** the aweshare producer and hub so consumers can call shared models. ## Do Not Launch **Never launch the long-running services from this agent** — not `aweshare hub serve`, not `aweshare producer start` (foreground it would block the session; even with `--background`, starting/stopping the shared service is the user's call). The same applies to starting the hub as a container (`docker run` / `docker compose up` of `ghcr.io/wehuman01/aweshare`) — deploying a service is the user's call. If the user wants to run them, give them the commands (see Hub Deployment) or tell them to run them in their own terminal (or as a service/systemd/daemon); a detached producer is inspected with `aweshare producer doctor --status` and stopped with `aweshare producer stop`. You may run these read-only commands: - `aweshare producer config path` - `aweshare producer config show` (secrets redacted) - `aweshare producer doctor` - `aweshare hub list invites [--reveal] [--token]` — the invite ledger: lifecycle pending/used/suspended/revoked/expired; `--reveal` re-shows stored codes, `--token` shows the token each invite minted - `aweshare hub status` — the live dashboard: capacity (producer slots, consumers, offering counts), last-5m health (admission 429s are not metered), admission-rejection pressure when 429s have been throttling requests (the tuning evidence for `limits` and per-offering caps) and the effective consumer defaults; no tables - `aweshare