browser-doc-mirror

Mirror browser-authenticated Confluence documents into a provenance-tracked local directory tree.

Updated May 9, 2026

Search Tags:#automation #documentation #confluence #knowledge-management #browser-automation #mirroring

Ready to run

npx skills add https://github.com/yes506/ai-driven-items --skill browser-doc-mirror

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-doc-mirror
Source: https://github.com/yes506/ai-driven-items/tree/main/skills/browser-doc-mirror
Command: npx skills add https://github.com/yes506/ai-driven-items --skill browser-doc-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of accessing and versioning internal documentation (like Confluence or private wikis) that is locked behind SSO and unreachable by standard MCP connectors.

Core Features & Use Cases

Authenticated Mirroring: Uses your existing browser session to fetch documents without needing to handle credentials or bypass security policies.
Provenance Tracking: Maintains a structured, gitignored local mirror with metadata, sync dates, and revision tracking.
Use Case: When your organization blocks Atlassian MCP connectors, use this skill to mirror your team's Confluence architecture pages into a local doc-mirror/ folder for offline reference and AI-assisted analysis.

Quick Start

Run the browser-doc-mirror skill to initialize a new mirror of the current Confluence space into the doc-mirror directory.

Frequently Asked Questions about browser-doc-mirror

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

FAQPage Schema

How do I mirror Confluence pages that are behind SSO into a local git repository?▼

To mirror Confluence pages behind SSO, this Skill uses your existing authenticated browser session to fetch documents into a structured local directory tree without requiring direct API access or credential handling.

Can I sync internal wiki documentation locally when Atlassian MCP connectors are blocked?▼

Yes, when Atlassian MCP connectors are blocked, you can use browser-authenticated mirroring to fetch internal wiki documentation into a git-tracked local cache for offline reference and AI-assisted analysis.

How does incremental synchronization work for mirrored web documents?▼

Incremental synchronization uses manifest-based state tracking and targeted page synchronization to update the local mirror, implementing atomic file operations to ensure data integrity and support crash recovery.

Do I need API credentials to mirror authenticated web docs into a local cache?▼

No, you do not need API credentials to mirror authenticated web docs. The process leverages your active browser session for authentication, bypassing the need to handle credentials or bypass security policies directly.

What is provenance tracking for mirrored browser documents?▼

Provenance tracking maintains a structured local mirror with metadata, sync dates, and revision tracking, ensuring that every mirrored document has a clear history and state record within the gitignored directory tree.