/announcekit

name: announcekit
description: |
  AnnounceKit integration. Manage data, records, and automate workflows. Use when the user wants to interact with AnnounceKit data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

AnnounceKit

AnnounceKit is a changelog and product update platform. It helps SaaS companies announce product updates, collect feedback, and keep users informed.

Official docs: https://developers.announcekit.com/

AnnounceKit Overview

• **AnnounceKit**
• **Product**
• **Story**
• **Category**
• **User**

Use action names and parameters as needed.

Working with AnnounceKit

This skill uses the Membrane CLI to interact with AnnounceKit. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to AnnounceKit

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://announcekit.app/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | | --- | --- | --- | | List Activities | list-activities | List activities for a specific post with pagination | | List Statuses | list-statuses | List all statuses (for roadmap issues) in a project | | Delete Roadmap Issue | delete-roadmap-issue | Delete a roadmap issue | | Update Roadmap Issue | update-roadmap-issue | Update an existing roadmap issue | | Create Roadmap Issue | create-roadmap-issue | Create a new issue on the roadmap | | Get Feedback Counts | get-feedback-counts | Get reaction counts for a specific post | | List Feedbacks | list-feedbacks | List feedbacks for a specific post with pagination | | Get Feed | get-feed | Get details of a specific feed by ID | | List Feeds | list-feeds | List all feeds in a project | | Delete Label | delete-label | Delete a label from a project | | Update Label | update-label | Update an existing label in a project | | Create Label | create-label | Create a new label in a project | | List Labels | list-labels | List all labels in a project | | Delete Post | delete-post | Delete a post from a project | | Update Post | update-post | Update an existing post/announcement | | Create Post | create-post | Create a new post/announcement in a project | | Get Post | get-post | Get details of a specific post by ID | | List Posts | list-posts | List posts in a project with optional filtering and pagination | | Get Project | get-project | Get details of a specific project by ID | | Get Current User | get-current-user | Get the current authenticated user and their active project |

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action r