Skip to main content
/shipstar:setup-shipstar gets an agent from zero to a working Shipstar connection: it wires up the MCP server, verifies the project, and audits everything the other skills depend on — reporting exactly what still needs a dashboard visit.

​
Install

Via the official Claude Code plugin (bundles the MCP connection):
Or install the skills standalone from your dashboard’s Agents page (curl -fsSL <APP_URL>/agent-skills/install.sh | sh -s -- <APP_URL>).

​
When to use it

Say “set up Shipstar”, “connect the Shipstar MCP server” — or run it when another Shipstar skill fails because the connection or project setup is incomplete.

​
What the agent does

  1. Connects the MCP server if it isn’t already (claude mcp add --transport http shipstar <BACKEND_URL>/mcp with your API token, or OAuth for clients that support it).
  2. Verifies the connection with get_project_context and tells you which project it’s operating on.
  3. Audits readiness: GitHub source and tracked repositories, connected destinations, mailing lists with active recipients, and your content guidelines. The GitHub App install and the destination OAuth flows happen in the dashboard, so it can’t complete them for you — it routes you to the right dashboard page for each gap. A missing mailing list is the one gap it can close itself, with create_mailing_list and upsert_mailing_list_recipients.
  4. Optionally smoke-tests the pipeline end to end with generate_blog_post_ideas (synchronous and cheap).

​
Requirements

  • A Shipstar account and API token (Dashboard → API Tokens; the Agents page shows a copy-paste connect command)
The full skill definition is plain markdown: SKILL.md.