markdown-to-html
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, Commo
Profile →npx skills add github/awesome-copilot --skill markdown-to-html --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Converts Markdown documents to HTML using a mix of libraries and patterns, enabling single-file or batch conversions and interoperability with static site templating systems.
How it works
The skill describes using libraries and tools such as marked.js, pandoc, gomarkdown/markdown, and templating systems (jekyll/jekyll, gohugoio/hugo). It provides examples of converting Markdown to HTML across several flavors and blocks demonstrating input Markdown and corresponding HTML, including code blocks, tables, and math rendering. It includes prerequisites (Node.js for CLI usage, installation commands like npm install -g marked or npm install marked), and configuration guidance for CLI usage (e.g., marked -i input.md -o output.html -c config.json; creating ~/.marked.json with gfm and breaks). It outlines supported CLI options, including input, output, string parsing, config, gfm, breaks, and help. It also provides security warnings about HTML sanitization when using untrusted input and recommends DOMPurify or similar.
When to use it
Use when asked to convert Markdown to HTML, render Markdown, generate HTML from Markdown, build static sites from Markdown, or create templates that convert Markdown to HTML. It applies to single-file conversions, batch processing, and integration with templating systems.
What it can touch
It references using the marked CLI and library, pandoc, gomarkdown, and external tools. It lists commands and file names such as marked, pandoc, gomarkdown/mdtohtml, and related configuration files like ~/.marked.json. It does not specify exact scripts or touchable system paths beyond those commands.
Caveats
Notes that marked does not sanitize output HTML and recommends using a sanitizer like DOMPurify or sanitize-html, and that gomarkdown does not sanitize output HTML with Bluemonday as a recommended sanitizer. It includes security warnings for untrusted input and mentions potential limitations around sanitization and HTML safety. There are no licensing details beyond general references; license is listed as MIT for the skill in the repository metadata.
# Markdown to HTML Conversion Expert skill for converting Markdown documents to HTML using the marked.js library, or writing data conversion scripts; in this case scripts similar to [markedJS/marked](https://github.com/markedjs/marked) repository. For custom scripts knowledge is not confined to `marked.js`, but data conversion methods are utilized from tools like [pandoc](https://github.com/jgm/pandoc) and [gomarkdown/markdown](https://github.com/gomarkdown/markdown) for data conversion; [jekyll/jekyll](https://github.com/jekyll/jekyll) and [gohugoio/hugo](https://github.com/gohugoio/hugo) for templating systems. The conversion script or tool should handle single files, batch conversions, and advanced configurations. ## When to Use This Skill - User asks to "convert markdown to html" or "transform md files" - User wants to "render markdown" as HTML output - User needs to generate HTML documentation from .md files - User is building static sites from Markdown content - User is building template system that converts markdown to html - User is working on a tool, widget, or custom template for an existing templating system - User wants to preview Markdown as rendered HTML ## Converting
- When to Use This Skill
- Converting Markdown to HTML
- Essential Basic Conversions
- Code Block Conversions
- Collapsed Section Conversions
- Mathematical Expression Conversions
- Table Conversions
- Working with [markedJS/marked](references/marked.md)
- Prerequisites
- Quick Conversion Methods
- Step-by-Step Workflows
- CLI Configuration
- Using Config Files
- CLI Options Reference
marked -i input.md -o output.html -c config.json Convert markdown to HTML pandoc input.md -o output.html Convert with standalone document (includes header/footer) pandoc input.md -s -o output.html Explicit format specification pandoc input.md -f markdown -t html -s -o output.html Start pandoc as a filter pandoc Type markdown, then Ctrl-D (Linux/macOS) or Ctrl-Z+Enter (Windows)
What does the markdown-to-html skill do?
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, Commo
How do I install it?
Run `npx skills add github/awesome-copilot --skill markdown-to-html --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.