confluence-crawlerlisted

Crawl an authenticated Confluence space (Atlassian Cloud or on-prem Server/Data Center) by page hierarchy and convert each page to clean Markdown with frontmatter. Handles macros, attachments, internal link rewriting, depth limits, and idempotent re-crawling. Use when the user wants to mirror, export, or ingest Confluence content.
eugenelim/agent-ready-repo · ★ 7 · Code & Development · score 81

Install: claude install-skill eugenelim/agent-ready-repo

# Confluence Crawler Crawl a Confluence space (Cloud or Server/Data Center) and write each page as Markdown with YAML frontmatter. ## Instructions You are a Confluence export agent. The heavy lifting — authentication, REST pagination, macro conversion, link rewriting, idempotency — lives in `scripts/`. Do not re-implement any of that logic; just invoke the scripts with the right arguments and report the result. ### Flavor support The skill works against both: - **Atlassian Cloud** (`*.atlassian.net`) — Basic auth with email + API token from `id.atlassian.com`. Base URL must include `/wiki` (setup adds it automatically). - **Confluence Server / Data Center** — Bearer auth with a Personal Access Token from the user's Confluence profile. Flavor is auto-detected from the base URL. Override via `CONFLUENCE_FLAVOR=cloud|server` if needed. ### Configuration location Credentials are resolved by the build-projected `credentials_shim.load_credentials` through Tier 1 (env) → Tier 2 (OS keyring) → Tier 3 dotfile. The dotfile lives at `~/.agentbundle/credentials.env`. The declared schema is in `references/creds-schema.toml`: | Key | Required | Notes | |---|---|---| | `CONFLUENCE_BASE_URL` | yes | Cloud: `https://<site>.atlassian.net/wiki`. Server: `https://confluence.corp.example.com`. | | `CONFLUENCE_API_TOKEN` | yes | Cloud API token or Server PAT. | | `CONFLUENCE_EMAIL` | Cloud only | Atlassian account email. | | `CONFLUENCE_FLAVOR` | no | `cloud` or `server`. Auto-detected f