What problem does it solve? Jira stores every issue body as Atlassian Document Format (ADF), but different clients accept different input formats, and the HTML-to-ADF conversion frequently rejects valid-looking HTML with an opaque INVALID_INPUT error. This Skill routes content through the correct path for each client and pre-validates HTML payloads before any MCP round-trip. ## Core Features & Use Cases - Client-aware routing: Identifies whether the client is acli (ADF), a contentFormat-based tool like createJiraIssue/editJiraIssue (Markdown), or an HTML-based tool like create_jira_issue/update_jira_issue, then applies the correct submission rules for each. - Pre-flight HTML checker: A bundled Node.js script validates rendered HTML against every known INVALID_INPUT trigger class, including disallowed elements, Confluence ac:/ri: constructs, named entities, multi-line pre blocks, and code combined with other inline marks. - Checklist handling: Converts Markdown task-list syntax to plain bullets on Markdown and HTML paths, or to native ADF taskList/taskItem nodes on the acli path. - Recovery protocol: When an unknown failure class slips through, it guides probe-ticket bisection with mcp-probe tagging and records failures to a JSONL log for future checker hardening. - Use Case: You drafted acceptance criteria with - [ ] checkboxes in a planning artefact and need to update a Jira ticket via update_jira_issue. The Skill flattens the checkboxes, renders allowlist-only HTML, runs the checker until it returns ok: true, and submits inline. ## Quick Start Ask the agent to update a Jira ticket description from your Markdown notes, and it will pick the right client path and validate the payload before submitting.
