confluence-reader

Reading Confluence pages recursively involves fetching a root page, traversing its child hierarchy up to a configurable depth, and consolidating all discovered content into a single structured markdown digest for downstream use.

The best way to capture cross-referenced Confluence pages for migration validation is to scan page content for links, recursively ingest them, and track visited pages to avoid loops while building a unified markdown digest.

Yes, you can use Confluence MCP tools to extract page hierarchies for auditing by fetching pages with include_metadata=true and convert_to_markdown=true, identifying parent and child relationships while aggregating content into a structured digest.

Yes, recursive Confluence content ingestion prevents infinite loops by tracking visited pages during traversal, ensuring that parent, child, and cross-referenced pages are safely consolidated into a unified markdown report without duplication.

Traversing deep Confluence page hierarchies for knowledge consolidation is limited by a configurable depth setting, meaning extremely deep structures may require multiple passes even though the Skill captures parents, children, and cross-referenced links into a single markdown blob.