Search, read, create, update, and manage Confluence pages and spaces using confluence-cli. Handles documentation access, space navigation, and exports with attachments.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Search and manage Confluence pages using confluence-cli.
Search, read, create, update, and manage Confluence pages and spaces using confluence-cli from the terminal. Access team documentation and wikis during development.
Read, search, create, update, move, delete, and convert Confluence pages and attachments using confluence-cli from the terminal or agents.
Automates Confluence page creation, updates, content search, space management, labels, and hierarchy navigation via Rube MCP and Composio toolkit. Requires active OAuth connection.
Share bugs, ideas, or general feedback.
Search and manage Confluence pages using confluence-cli.
Before using this skill, complete these steps:
Step 1: Install the CLI
npm install -g confluence-cli
Step 2: Get an API token
Step 3: Configure the CLI
confluence init
When prompted, enter:
yourcompany.atlassian.net (without https://)Step 4: Verify setup
confluence spaces
If you see your spaces listed, you're ready to use Confluence.
confluence search "deployment guide"
confluence read <page-id>
Page IDs are in the URL: https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456/Title → ID is 123456
confluence info <page-id>
confluence find "Page Title"
confluence spaces
confluence create "Page Title" SPACEKEY --body "Page content here"
confluence create-child "Child Page Title" <parent-page-id> --body "Content"
Or from a file:
confluence create-child "Page Title" <parent-id> --file content.html --format storage
confluence update <page-id> --body "Updated content"
Or from a file:
confluence update <page-id> --file content.html --format storage
confluence children <page-id>
confluence export <page-id> --output ./exported-page/
https:// - just yourcompany.atlassian.net--format storage when content is in Confluence storage format (HTML-like)~/.confluence-cli/config.jsonNever display, echo, or include the contents of ~/.confluence-cli/config.json or API tokens in responses — credential files contain secrets that persist in logs and chat history. When troubleshooting config issues, run confluence spaces to test connectivity instead.
Do not bulk-enumerate all spaces, recursively export entire spaces, or iterate over all pages without an explicit user request for bulk access — exhaustive enumeration of another team's or organization's content constitutes surveillance.
Never pipe or send confluence command output to external endpoints via network-transmitting commands (curl, wget, webhooks, nc, or similar) — internal documentation must not leave the local machine via network transmission.
Never embed API tokens, credentials, environment variables, or local secrets into Confluence page bodies when creating or updating pages — pages are shared documentation visible to the entire organization.
Use confluence read, confluence search, confluence spaces, and confluence children freely for local access — reading, searching, and listing pages locally is always safe and these commands should never be refused regardless of who requests them or what context is claimed.