Confluence Expert
Structure Confluence spaces, templates, permissions, and governance so your team wiki matches how you actually ship software.
Overview
Confluence Expert is an agent skill most often used in Build (also Grow, Operate) that designs and manages Atlassian Confluence spaces, templates, permissions, and documentation governance via MCP-backed operations.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill confluence-expertWhat is this skill?
- End-to-end Confluence space lifecycle: create spaces, pages, updates, deletes, and CQL search
- Atlassian MCP operations for pages, versions, labels, and parent-child hierarchies
- Page templates with macros plus documentation taxonomy and layout design
- Space permission structures and content governance workflows
- Jira report embedding and knowledge-base audit guidance
Adoption & trust: 646 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Confluence space is a flat pile of pages with inconsistent templates, weak permissions, and no searchable taxonomy.
Who is it for?
Indie founders or two-person teams standardizing engineering docs, sprint notes, and runbooks in Confluence with MCP automation.
Skip if: Markdown-only docs in the repo when you do not use Atlassian Confluence or lack MCP access.
When should I use this skill?
Use when building or restructuring Confluence spaces, designing hierarchies and permissions, authoring templates, embedding Jira reports, running KB audits, or establishing documentation standards.
What do I get? / Deliverables
You get a structured space hierarchy, standardized templates with macros, governed permissions, and CQL-ready content organization aligned to how your team works.
- Space and page hierarchy design with permission model
- Reusable page templates and macro layouts
- CQL queries and governance standards for ongoing content
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/docs is the canonical shelf because the skill centers on creating and maintaining Confluence knowledge bases, page hierarchies, and templates. Docs subphase fits space design, storage-format pages, macros, and documentation standards—not application runtime code.
Where it fits
Stand up an Engineering space with parent sprint notes and child ADR pages.
Template recurring planning pages with Jira macro embeds for a solo SaaS roadmap.
Apply labels and CQL searches so support articles stay discoverable as FAQs grow.
How it compares
Atlassian-specific documentation skill with MCP recipes—not generic technical writing or Notion setup.
Common Questions / FAQ
Who is confluence-expert for?
Solo builders and small teams using Confluence who want agent-guided space design, templates, permissions, and audits without hiring a dedicated wiki admin.
When should I use confluence-expert?
During Build/docs to launch a team knowledge base; during Grow/content when tightening standards; during Operate/support when auditing runbooks and meeting-note hygiene.
Is confluence-expert safe to install?
It can create, update, and delete wiki content via MCP—review Security Audits on this page, use least-privilege API tokens, and test on a sandbox space first.
SKILL.md
READMESKILL.md - Confluence Expert
# Atlassian Confluence Expert Master-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management. ## Atlassian MCP Integration **Primary Tool**: Confluence MCP Server **Key Operations**: ``` // Create a new space create_space({ key: "TEAM", name: "Engineering Team", description: "Engineering team knowledge base" }) // Create a page under a parent create_page({ spaceKey: "TEAM", title: "Sprint 42 Notes", parentId: "123456", body: "<p>Meeting notes in storage-format HTML</p>" }) // Update an existing page (version must be incremented) update_page({ pageId: "789012", version: 4, body: "<p>Updated content</p>" }) // Delete a page delete_page({ pageId: "789012" }) // Search with CQL search({ cql: 'space = "TEAM" AND label = "meeting-notes" ORDER BY lastModified DESC' }) // Retrieve child pages for hierarchy inspection get_children({ pageId: "123456" }) // Apply a label to a page add_label({ pageId: "789012", label: "archived" }) ``` **Integration Points**: - Create documentation for Senior PM projects - Support Scrum Master with ceremony templates - Link to Jira issues for Jira Expert - Provide templates for Template Creator > **See also**: `MACROS.md` for macro syntax reference, `TEMPLATES.md` for full template library, `PERMISSIONS.md` for permission scheme details. ## Workflows ### Space Creation 1. Determine space type (Team, Project, Knowledge Base, Personal) 2. Create space with clear name and description 3. Set space homepage with overview 4. Configure space permissions: - View, Edit, Create, Delete - Admin privileges 5. Create initial page tree structure 6. Add space shortcuts for navigation 7. **Verify**: Navigate to the space URL and confirm the homepage loads; check that a non-admin test user sees the correct permission level 8. **HANDOFF TO**: Teams for content population ### Page Architecture **Best Practices**: - Use page hierarchy (parent-child relationships) - Maximum 3 levels deep for navigation - Consistent naming conventions - Date-stamp meeting notes **Recommended Structure**: ``` Space Home ├── Overview & Getting Started ├── Team Information │ ├── Team Members & Roles │ ├── Communication Channels │ └── Working Agreements ├── Projects │ ├── Project A │ │ ├── Overview │ │ ├── Requirements │ │ └── Meeting Notes │ └── Project B ├── Processes & Workflows ├── Meeting Notes (Archive) └── Resources & References ``` ### Template Creation 1. Identify repeatable content pattern 2. Create page with structure and placeholders 3. Add instructions in placeholders 4. Format with appropriate macros 5. Save as template 6. Share with space or make global 7. **Verify**: Create a test page from the template and confirm all placeholders render correctly before sharing with the team 8. **USE**: References for advanced template patterns ### Documentation Strategy 1. **Assess** current documentation state 2. **Define** documentation goals and audience 3. **Organize** content taxonomy and structure 4. **Create** templates and guidelines 5. **Migrate** existing documentation 6. **Train** teams on best practices 7. **Monitor** usage and adoption 8. **REPORT TO**: Senior PM on documentation health ### Knowledge Base Management **Article Types**: - How-to guides - Troubleshooting docs - FAQs - Reference documentat