Skip to Content
Tooling

Tooling

Climakers currently exposes one active commercial product group and two live tools inside it.

The tools share a common operator model, but they are optimized for different scopes of work.

Both tools are read-only by design, target Atlassian Confluence Cloud only, and export customer-controlled Markdown or native payloads that can be stored under the customer’s own governance model.

Active product group

Atlassian Confluence

This is the current live product family. It contains the public manuals for acp2md and acs2md.

acp2md

acp2md is the page-level specialist.

Use it when you need exact scope and exact control.

Commercial packaging: Hobbyist for individual operators and Multiple Seats for small teams that need the same focused page workflow on more than one machine.

  • Convert one Confluence page by ID, title, or URL.
  • Retrieve native atlas_doc_format or storage output without conversion.
  • Count nodes and marks before migration or AI ingestion.
  • Inspect page properties and preserve one authoritative document outside Confluence.
  • Discover the right page safely with space list, space pages, and tree --short before exporting.

Best fit:

  • legal and compliance evidence capture
  • support and incident workflows
  • migration engineering for difficult pages
  • curated RAG source documents
  • runbook and procedure retention

acs2md

acs2md is the space-scale export tool.

Use it when the requirement is an estate, not a single document.

Commercial packaging: Professional, Small Team, CI/CD Automation, Enterprise, Enterprise Pro, and Enterprise Plus for governed space-scale documentation programs.

  • Convert a full Confluence space into a Markdown directory tree.
  • Preserve hierarchy and rewrite internal links for portable output.
  • Keep recurring exports efficient with changed-only sync behavior.
  • Inspect spaces, pages, properties, and permissions from the same binary.
  • Track long-running exports and native downloads with progress output on stderr.

Best fit:

  • documentation continuity copies
  • backup and disaster recovery archives
  • static-site or Git migrations
  • large AI and enterprise-search corpora
  • governance and access-review workflows

Shared operating model

Both tools are designed around the same core workflow:

  1. activate the license
  2. configure Confluence access
  3. run doctor
  4. discover the correct scope with space list and space pages
  5. execute the export or retrieval command

Shared platform characteristics

  • customer-controlled Markdown output
  • Confluence Cloud authentication with Atlassian API tokens
  • commercial licensing and local license storage
  • CLI-first execution suitable for local operations, CI, and governed automation
  • native format retrieval for engineering and migration analysis
  • read-only GET-based access to Confluence content and metadata
  • discovery and readiness commands such as doctor, space list, space pages, and tree
  • macOS and Linux released builds; Windows is not supported yet

Support

When operators hit installation problems, licensing issues, configuration errors, connectivity failures, or unexpected command behavior, use the Climakers support workflow instead of guessing from incomplete evidence.

  • Contact support@climakers.com for product errors, operational incidents, and workflow questions.
  • Include the product name, version, platform, sanitized command, and the exact observed error.
  • Never send credentials, API tokens, license keys, session cookies, or confidential customer content.
  • Expect a response as soon as possible; clearer reproduction details usually reduce turnaround time.

Use the full Support page for the complete support process, safe disclosure guidance, and a support email template.

Reserved future product groups

Atlassian Jira

Reserved for future Jira-oriented tooling and workflows.

Google Workspace

Reserved for future Google Workspace-oriented tooling and workflows.

Last updated on