Climakers Documentation

Climakers documentation is organized for paying customers and operational users.

That means these pages are not just feature summaries. They are structured to answer the questions teams actually have when they evaluate, install, license, configure, and run a commercial CLI tool in a real environment.

How to use this documentation

1. Start with the active product group so you understand the platform boundary and the available tools.
2. Choose the tool that matches the scope of the job: one page or one full documentation estate.
3. Move into the versioned manual for setup, command discovery, workflow design, and repeatable execution.

Active product groups

Atlassian Confluence

The Atlassian Confluence group is the first active Climakers product family. It is built for teams that need to move Confluence knowledge into customer-controlled Markdown for backup, continuity, migration, audit, search, and AI workflows.

• Group overview
• acp2md overview
• acs2md overview
• acp2md vs acs2md

Atlassian Jira

The Atlassian Jira group governs, backs up, and safely operates Jira Cloud Automation from customer-controlled files. It is built for teams whose automation has grown across many projects and now needs inventory, audit, drift review, restore, and safe bulk operations.

• Group overview
• ajat overview

Current commercial tools

acp2md

acp2md stands for Atlassian Confluence Page to Markdown.

Choose acp2md when the requirement is exact page-level work: export one page, retrieve one native payload, analyze one document, or preserve one high-value artifact with clear scope.

Commercial fit: Hobbyist for individual operators and Multiple Seats for shared team use.

• Overview
• Getting Started
• Configuration
• Convert Pages
• Get Pages
• Count & Analyze
• Page Properties
• License
• Utilities

acs2md

acs2md stands for Atlassian Confluence Space to Markdown.

Choose acs2md when the requirement is a full-space export, continuity copy, migration payload, governed documentation estate, or repeatable changed-only synchronization workflow.

Commercial fit: Professional, Small Team, CI/CD Automation, Enterprise, Enterprise Pro, and Enterprise Plus for larger documentation programs and governed automation.

• Overview
• Getting Started
• Configuration
• Convert Spaces
• Get Space Content
• List Spaces
• List Pages
• Space Properties
• Space Permissions
• License
• Utilities

ajat

ajat stands for the Atlassian Jira Automation Tool.

Choose ajat when the requirement is governance, backup, reporting, drift review, restore, or safe bulk operation of a Jira Cloud automation estate — exporting rules to plain JSON, turning them into self-contained HTML reports, and operating them with a plan-first safety model.

Commercial fit: Trial, Solo, Team, CI/CD Automation, and Enterprise for teams managing automation across many projects and tenants.

• Overview
• Getting Started
• Configuration
• Export Rules
• Reports
• Diff & Drift
• Rule Operations
• Import & Promote
• License
• Utilities

Operator utilities

The public manuals now document the operator workflow around the conversion commands, not just the conversion commands themselves.

• Use Getting Started to choose the right tool first and jump into the correct product-specific setup guide.
• Use Support when you need help with installation, licensing, configuration, or runtime issues.
• Use acp2md Utilities for doctor, tree, and completion in the page-level tool.
• Use acs2md Utilities for doctor, tree, and completion in the space-level tool.
• Use ajat Utilities for doctor, tree, support, and completion in the Jira Automation tool.
• Use acp2md vs acs2md when the main question is scope selection rather than syntax.

Recommended entry points