` | Override page title (defaults to first H1 heading in the markdown) | | `--dry-run` | Preview what would happen without making changes | | `-y, --yes` | Skip confirmation prompts (for CI\/scripts) | ### Configuration Commands ```bash md2cf config # Interactive setup md2cf config set <k> <v> # Set a value (email, token, baseUrl) md2cf config get <key> # Get a value md2cf config list # List all config (token masked) md2cf config reset # Delete all config md2cf config path # Show config file location ``` ### Source Types The `<source>` argument accepts: - **Local file path**: `.\/docs\/guide.md`, `README.md`, `\/absolute\/path\/file.md` - **Local folder path**: `.\/docs\/`, `\/absolute\/path\/to\/folder\/` (automatically synced recursively) - **Remote URL**: `https:\/\/raw.githubusercontent.com\/org\/repo\/main\/docs\/guide.md` ### Folder Sync When the source is a folder, md2cf automatically syncs it recursively: - Mirrors the local folder structure to Confluence - Folders become pages (with default content) - Markdown files become pages - Existing pages are updated, new pages are created - Nested folder structure is preserved as parent-child page relationships ### Title Resolution The page title is determined in this order: 1. `--title` flag value (if provided) 2. First `# H1` heading in the markdown content 3. Filename converted to title case (e.g., `getting-started.md` becomes "Getting Started") ## Examples **Update a page from a local file:** ```bash md2cf .\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` **Update with custom title:** ```bash md2cf .\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 --title "Custom Title" ``` **Create a page in a space root:** ```bash md2cf .\/onboarding.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG --create ``` **Create using short flag:** ```bash md2cf .\/guide.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG -c ``` **Create a child page under an existing page:** ```bash md2cf .\/api-docs.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 --create ``` **Sync from a remote URL:** ```bash md2cf https:\/\/raw.githubusercontent.com\/org\/repo\/main\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` **Sync entire folder recursively:** ```bash md2cf .\/docs\/ https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` This will mirror the folder structure: - `docs\/README.md` → Page "README" (child of page 123456) - `docs\/api\/auth.md` → Page "api" (folder page) → Page "auth" (child of "api") - `docs\/guides\/start.md` → Page "guides" (folder page) → Page "start" (child of "guides") ## Edge Cases - If no URL is provided, the command will fail. - For updates (no `--create` flag), the URL must point to an existing page. - For creates with `--create` flag, the URL can point to either a page (creates as child) or a space (creates in space root). - Remote markdown URLs must be publicly accessible or return content without authentication. - Title defaults to the first H1 heading in the markdown, or the filename if no H1 is found. </article></body></html>

--- name: md2cf description: > Sync markdown files to Confluence pages. Use this skill when asked to publish, sync, or upload markdown content to Confluence. Handles creating new pages, updating existing pages, and nesting pages under parents. Keywords: confluence, wiki, markdown, publish, sync, atlassian, documentation. license: MIT compatibility: Requires md2cf CLI to be installed globally (npm install -g md2cf) and configured (md2cf config). Requires Node.js >= 24. metadata: author: sujeet-pro version: "1.0" --- ## Instructions Use the `md2cf` CLI tool to sync markdown files to Confluence pages. The tool converts Markdown to Atlassian Document Format (ADF) and uses the Confluence REST API v2. ### Prerequisites The user must have md2cf installed and configured before this skill can be used: ```bash npm install -g md2cf md2cf config ``` Configuration requires: Atlassian email, API token (from https:\/\/id.atlassian.com\/manage\/api-tokens), and Confluence base URL. ### Commands The CLI intelligently determines the action based on the URL and flags: - **No `--create` flag**: Updates the page at the URL - **With `--create` flag**: - If URL points to a page → creates a new child page - If URL points to a space → creates a new page in that space #### Update an existing Confluence page (default) ```bash md2cf

``` The URL must be a full Confluence page URL. This is the default mode. #### Create a new page in a space ```bash md2cf

--create # or use the short flag md2cf

-c ``` #### Create a page as child of another page ```bash md2cf

--create ``` ### Options | Option | Description | |--------|-------------| | `-c, --create` | Create a new page (as child if URL is a page, in space if URL is a space) | | `--title ` | Override page title (defaults to first H1 heading in the markdown) | | `--dry-run` | Preview what would happen without making changes | | `-y, --yes` | Skip confirmation prompts (for CI\/scripts) | ### Configuration Commands ```bash md2cf config # Interactive setup md2cf config set <k> <v> # Set a value (email, token, baseUrl) md2cf config get <key> # Get a value md2cf config list # List all config (token masked) md2cf config reset # Delete all config md2cf config path # Show config file location ``` ### Source Types The `<source>` argument accepts: - **Local file path**: `.\/docs\/guide.md`, `README.md`, `\/absolute\/path\/file.md` - **Local folder path**: `.\/docs\/`, `\/absolute\/path\/to\/folder\/` (automatically synced recursively) - **Remote URL**: `https:\/\/raw.githubusercontent.com\/org\/repo\/main\/docs\/guide.md` ### Folder Sync When the source is a folder, md2cf automatically syncs it recursively: - Mirrors the local folder structure to Confluence - Folders become pages (with default content) - Markdown files become pages - Existing pages are updated, new pages are created - Nested folder structure is preserved as parent-child page relationships ### Title Resolution The page title is determined in this order: 1. `--title` flag value (if provided) 2. First `# H1` heading in the markdown content 3. Filename converted to title case (e.g., `getting-started.md` becomes "Getting Started") ## Examples **Update a page from a local file:** ```bash md2cf .\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` **Update with custom title:** ```bash md2cf .\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 --title "Custom Title" ``` **Create a page in a space root:** ```bash md2cf .\/onboarding.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG --create ``` **Create using short flag:** ```bash md2cf .\/guide.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG -c ``` **Create a child page under an existing page:** ```bash md2cf .\/api-docs.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 --create ``` **Sync from a remote URL:** ```bash md2cf https:\/\/raw.githubusercontent.com\/org\/repo\/main\/README.md https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` **Sync entire folder recursively:** ```bash md2cf .\/docs\/ https:\/\/mycompany.atlassian.net\/wiki\/spaces\/ENG\/pages\/123456 ``` This will mirror the folder structure: - `docs\/README.md` → Page "README" (child of page 123456) - `docs\/api\/auth.md` → Page "api" (folder page) → Page "auth" (child of "api") - `docs\/guides\/start.md` → Page "guides" (folder page) → Page "start" (child of "guides") ## Edge Cases - If no URL is provided, the command will fail. - For updates (no `--create` flag), the URL must point to an existing page. - For creates with `--create` flag, the URL can point to either a page (creates as child) or a space (creates in space root). - Remote markdown URLs must be publicly accessible or return content without authentication. - Title defaults to the first H1 heading in the markdown, or the filename if no H1 is found. </article></body></html>