Confluence

**Quick judgment**: This skill is a practical, CLI-based integration for Atlassian Confluence that becomes very useful once the initial setup is done. It is best suited for environments where Confluence is a primary knowledge base and agents need to read and manage documentation programmatically. **What it does well** - Wraps `confluence-cli` to support: searching pages, reading content, getting page info, finding by title, listing spaces, creating and updating pages (including child pages), listing children, and exporting pages with attachments. - One-time configuration (domain, email, API token) then persists in `~/.confluence-cli/config.json`, enabling repeated automated calls. - Supports both inline content and file-based operations with `--format storage`, which is important for preserving Confluence formatting. **Main risks / limitations** - **Destructive potential**: `create`, `create-child`, and `update` can modify or overwrite important pages if misused or given incorrect IDs/titles. Agents must be constrained to safe spaces or patterns. - **Access scope**: The skill inherits all permissions of the configured Atlassian account; if that account has broad Confluence access, an agent could read or export sensitive internal documents. - **Setup dependency**: Requires Node.js, global `confluence-cli` install, and manual `confluence init` with API token. If this is not correctly performed, the skill will fail at runtime. - **Reliance on external service**: Availability and performance depend on Atlassian’s API and network conditions. **Recommended scenarios** - Internal tooling agents that need to **search and read Confluence docs** (e.g., troubleshooting guides, deployment instructions, onboarding materials) to answer user questions. - Documentation automation workflows that **create or update Confluence pages** from code, logs, or other systems, where write access is intentionally desired and controlled. - Knowledge management assistants that build **content indexes or navigation trees** by listing spaces and child pages, or that **export pages and attachments** for backup or downstream processing. - Environments where security controls and account permissions are already well-managed, and the risk of broad Confluence access by an automated agent is acceptable and monitored.