← ClaudeAtlas

agent-adminlisted

Query and manage Shipwright agents via the admin API — cron jobs, env vars, tool permissions, API tokens, and plugins. Use to configure the running agent, manage its schedules, inspect another agent's config, or provision a new agent.
app-vitals/shipwright · ★ 6 · AI & Automation · score 71
Install: claude install-skill app-vitals/shipwright
# Shipwright Agent Admin — Skill Use this skill to configure and manage Shipwright agents via the admin API. Covers cron jobs, env vars, tool permissions, API tokens, and plugins for any agent — including yourself. **Scope boundary:** For delivery pipeline work (planning, code tasks, reviews, deploys) use the task-store, dev-task, review, or deploy skills. This skill is for agent lifecycle management only. --- ## Authentication All calls require a Bearer token: ```bash Authorization: Bearer $SHIPWRIGHT_AGENT_API_KEY ``` Your key and base URL are in the agent env: ```bash echo $SHIPWRIGHT_API_URL # base URL for the admin API echo $SHIPWRIGHT_AGENT_API_KEY # your per-agent API key echo $SHIPWRIGHT_AGENT_ID # your own agent ID ``` Verify the service is reachable before doing anything: ```bash curl -sf "$SHIPWRIGHT_API_URL/health" ``` **Creating new agents** is an admin-only operation — it requires an admin-level key (`SHIPWRIGHT_ADMIN_API_KEYS` on the server side). All other operations work with the per-agent API key. --- ## Your Agent Identity ```bash # Inspect your full config bundle (env vars, crons, tools, plugins) curl -sf -H "Authorization: Bearer $SHIPWRIGHT_AGENT_API_KEY" \ "$SHIPWRIGHT_API_URL/agents/$SHIPWRIGHT_AGENT_ID/config" | jq . ``` ## Finding Other Agents To manage another agent (e.g. resolve a name like "warchild" to an ID), list all agents: ```bash curl -sf -H "Authorization: Bearer $SHIPWRIGHT_AGENT_API_KEY" \ "$SHIPWRIGHT_A