Confluence
Read and write Confluence spaces, pages, attachments, and blog posts through Membrane so agents automate team documentation without hand-rolling Atlassian OAuth.
Overview
Confluence is an agent skill for the Build phase that connects agents to Atlassian Confluence via the Membrane CLI for pages, spaces, and attachments.
Install
npx skills add https://github.com/membranedev/application-skills --skill confluenceWhat is this skill?
- Confluence model: Space → Page → Attachment plus Blog Post entities
- Uses Membrane CLI with automatic credential refresh for Atlassian Cloud
- Document Management category skill with MIT license and Free-tier Membrane support
- npm global install path for @membranehq/cli and membrane login flow
- Official Atlassian Cloud Confluence API alignment via Membrane actions
- Membrane CLI install: npm install -g @membranehq/cli@latest
- Skill metadata version 1.0
Adoption & trust: 1.4k installs on skills.sh; 178 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need your coding agent to manage Confluence docs but do not want to implement and maintain Atlassian Cloud auth and API plumbing yourself.
Who is it for?
Indie builders using Confluence for specs and runbooks who already use or can adopt Membrane for SaaS integrations.
Skip if: Teams on Notion or Git-only docs with no Confluence tenant, or air-gapped environments that cannot use network-backed CLIs.
When should I use this skill?
User wants to interact with Confluence data—spaces, pages, attachments, blog posts—or manage document workflows via Membrane.
What do I get? / Deliverables
You run Membrane-authenticated Confluence actions from the terminal so agents can list, create, and update documentation records in the right spaces.
- Configured Membrane CLI session for Confluence
- Executed Confluence actions against spaces, pages, or attachments
Recommended Skills
Journey fit
Confluence integration is built when wiring the product or agent to external knowledge systems—typically during Build alongside other SaaS connectors. Integrations is the right shelf because auth, CLI install, and Membrane-mediated API calls are the core deliverable, not writing prose docs from scratch.
How it compares
Membrane-backed Confluence connector skill—not a static Markdown template pack or local wiki generator.
Common Questions / FAQ
Who is confluence for?
Solo builders and small teams on Atlassian Cloud who want agents to read and write Confluence content through a managed integration layer.
When should I use confluence?
During Build integrations when syncing specs, publishing agent-generated docs to a space, fetching page context for coding tasks, or automating attachment workflows— and during Grow content/support when updating customer-facing knowledge in Confluence.
Is confluence safe to install?
Review the Security Audits panel on this Prism page; Membrane handles credentials—scope login to the right tenant and least-privilege Confluence access for production spaces.
SKILL.md
READMESKILL.md - Confluence
# Confluence Confluence is a team collaboration and document management tool. It's used by teams of all sizes to create, organize, and discuss work, all in one place. Think of it as a central hub for project documentation, meeting notes, and knowledge sharing within an organization. Official docs: https://developer.atlassian.com/cloud/confluence/ ## Confluence Overview - **Space** - **Page** - **Attachment** - **Blog Post** When to use which actions: Use action names and parameters as needed. ## Working with Confluence This skill uses the Membrane CLI to interact with Confluence. 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: ```bash npm install -g @membranehq/cli@latest ``` ### Authentication ```bash 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: ```bash 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 Confluence Use `membrane connection ensure` to find or create a connection by app URL or domain: ```bash membrane connection ensure "https://www.atlassian.com/software/confluence" --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: ```bash 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