confluence

Organize Confluence spaces, pages, and macros using the REST API.

10|7|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/librefang/librefang-registry --skill confluence-librefang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: confluence
Source: https://github.com/librefang/librefang-registry/tree/main/skills/confluence
Command: npx skills add https://github.com/librefang/librefang-registry --skill confluence-librefang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Confluence pages and spaces often become tangled without a clear structure. This skill provides guidance on organizing spaces, designing page hierarchies, using macros effectively, and automating structure with the Confluence REST API to keep documentation discoverable and maintainable.

Core Features & Use Cases

  • Guidance on space and page architecture that keeps hierarchies shallow (3-4 levels) and pages easily navigable.
  • Techniques for consistent labeling, page templates, and macro usage to build scalable knowledge bases.
  • Use Case: A team implements a project wiki with a 3-level hierarchy, labeled pages, and a runbook template to standardize incident documentation.

Quick Start

Create a space home, design a 3-4 level page hierarchy, and tag pages with a consistent labeling scheme.

Frequently Asked Questions about confluence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Confluence spaces to keep page hierarchies navigable?

The best way to organize Confluence pages is to maintain a shallow hierarchy of 3-4 levels and apply a consistent labeling scheme. This approach prevents tangled spaces and keeps documentation easily discoverable for team wikis and runbooks.

Can I automate Confluence page creation and structure using the REST API?

Yes, you can automate Confluence structure by leveraging the REST API and page templates. This enforces hierarchy, labels, and permissions automatically, ensuring consistent documentation architecture across project runbooks and internal wikis.

What is the recommended page hierarchy depth for a Confluence knowledge base?

The recommended page hierarchy depth for a Confluence knowledge base is 3-4 levels. Keeping hierarchies shallow ensures pages remain easily navigable and maintainable, preventing spaces from becoming tangled as documentation scales.

How do I use macros and templates to build a scalable Confluence wiki?

Use Confluence macros and page templates alongside consistent labeling to build a scalable wiki. Standardizing macro usage and templates ensures uniform page architecture, making internal wikis and product documentation highly discoverable.

Does this approach work for standardizing incident runbooks in Confluence?

Yes, this approach works for incident runbooks by applying a standardized runbook template within a 3-level page hierarchy. Using consistent labels and templates standardizes incident documentation and enforces clear permissions across team spaces.