> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shipstar.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Add an announcement banner

> Claude Code skill that puts a Shipstar announcement banner at the top of your website — generated from your commits, reviewed with you, embedded once, and scheduled to update itself weekly or monthly.

`/shipstar:add-announcement-banner` has your coding agent put a one-line
announcement bar at the top of your site: the most impactful change of the
period as a headline, one sentence, and a call-to-action, generated from your
commits. Exactly one banner is live per project — every publish replaces it
under the same embed key, so the site is set up once and stays current.

## Install

Via the official Claude Code plugin (bundles the MCP connection):

```
/plugin marketplace add shipstar-ai/shipstar-plugin
/plugin install shipstar@shipstar
```

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 "add a what's-new bar to our homepage", "highlight the new feature at the
top of the site this week", or "put an announcement banner on our site that
updates itself".

## What the agent does

1. **Checks the starting point** — [`get_project_context`](/mcp/project/get-project-context)
   for a connected GitHub source, [`get_banner`](/mcp/banner/get-banner) for
   what is live now, and asks where the banner should click through to and
   whether it should come down on its own.
2. **Generates and reviews** — [`generate_banner`](/mcp/generation/generate-banner)
   (25 credits), then shows you the exact headline, body, and button label
   before anything goes live; edits go through
   [`update_content`](/mcp/lifecycle/update-content).
3. **Publishes on your say-so** — [`publish_content`](/mcp/lifecycle/publish-content)
   makes it the live banner and reports the embed key.
4. **Puts it on the site** — the one-tag embed (`data-type="banner"`, sticks
   to the top, dismissable) or a server-rendered bar from
   [`GET /api/v1/banner`](/api-reference/banner/get-live-banner), where a
   `404` means "no banner, render nothing".
5. **Keeps it fresh** — points you at the dashboard's weekly or monthly
   banner schedule, whose "Link to" and "Take down after" choices apply to
   every run.

## Guardrails

* Never publishes without you seeing the exact text first.
* Never invents a link: with no URL from you, Shipstar resolves one at
  publish (your Changelog page, else the period's changelog) or shows no
  button.