Claude Skills by desplega-ai

Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup

Close a GitHub or GitLab issue with a summary comment

Create a pull request (GitHub) or merge request (GitLab) from the current branch

Implement a GitHub issue or GitLab issue and create a PR/MR

Investigate and triage a Sentry error issue

Respond to a GitHub issue/PR or GitLab issue/MR

Review a task that has been offered to you and decide whether to accept or reject it

Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback

Start the Agent Swarm Leader

Start an Agent Swarm Worker

Effective communication within the agent swarm using internal Slack

Handle the agent personal todos.md file

How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.

Work on a specific task assigned to you in the agent swarm

Serve interactive web content (HTML pages, dashboards, approval flows, static reports, custom Hono apps) to a public URL via localtunnel. Use when the user asks to "create an artifact for X", "host this for me", "make me a tunneled URL", "spin up a web server for X", "publish this report so I can see it", "share this file/page publicly", "expose this dashboard", "give me a live link", or anything that needs a browser-reachable URL pointing at agent-generated content. Wraps the `agent-swarm ar...

Use the swarm KV store (Redis-like, namespaced) for cross-task / cross-session / per-page state. Auto-scoped to your context (Slack thread / PR / Linear issue / agent / page). Use for counters, cursors, page state. Do NOT use for secrets (`swarm_config`), embedded knowledge (`memory`), or files (`agent-fs`).

DB-backed static content (HTML or JSON) served by the API directly. Cheap, versioned, share-able by URL. The lighter-weight cousin of `artifacts` — no PM2, no tunnels, no port allocation, no `services` registry row. > **Capability gate**: the `create_page` MCP tool is only available when the > agent's `CAPABILITIES` env var includes `pages` > (e.g. `CAPABILITIES=core,task-pool,pages`). If the tool is missing from > your MCP list, this is why.