Menu
Convert Markdown text to Zendesk-compatible HTML. Use when user needs to format content for Zendesk tickets, macros, triggers, or automations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when the user asks to "onboard", "analyze this repo", "understand this codebase", "familiarize yourself", "what is this project", or needs to deeply understand a codebase's architecture, patterns, and conventions before starting work.
Analyze the current repo deeply and suggest agentic workflows tailored to its architecture, patterns, and pain points. Use when user calls /aw-planner.
Read a GitHub issue with all comments and linked content to add as working context. Use when the user provides a GitHub issue URL or reference.
Generate a comprehensive manual testing guide for completed work, with note sections for user feedback that the agent reviews afterward. Use when the user wants to manually test changes before shipping.
Review PR comments, validate which are actionable and correct, and propose fixes for valid ones. Use when user wants to address feedback on a pull request.
Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work.
| name | zendesk-markdown |
| description | Convert Markdown text to Zendesk-compatible HTML. Use when user needs to format content for Zendesk tickets, macros, triggers, or automations. |
Convert Markdown-formatted text into HTML that works correctly in Zendesk Support (triggers, automations, dynamic content, email templates, macros).
User provides Markdown text, and you convert it to clean, minified HTML.
| Markdown | HTML |
|---|---|
**bold** | <strong>bold</strong> |
*italic* | <em>italic</em> |
`code` | <code>code</code> |
| Markdown | HTML |
|---|---|
# Heading 1 | <h1>Heading 1</h1> |
## Heading 2 | <h2>Heading 2</h2> |
### Heading 3 | <h3>Heading 3</h3> |
#### Heading 4 | <h4>Heading 4</h4> |
Bulleted list:
* Item one
* Item two
→
<ul><li>Item one</li><li>Item two</li></ul>
Numbered list:
1. Step one
2. Step two
→
<ol><li>Step one</li><li>Step two</li></ol>
Nested lists: Use nested <ul> or <ol> inside <li> elements.
| Markdown | HTML |
|---|---|
[Link text](https://example.com) | <a href="https://example.com">Link text</a> |
 | <img src="https://example.com/image.png" alt="Alt text"> |
Code block:
```
code here
```
→
<pre><code>code here</code></pre>
Blockquote:
> Quoted text
→
<blockquote>Quoted text</blockquote>
Horizontal rule:
---
→
<hr>
Separate paragraphs with blank lines → wrap each in <p> tags.
First paragraph.
Second paragraph.
→
<p>First paragraph.</p><p>Second paragraph.</p>
Minify the HTML: Write on a single line with no unnecessary whitespace. Zendesk renders extra gaps/spaces in emails if HTML isn't minified.
Valid HTML only: Don't include markdown artifacts or partial conversions.
Escape special characters: Convert < to <, > to >, & to & in text content (not in HTML tags).
No outer wrapper: Don't wrap entire output in <div> or <body> unless specifically requested.
Input:
# Welcome
Thank you for contacting us!
We'll help you with:
* Account issues
* Billing questions
* Technical support
Please **reply** to this email or visit [our help center](https://help.example.com).
Output:
<h1>Welcome</h1><p>Thank you for contacting us!</p><p>We'll help you with:</p><ul><li>Account issues</li><li>Billing questions</li><li>Technical support</li></ul><p>Please <strong>reply</strong> to this email or visit <a href="https://help.example.com">our help center</a>.</p>