` | +| `--help` | Show all options | + +### Security Warning + +⚠️ **Marked does NOT sanitize output HTML.** For untrusted input, use a sanitizer: + +```javascript +import { marked } from 'marked'; +import DOMPurify from 'dompurify'; + +const unsafeHtml = marked.parse(untrustedMarkdown); +const safeHtml = DOMPurify.sanitize(unsafeHtml); +``` + +Recommended sanitizers: + +- [DOMPurify](https://github.com/cure53/DOMPurify) (recommended) +- [sanitize-html](https://github.com/apostrophecms/sanitize-html) +- [js-xss](https://github.com/leizongmin/js-xss) + +### Supported Markdown Flavors + +| Flavor | Support | +|--------|---------| +| Original Markdown | 100% | +| CommonMark 0.31 | 98% | +| GitHub Flavored Markdown | 97% | + +### Troubleshooting + +| Issue | Solution | +|-------|----------| +| Special characters at file start | Strip zero-width chars: `content.replace(/^[\u200B\u200C\u200D\uFEFF]/,"")` | +| Code blocks not highlighting | Add a syntax highlighter like highlight.js | +| Tables not rendering | Ensure `gfm: true` option is set | +| Line breaks ignored | Set `breaks: true` in options | +| XSS vulnerability concerns | Use DOMPurify to sanitize output | + +## Working with [`pandoc`](references/pandoc.md) + +### Prerequisites + +- Pandoc installed (download from
Hello pandoc!
+``` + +#### Method 3: Format Conversion + +```bash +# HTML to Markdown +pandoc -f html -t markdown input.html -o output.md + +# Markdown to LaTeX +pandoc input.md -s -o output.tex + +# Markdown to PDF (requires LaTeX) +pandoc input.md -s -o output.pdf + +# Markdown to Word +pandoc input.md -s -o output.docx +``` + +### CLI Configuration + +| Option | Description | +|--------|-------------| +| `-f, --fromBasic writing and formatting syntax
+``` + +```md +## Headings +``` + +```html +Headings
+``` + +```md +### A third-level heading +``` + +```html +A third-level heading
+``` + +### Markdown + +```md +Heading 2 +--- +``` + +### Parsed HTML + +```html +Heading 2
+``` + +--- + +## Paragraphs + +### Markdown + +```md +Create sophisticated formatting for your prose and code on GitHub with simple syntax. +``` + +### Parsed HTML + +```html +Create sophisticated formatting for your prose and code on GitHub with simple syntax.
+``` + +--- + +## Inline Formatting + +### Bold + +```md +**This is bold text** +``` + +```html +This is bold text +``` + +--- + +### Italic + +```md +_This text is italicized_ +``` + +```html +This text is italicized +``` + +--- + +### Bold + Italic + +```md +***All this text is important*** +``` + +```html +All this text is important +``` + +--- + +### Strikethrough (GFM) + +```md +~~This was mistaken text~~ +``` + +```html +This is a subscript text
+``` + +```md +This is a superscript text +``` + +```html +This is a superscript text
+``` + +--- + +## Blockquotes + +### Markdown + +```md +> Text that is a quote +``` + +### Parsed HTML + +```html +++``` + +--- + +### GitHub Alert (NOTE) + +```md +> [!NOTE] +> Useful information. +``` + +```html +Text that is a quote
+
++``` + +> ⚠️ The `markdown-alert-*` classes are GitHub-specific, not standard Markdown. + +--- + +## Inline Code + +```md +Use `git status` to list files. +``` + +```html +Note
+Useful information.
+
Use git status to list files.
+git status
+git add
+| Style | +Syntax | +
|---|---|
| Bold | ++ |
+```
+
+---
+
+## Lists
+
+### Unordered List
+
+```md
+- George Washington
+- John Adams
+```
+
+```html
+-
+
- George Washington +
- John Adams +
-
+
- James Madison +
- James Monroe +
-
+
-
+ First item
+
-
+
- Nested item +
+
-
+
- + Done + +
- + Pending + +
+ Here is a footnote + + 1 + . +
+ +-
+
-
+
My reference.
+
+
*not italic*
+``` + +--- + +## Emoji + +```md +:+1: +``` + +```html +\`#RRGGBB\` | \`#0969DA\` |  |
+| RGB | \`rgb(R,G,B)\` | \`rgb(9, 105, 218)\` |  |
+| HSL | \`hsl(H,S,L)\` | \`hsl(212, 92%, 45%)\` |  |
+
+> \[!NOTE]
+>
+> * A supported color model cannot have any leading or trailing spaces within the backticks.
+> * The visualization of the color is only supported in issues, pull requests, and discussions.
+
+## Links
+
+You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut Command+K to create a link. When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.
+
+You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut Command+V. If you'd like to replace the text with the link, use the keyboard shortcut Command+Shift+V.
+
+`This site was built using [GitHub Pages](https://pages.github.com/).`
+
+
+
+> \[!NOTE]
+> GitHub automatically creates links when valid URLs are written in a comment. For more information, see [Autolinked references and URLs](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls).
+
+## Section links
+
+You can link directly to any section that has a heading. To view the automatically generated anchor in a rendered file, hover over the section heading to expose the icon and click the icon to display the anchor in your browser.
+
+
+
+If you need to determine the anchor for a heading in a file you are editing, you can use the following basic rules:
+
+* Letters are converted to lower-case.
+* Spaces are replaced by hyphens (`-`). Any other whitespace or punctuation characters are removed.
+* Leading and trailing whitespace are removed.
+* Markup formatting is removed, leaving only the contents (for example, `_italics_` becomes `italics`).
+* If the automatically generated anchor for a heading is identical to an earlier anchor in the same document, a unique identifier is generated by appending a hyphen and an auto-incrementing integer.
+
+For more detailed information on the requirements of URI fragments, see [RFC 3986: Uniform Resource Identifier (URI): Generic Syntax, Section 3.5](https://www.rfc-editor.org/rfc/rfc3986#section-3.5).
+
+The code block below demonstrates the basic rules used to generate anchors from headings in rendered content.
+
+```markdown
+# Example headings
+
+## Sample Section
+
+## This'll be a _Helpful_ Section About the Greek Letter Θ!
+A heading containing characters not allowed in fragments, UTF-8 characters, two consecutive spaces between the first and second words, and formatting.
+
+## This heading is not unique in the file
+
+TEXT 1
+
+## This heading is not unique in the file
+
+TEXT 2
+
+# Links to the example headings above
+
+Link to the sample section: [Link Text](#sample-section).
+
+Link to the helpful section: [Link Text](#thisll-be-a-helpful-section-about-the-greek-letter-Θ).
+
+Link to the first non-unique section: [Link Text](#this-heading-is-not-unique-in-the-file).
+
+Link to the second non-unique section: [Link Text](#this-heading-is-not-unique-in-the-file-1).
+```
+
+> \[!NOTE]
+> If you edit a heading, or if you change the order of headings with "identical" anchors, you will also need to update any links to those headings as the anchors will change.
+
+## Relative links
+
+You can define relative links and image paths in your rendered files to help readers navigate to other files in your repository.
+
+A relative link is a link that is relative to the current file. For example, if you have a README file in root of your repository, and you have another file in *docs/CONTRIBUTING.md*, the relative link to *CONTRIBUTING.md* in your README might look like this:
+
+```text
+[Contribution guidelines for this project](docs/CONTRIBUTING.md)
+```
+
+GitHub will automatically transform your relative link or image path based on whatever branch you're currently on, so that the link or path always works. The path of the link will be relative to the current file. Links starting with `/` will be relative to the repository root. You can use all relative link operands, such as `./` and `../`.
+
+Your link text should be on a single line. The example below will not work.
+
+```markdown
+[Contribution
+guidelines for this project](docs/CONTRIBUTING.md)
+```
+
+Relative links are easier for users who clone your repository. Absolute links may not work in clones of your repository - we recommend using relative links to refer to other files within your repository.
+
+## Custom anchors
+
+You can use standard HTML anchor tags (``) to create navigation anchor points for any location in the document. To avoid ambiguous references, use a unique naming scheme for anchor tags, such as adding a prefix to the `name` attribute value.
+
+> \[!NOTE]
+> Custom anchors will not be included in the document outline/Table of Contents.
+
+You can link to a custom anchor using the value of the `name` attribute you gave the anchor. The syntax is exactly the same as when you link to an anchor that is automatically generated for a heading.
+
+For example:
+
+```markdown
+# Section Heading
+
+Some body text of this section.
+
+
+Some text I want to provide a direct link to, but which doesn't have its own heading.
+
+(… more content…)
+
+[A link to that custom anchor](#my-custom-anchor-point)
+```
+
+> \[!TIP]
+> Custom anchors are not considered by the automatic naming and numbering behavior of automatic heading links.
+
+## Line breaks
+
+If you're writing in issues, pull requests, or discussions in a repository, GitHub will render a line break automatically:
+
+```markdown
+This example
+Will span two lines
+```
+
+However, if you are writing in an .md file, the example above would render on one line without a line break. To create a line break in an .md file, you will need to include one of the following:
+
+* Include two spaces at the end of the first line.
+ + This example + Will span two lines ++ +* Include a backslash at the end of the first line. + + ```markdown + This example\ + Will span two lines + ``` + +* Include an HTML single line break tag at the end of the first line. + + ```markdown + This example
+ Will span two lines + ``` + +If you leave a blank line between two lines, both .md files and Markdown in issues, pull requests, and discussions will render the two lines separated by the blank line: + +```markdown +This example + +Will have a blank line separating both lines +``` + +## Images + +You can display an image by adding ! and wrapping the alt text in `[ ]`. Alt text is a short text equivalent of the information in the image. Then, wrap the link for the image in parentheses `()`. + +`` + + + +GitHub supports embedding images into your issues, pull requests, discussions, comments and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see [Uploading assets](#uploading-assets). + +> \[!NOTE] +> When you want to display an image that is in your repository, use relative links instead of absolute links. + +Here are some examples for using relative links to display an image. + +| Context | Relative Link | +| ----------------------------------------------------------- | ---------------------------------------------------------------------- | +| In a `.md` file on the same branch | `/assets/images/electrocat.png` | +| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | +| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png?raw=true` | +| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | +| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | + +> \[!NOTE] +> The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository that contains these images. + +For more information, see [Relative Links](#relative-links). + +### The Picture element + +The `
+function test() {
+ console.log("notice the blank line before this function?");
+}
+++``` + +--- + +## Showing Backticks Inside Code Blocks + +### Markdown + +`````md + ```` + ``` + Look! You can see my backticks. + ``` + ```` +````` + +### Parsed HTML + +```html +Tip
+To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
+
+ ```
+
+ Look! You can see my backticks.
+
+ ```
+
+require 'redcarpet'
+markdown = Redcarpet.new("Hello World!")
+puts markdown.to_html
+` tag |
+| -------------- | ------------------------------ |
+| ```js | `` |
+| ```html | `` |
+| ```md | `` |
+| ``` (no lang) | `` |
+
+---
+
+## HTML Comments (Ignored by Renderer)
+
+```md
+
+```
+
+```html
+
+```
+
+---
+
+## Links
+
+```md
+[About writing and formatting on GitHub](https://docs.github.com/...)
+```
+
+```html
+About writing and formatting on GitHub
+```
+
+---
+
+## Lists
+
+```md
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
+```
+
+```html
+
+ -
+ GitHub Flavored Markdown Spec
+
+
+```
+
+---
+
+## Diagrams (Conceptual Parsing)
+
+### Markdown
+
+````md
+```mermaid
+graph TD
+ A --> B
+```
+````
+
+### Parsed HTML
+
+```html
+
+graph TD
+ A --> B
+
+```
+
+## Closing Notes
+
+* No `language-*` class appears here because **no language identifier** was provided.
+* The inner triple backticks are preserved **as literal text** inside ``.
diff --git a/skills/markdown-to-html/references/code-blocks.md b/skills/markdown-to-html/references/code-blocks.md
new file mode 100644
index 00000000..0f9ef2bd
--- /dev/null
+++ b/skills/markdown-to-html/references/code-blocks.md
@@ -0,0 +1,70 @@
+# Creating and highlighting code blocks
+
+Share samples of code with fenced code blocks and enabling syntax highlighting.
+
+## Fenced code blocks
+
+You can create fenced code blocks by placing triple backticks \`\`\` before and after the code block. We recommend placing a blank line before and after code blocks to make the raw formatting easier to read.
+
+````text
+```
+function test() {
+ console.log("notice the blank line before this function?");
+}
+```
+````
+
+
+
+> \[!TIP]
+> To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
+
+To display triple backticks in a fenced code block, wrap them inside quadruple backticks.
+
+`````text
+````
+```
+Look! You can see my backticks.
+```
+````
+`````
+
+
+
+If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on GitHub. For more information, see [About writing and formatting on GitHub](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor).
+
+## Syntax highlighting
+
+
+
+You can add an optional language identifier to enable syntax highlighting in your fenced code block.
+
+Syntax highlighting changes the color and style of source code to make it easier to read.
+
+For example, to syntax highlight Ruby code:
+
+````text
+```ruby
+require 'redcarpet'
+markdown = Redcarpet.new("Hello World!")
+puts markdown.to_html
+```
+````
+
+This will display the code block with syntax highlighting:
+
+
+
+> \[!TIP]
+> When you create a fenced code block that you also want to have syntax highlighting on a GitHub Pages site, use lower-case language identifiers. For more information, see [About GitHub Pages and Jekyll](https://docs.github.com/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll#syntax-highlighting).
+
+We use [Linguist](https://github.com/github-linguist/linguist) to perform language detection and to select [third-party grammars](https://github.com/github-linguist/linguist/blob/main/vendor/README.md) for syntax highlighting. You can find out which keywords are valid in [the languages YAML file](https://github.com/github-linguist/linguist/blob/main/lib/linguist/languages.yml).
+
+## Creating diagrams
+
+You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, GeoJSON, TopoJSON, and ASCII STL syntax. For more information, see [Creating diagrams](https://docs.github.com/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams).
+
+## Further reading
+
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
+* [Basic writing and formatting syntax](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
\ No newline at end of file
diff --git a/skills/markdown-to-html/references/collapsed-sections-to-html.md b/skills/markdown-to-html/references/collapsed-sections-to-html.md
new file mode 100644
index 00000000..2689c6bb
--- /dev/null
+++ b/skills/markdown-to-html/references/collapsed-sections-to-html.md
@@ -0,0 +1,136 @@
+# Collapsed Sections to HTML
+
+## `` Block (Raw HTML in Markdown)
+
+### Markdown
+
+````md
+
+
+Tips for collapsed sections
+
+### You can add a header
+
+You can add text within a collapsed section.
+
+You can add an image or a code block, too.
+
+ ```ruby
+ puts "Hello World"
+ ```
+
+
+````
+
+---
+
+### Parsed HTML
+
+```html
+
+ Tips for collapsed sections
+
+ You can add a header
+
+ You can add text within a collapsed section.
+
+ You can add an image or a code block, too.
+
+
+puts "Hello World"
+
+
+```
+
+#### Notes:
+
+* Markdown **inside ``** is still parsed normally.
+* Syntax highlighting is preserved via `class="language-ruby"`.
+
+---
+
+## Open by Default (`open` attribute)
+
+### Markdown
+
+````md
+
+
+Tips for collapsed sections
+
+### You can add a header
+
+You can add text within a collapsed section.
+
+You can add an image or a code block, too.
+
+ ```ruby
+ puts "Hello World"
+ ```
+
+
+````
+
+### Parsed HTML
+
+```html
+
+ Tips for collapsed sections
+
+ You can add a header
+
+ You can add text within a collapsed section.
+
+ You can add an image or a code block, too.
+
+
+puts "Hello World"
+
+
+```
+
+## Key Rules
+
+* `` and `` are **raw HTML**, not Markdown syntax
+* Markdown inside `` **is still parsed**
+* Syntax highlighting works normally inside collapsed sections
+* Use `` as the **clickable label**
+
+## Paragraphs with Inline HTML & SVG
+
+### Markdown
+
+```md
+You can streamline your Markdown by creating a collapsed section with the `` tag.
+```
+
+### Parsed HTML
+
+```html
+
+ You can streamline your Markdown by creating a collapsed section with the <details> tag.
+
+```
+
+---
+
+### Markdown (inline SVG preserved)
+
+```md
+Any Markdown within the `` block will be collapsed until the reader clicks to expand the details.
+```
+
+### Parsed HTML
+
+```html
+
+ Any Markdown within the <details> block will be collapsed until the reader clicks
+
+ to expand the details.
+
+```
diff --git a/skills/markdown-to-html/references/collapsed-sections.md b/skills/markdown-to-html/references/collapsed-sections.md
new file mode 100644
index 00000000..11309e4b
--- /dev/null
+++ b/skills/markdown-to-html/references/collapsed-sections.md
@@ -0,0 +1,48 @@
+# Organizing information with collapsed sections
+
+You can streamline your Markdown by creating a collapsed section with the `` tag.
+
+## Creating a collapsed section
+
+You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
+
+Any Markdown within the `` block will be collapsed until the reader clicks to expand the details.
+
+Within the `` block, use the `` tag to let readers know what is inside. The label appears to the right of .
+
+````markdown
+
+
+Tips for collapsed sections
+
+### You can add a header
+
+You can add text within a collapsed section.
+
+You can add an image or a code block, too.
+
+```ruby
+ puts "Hello World"
+```
+
+
+````
+
+The Markdown inside the `` label will be collapsed by default:
+
+
+
+After a reader clicks , the details are expanded:
+
+
+
+Optionally, to make the section display as open by default, add the `open` attribute to the `` tag:
+
+```html
+
+```
+
+## Further reading
+
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
+* [Basic writing and formatting syntax](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
\ No newline at end of file
diff --git a/skills/markdown-to-html/references/gomarkdown.md b/skills/markdown-to-html/references/gomarkdown.md
new file mode 100644
index 00000000..21abf824
--- /dev/null
+++ b/skills/markdown-to-html/references/gomarkdown.md
@@ -0,0 +1,253 @@
+# gomarkdown/markdown Reference
+
+Go library for parsing Markdown and rendering HTML. Fast, extensible, and thread-safe.
+
+## Installation
+
+```bash
+# Add to your Go project
+go get github.com/gomarkdown/markdown
+
+# Install CLI tool
+go install github.com/gomarkdown/mdtohtml@latest
+```
+
+## Basic Usage
+
+### Simple Conversion
+
+```go
+package main
+
+import (
+ "fmt"
+ "github.com/gomarkdown/markdown"
+)
+
+func main() {
+ md := []byte("# Hello World\n\nThis is **bold** text.")
+ html := markdown.ToHTML(md, nil, nil)
+ fmt.Println(string(html))
+}
+```
+
+### Using CLI Tool
+
+```bash
+# Convert file to HTML
+mdtohtml input.md output.html
+
+# Output to stdout
+mdtohtml input.md
+```
+
+## Parser Configuration
+
+### Common Extensions
+
+```go
+import (
+ "github.com/gomarkdown/markdown"
+ "github.com/gomarkdown/markdown/parser"
+)
+
+// Create parser with extensions
+extensions := parser.CommonExtensions | parser.AutoHeadingIDs
+p := parser.NewWithExtensions(extensions)
+
+// Parse markdown
+doc := p.Parse(md)
+```
+
+### Available Parser Extensions
+
+| Extension | Description |
+|-----------|-------------|
+| `parser.CommonExtensions` | Tables, fenced code, autolinks, strikethrough |
+| `parser.Tables` | Pipe tables support |
+| `parser.FencedCode` | Fenced code blocks with language |
+| `parser.Autolink` | Auto-detect URLs |
+| `parser.Strikethrough` | ~~strikethrough~~ text |
+| `parser.SpaceHeadings` | Require space after # in headings |
+| `parser.HeadingIDs` | Custom heading IDs {#id} |
+| `parser.AutoHeadingIDs` | Auto-generate heading IDs |
+| `parser.Footnotes` | Footnote support |
+| `parser.NoEmptyLineBeforeBlock` | No blank line required before blocks |
+| `parser.HardLineBreak` | Newlines become `
` |
+| `parser.MathJax` | MathJax support |
+| `parser.SuperSubscript` | Super^script^ and sub~script~ |
+| `parser.Mmark` | Mmark syntax support |
+
+## HTML Renderer Configuration
+
+### Common Flags
+
+```go
+import (
+ "github.com/gomarkdown/markdown"
+ "github.com/gomarkdown/markdown/html"
+ "github.com/gomarkdown/markdown/parser"
+)
+
+// Parser
+p := parser.NewWithExtensions(parser.CommonExtensions)
+
+// Renderer
+htmlFlags := html.CommonFlags | html.HrefTargetBlank
+opts := html.RendererOptions{
+ Flags: htmlFlags,
+ Title: "My Document",
+ CSS: "style.css",
+}
+renderer := html.NewRenderer(opts)
+
+// Convert
+html := markdown.ToHTML(md, p, renderer)
+```
+
+### Available HTML Flags
+
+| Flag | Description |
+|------|-------------|
+| `html.CommonFlags` | Common sensible defaults |
+| `html.HrefTargetBlank` | Add `target="_blank"` to links |
+| `html.CompletePage` | Generate complete HTML document |
+| `html.UseXHTML` | Use XHTML output |
+| `html.FootnoteReturnLinks` | Add return links in footnotes |
+| `html.FootnoteNoHRTag` | No `
` before footnotes |
+| `html.Smartypants` | Smart punctuation |
+| `html.SmartypantsFractions` | Smart fractions (1/2 → ½) |
+| `html.SmartypantsDashes` | Smart dashes (-- → –) |
+| `html.SmartypantsLatexDashes` | LaTeX-style dashes |
+
+### Renderer Options
+
+```go
+opts := html.RendererOptions{
+ Flags: htmlFlags,
+ Title: "Document Title",
+ CSS: "path/to/style.css",
+ Icon: "favicon.ico",
+ Head: []byte(""),
+ RenderNodeHook: customRenderHook,
+}
+```
+
+## Complete Example
+
+```go
+package main
+
+import (
+ "os"
+ "github.com/gomarkdown/markdown"
+ "github.com/gomarkdown/markdown/html"
+ "github.com/gomarkdown/markdown/parser"
+)
+
+func mdToHTML(md []byte) []byte {
+ // Parser with extensions
+ extensions := parser.CommonExtensions |
+ parser.AutoHeadingIDs |
+ parser.NoEmptyLineBeforeBlock
+ p := parser.NewWithExtensions(extensions)
+ doc := p.Parse(md)
+
+ // HTML renderer with options
+ htmlFlags := html.CommonFlags | html.HrefTargetBlank
+ opts := html.RendererOptions{Flags: htmlFlags}
+ renderer := html.NewRenderer(opts)
+
+ return markdown.Render(doc, renderer)
+}
+
+func main() {
+ md, _ := os.ReadFile("input.md")
+ html := mdToHTML(md)
+ os.WriteFile("output.html", html, 0644)
+}
+```
+
+## Security: Sanitizing Output
+
+**Important:** gomarkdown does not sanitize HTML output. Use Bluemonday for untrusted input:
+
+```go
+import (
+ "github.com/microcosm-cc/bluemonday"
+ "github.com/gomarkdown/markdown"
+)
+
+// Convert markdown to potentially unsafe HTML
+unsafeHTML := markdown.ToHTML(md, nil, nil)
+
+// Sanitize using Bluemonday
+p := bluemonday.UGCPolicy()
+safeHTML := p.SanitizeBytes(unsafeHTML)
+```
+
+### Bluemonday Policies
+
+| Policy | Description |
+|--------|-------------|
+| `UGCPolicy()` | User-generated content (most common) |
+| `StrictPolicy()` | Strip all HTML |
+| `StripTagsPolicy()` | Strip tags, keep text |
+| `NewPolicy()` | Build custom policy |
+
+## Working with AST
+
+### Accessing the AST
+
+```go
+import (
+ "github.com/gomarkdown/markdown/ast"
+ "github.com/gomarkdown/markdown/parser"
+)
+
+p := parser.NewWithExtensions(parser.CommonExtensions)
+doc := p.Parse(md)
+
+// Walk the AST
+ast.WalkFunc(doc, func(node ast.Node, entering bool) ast.WalkStatus {
+ if heading, ok := node.(*ast.Heading); ok && entering {
+ fmt.Printf("Found heading level %d\n", heading.Level)
+ }
+ return ast.GoToNext
+})
+```
+
+### Custom Renderer
+
+```go
+type MyRenderer struct {
+ *html.Renderer
+}
+
+func (r *MyRenderer) RenderNode(w io.Writer, node ast.Node, entering bool) ast.WalkStatus {
+ // Custom rendering logic
+ if heading, ok := node.(*ast.Heading); ok && entering {
+ fmt.Fprintf(w, "", heading.Level)
+ return ast.GoToNext
+ }
+ return r.Renderer.RenderNode(w, node, entering)
+}
+```
+
+## Handling Newlines
+
+Windows and Mac newlines need normalization:
+
+```go
+// Normalize newlines before parsing
+normalized := parser.NormalizeNewlines(input)
+html := markdown.ToHTML(normalized, nil, nil)
+```
+
+## Resources
+
+- [Package Documentation](https://pkg.go.dev/github.com/gomarkdown/markdown)
+- [Advanced Processing Guide](https://blog.kowalczyk.info/article/cxn3/advanced-markdown-processing-in-go.html)
+- [GitHub Repository](https://github.com/gomarkdown/markdown)
+- [CLI Tool](https://github.com/gomarkdown/mdtohtml)
+- [Bluemonday Sanitizer](https://github.com/microcosm-cc/bluemonday)
diff --git a/skills/markdown-to-html/references/hugo.md b/skills/markdown-to-html/references/hugo.md
new file mode 100644
index 00000000..07904508
--- /dev/null
+++ b/skills/markdown-to-html/references/hugo.md
@@ -0,0 +1,394 @@
+# Hugo Reference
+
+Hugo is the world's fastest static site generator. It builds sites in milliseconds and supports advanced content management features.
+
+## Installation
+
+### Windows
+
+```powershell
+# Using Chocolatey
+choco install hugo-extended
+
+# Using Scoop
+scoop install hugo-extended
+
+# Using Winget
+winget install Hugo.Hugo.Extended
+```
+
+### macOS
+
+```bash
+# Using Homebrew
+brew install hugo
+```
+
+### Linux
+
+```bash
+# Debian/Ubuntu (snap)
+snap install hugo --channel=extended
+
+# Using package manager (may not be latest)
+sudo apt-get install hugo
+
+# Or download from https://gohugo.io/installation/
+```
+
+## Quick Start
+
+### Create New Site
+
+```bash
+# Create site
+hugo new site mysite
+cd mysite
+
+# Initialize git and add theme
+git init
+git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke themes/ananke
+echo "theme = 'ananke'" >> hugo.toml
+
+# Create first post
+hugo new content posts/my-first-post.md
+
+# Start development server
+hugo server -D
+```
+
+### Directory Structure
+
+```
+mysite/
+├── archetypes/ # Content templates
+│ └── default.md
+├── assets/ # Assets to process (SCSS, JS)
+├── content/ # Markdown content
+│ └── posts/
+├── data/ # Data files (YAML, JSON, TOML)
+├── i18n/ # Internationalization
+├── layouts/ # Templates
+│ ├── _default/
+│ ├── partials/
+│ └── shortcodes/
+├── static/ # Static files (copied as-is)
+├── themes/ # Themes
+└── hugo.toml # Configuration
+```
+
+## CLI Commands
+
+| Command | Description |
+|---------|-------------|
+| `hugo new site ` | Create new site |
+| `hugo new content ` | Create content file |
+| `hugo` | Build to `public/` |
+| `hugo server` | Start dev server |
+| `hugo mod init` | Initialize Hugo Modules |
+| `hugo mod tidy` | Clean up modules |
+
+### Build Options
+
+```bash
+# Basic build
+hugo
+
+# Build with minification
+hugo --minify
+
+# Build with drafts
+hugo -D
+
+# Build for specific environment
+hugo --environment production
+
+# Build to custom directory
+hugo -d ./dist
+
+# Verbose output
+hugo -v
+```
+
+### Server Options
+
+```bash
+# Start with drafts
+hugo server -D
+
+# Bind to all interfaces
+hugo server --bind 0.0.0.0
+
+# Custom port
+hugo server --port 8080
+
+# Disable live reload
+hugo server --disableLiveReload
+
+# Navigate to changed content
+hugo server --navigateToChanged
+```
+
+## Configuration (hugo.toml)
+
+```toml
+# Basic settings
+baseURL = 'https://example.com/'
+languageCode = 'en-us'
+title = 'My Hugo Site'
+theme = 'ananke'
+
+# Build settings
+[build]
+ writeStats = true
+
+# Markdown configuration
+[markup]
+ [markup.goldmark]
+ [markup.goldmark.extensions]
+ definitionList = true
+ footnote = true
+ linkify = true
+ strikethrough = true
+ table = true
+ taskList = true
+ [markup.goldmark.parser]
+ autoHeadingID = true
+ autoHeadingIDType = 'github'
+ [markup.goldmark.renderer]
+ unsafe = false
+ [markup.highlight]
+ style = 'monokai'
+ lineNos = true
+
+# Taxonomies
+[taxonomies]
+ category = 'categories'
+ tag = 'tags'
+ author = 'authors'
+
+# Menus
+[menus]
+ [[menus.main]]
+ name = 'Home'
+ pageRef = '/'
+ weight = 10
+ [[menus.main]]
+ name = 'Posts'
+ pageRef = '/posts'
+ weight = 20
+
+# Parameters
+[params]
+ description = 'My awesome site'
+ author = 'John Doe'
+```
+
+## Front Matter
+
+Hugo supports TOML, YAML, and JSON front matter:
+
+### TOML (default)
+
+```markdown
++++
+title = 'My First Post'
+date = 2025-01-28T12:00:00-05:00
+draft = false
+tags = ['hugo', 'tutorial']
+categories = ['blog']
+author = 'John Doe'
++++
+
+Content here...
+```
+
+### YAML
+
+```markdown
+---
+title: "My First Post"
+date: 2025-01-28T12:00:00-05:00
+draft: false
+tags: ["hugo", "tutorial"]
+---
+
+Content here...
+```
+
+## Templates
+
+### Base Template (_default/baseof.html)
+
+```html
+
+
+
+ {{ .Title }} | {{ .Site.Title }}
+ {{ partial "head.html" . }}
+
+
+ {{ partial "header.html" . }}
+
+ {{ block "main" . }}{{ end }}
+
+ {{ partial "footer.html" . }}
+
+
+```
+
+### Single Page (_default/single.html)
+
+```html
+{{ define "main" }}
+
+
+{{ end }}
+```
+
+### List Page (_default/list.html)
+
+```html
+{{ define "main" }}
+{{ .Title }}
+{{ range .Pages }}
+
+ {{ .Title }}
+ {{ .Summary }}
+
+{{ end }}
+{{ end }}
+```
+
+## Shortcodes
+
+### Built-in Shortcodes
+
+```markdown
+{{< figure src="/images/photo.jpg" title="My Photo" >}}
+
+{{< youtube dQw4w9WgXcQ >}}
+
+{{< gist user 12345 >}}
+
+{{< highlight go >}}
+fmt.Println("Hello")
+{{< /highlight >}}
+```
+
+### Custom Shortcode (layouts/shortcodes/alert.html)
+
+```html
+
+ {{ .Inner | markdownify }}
+
+```
+
+Usage:
+
+```markdown
+{{< alert type="warning" >}}
+**Warning:** This is important!
+{{< /alert >}}
+```
+
+## Content Organization
+
+### Page Bundles
+
+```
+content/
+├── posts/
+│ └── my-post/ # Page bundle
+│ ├── index.md # Content
+│ └── image.jpg # Resources
+└── _index.md # Section page
+```
+
+### Accessing Resources
+
+```html
+{{ $image := .Resources.GetMatch "image.jpg" }}
+{{ with $image }}
+ 
+{{ end }}
+```
+
+## Hugo Pipes (Asset Processing)
+
+### SCSS Compilation
+
+```html
+{{ $styles := resources.Get "scss/main.scss" | toCSS | minify }}
+
+```
+
+### JavaScript Bundling
+
+```html
+{{ $js := resources.Get "js/main.js" | js.Build | minify }}
+
+```
+
+## Taxonomies
+
+### Configure
+
+```toml
+[taxonomies]
+ tag = 'tags'
+ category = 'categories'
+```
+
+### Use in Front Matter
+
+```markdown
++++
+tags = ['go', 'hugo']
+categories = ['tutorials']
++++
+```
+
+### List Taxonomy Terms
+
+```html
+{{ range .Site.Taxonomies.tags }}
+ {{ .Page.Title }} ({{ .Count }})
+{{ end }}
+```
+
+## Multilingual Sites
+
+```toml
+defaultContentLanguage = 'en'
+
+[languages]
+ [languages.en]
+ title = 'My Site'
+ weight = 1
+ [languages.es]
+ title = 'Mi Sitio'
+ weight = 2
+```
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Page not found | Check `baseURL` configuration |
+| Theme not loading | Verify theme path in config |
+| Raw HTML not showing | Set `unsafe = true` in goldmark config |
+| Slow builds | Use `--templateMetrics` to debug |
+| Module errors | Run `hugo mod tidy` |
+| CSS not updating | Clear browser cache or use fingerprinting |
+
+## Resources
+
+- [Hugo Documentation](https://gohugo.io/documentation/)
+- [Hugo Themes](https://themes.gohugo.io/)
+- [Hugo Discourse](https://discourse.gohugo.io/)
+- [GitHub Repository](https://github.com/gohugoio/hugo)
+- [Quick Reference](https://gohugo.io/quick-reference/)
diff --git a/skills/markdown-to-html/references/jekyll.md b/skills/markdown-to-html/references/jekyll.md
new file mode 100644
index 00000000..cc99a935
--- /dev/null
+++ b/skills/markdown-to-html/references/jekyll.md
@@ -0,0 +1,321 @@
+# Jekyll Reference
+
+Jekyll is a static site generator that transforms Markdown content into complete websites. It's blog-aware and powers GitHub Pages.
+
+## Installation
+
+### Prerequisites
+
+- Ruby 2.7.0 or higher
+- RubyGems
+- GCC and Make
+
+### Install Jekyll
+
+```bash
+# Install Jekyll and Bundler
+gem install jekyll bundler
+```
+
+### Platform-Specific Installation
+
+```bash
+# macOS (install Xcode CLI tools first)
+xcode-select --install
+gem install jekyll bundler
+
+# Ubuntu/Debian
+sudo apt-get install ruby-full build-essential zlib1g-dev
+gem install jekyll bundler
+
+# Windows (use RubyInstaller)
+# Download from https://rubyinstaller.org/
+gem install jekyll bundler
+```
+
+## Quick Start
+
+### Create New Site
+
+```bash
+# Create new Jekyll site
+jekyll new myblog
+
+# Navigate to site
+cd myblog
+
+# Build and serve
+bundle exec jekyll serve
+
+# Open http://localhost:4000
+```
+
+### Directory Structure
+
+```
+myblog/
+├── _config.yml # Site configuration
+├── _posts/ # Blog posts
+│ └── 2025-01-28-welcome.md
+├── _layouts/ # Page templates
+├── _includes/ # Reusable components
+├── _data/ # Data files (YAML, JSON, CSV)
+├── _sass/ # Sass partials
+├── assets/ # CSS, JS, images
+├── index.md # Home page
+└── Gemfile # Ruby dependencies
+```
+
+## CLI Commands
+
+| Command | Description |
+|---------|-------------|
+| `jekyll new ` | Create new site |
+| `jekyll build` | Build to `_site/` |
+| `jekyll serve` | Build and serve locally |
+| `jekyll clean` | Remove generated files |
+| `jekyll doctor` | Check for issues |
+
+### Build Options
+
+```bash
+# Build site
+bundle exec jekyll build
+
+# Build with production environment
+JEKYLL_ENV=production bundle exec jekyll build
+
+# Build to custom directory
+bundle exec jekyll build --destination ./public
+
+# Build with incremental regeneration
+bundle exec jekyll build --incremental
+```
+
+### Serve Options
+
+```bash
+# Serve with live reload
+bundle exec jekyll serve --livereload
+
+# Include draft posts
+bundle exec jekyll serve --drafts
+
+# Specify port
+bundle exec jekyll serve --port 8080
+
+# Bind to all interfaces
+bundle exec jekyll serve --host 0.0.0.0
+```
+
+## Configuration (_config.yml)
+
+```yaml
+# Site settings
+title: My Blog
+description: A great blog
+baseurl: ""
+url: "https://example.com"
+
+# Build settings
+markdown: kramdown
+theme: minima
+plugins:
+ - jekyll-feed
+ - jekyll-seo-tag
+
+# Kramdown settings
+kramdown:
+ input: GFM
+ syntax_highlighter: rouge
+ hard_wrap: false
+
+# Collections
+collections:
+ docs:
+ output: true
+ permalink: /docs/:name/
+
+# Defaults
+defaults:
+ - scope:
+ path: ""
+ type: "posts"
+ values:
+ layout: "post"
+
+# Exclude from processing
+exclude:
+ - Gemfile
+ - Gemfile.lock
+ - node_modules
+ - vendor
+```
+
+## Front Matter
+
+Every content file needs YAML front matter:
+
+```markdown
+---
+layout: post
+title: "My First Post"
+date: 2025-01-28 12:00:00 -0500
+categories: blog tutorial
+tags: [jekyll, markdown]
+author: John Doe
+excerpt: "A brief introduction..."
+published: true
+---
+
+Your content here...
+```
+
+## Markdown Processors
+
+### Kramdown (Default)
+
+```yaml
+# _config.yml
+markdown: kramdown
+kramdown:
+ input: GFM # GitHub Flavored Markdown
+ syntax_highlighter: rouge
+ syntax_highlighter_opts:
+ block:
+ line_numbers: true
+```
+
+### CommonMark
+
+```ruby
+# Gemfile
+gem 'jekyll-commonmark-ghpages'
+```
+
+```yaml
+# _config.yml
+markdown: CommonMarkGhPages
+commonmark:
+ options: ["SMART", "FOOTNOTES"]
+ extensions: ["strikethrough", "autolink", "table"]
+```
+
+## Liquid Templating
+
+### Variables
+
+```liquid
+{{ page.title }}
+{{ site.title }}
+{{ content }}
+{{ page.date | date: "%B %d, %Y" }}
+```
+
+### Loops
+
+```liquid
+{% for post in site.posts %}
+
+ {{ post.title }}
+ {{ post.excerpt }}
+
+{% endfor %}
+```
+
+### Conditionals
+
+```liquid
+{% if page.title %}
+ {{ page.title }}
+{% endif %}
+
+{% unless page.draft %}
+ {{ content }}
+{% endunless %}
+```
+
+### Includes
+
+```liquid
+{% include header.html %}
+{% include footer.html param="value" %}
+```
+
+## Layouts
+
+### Basic Layout (_layouts/default.html)
+
+```html
+
+
+
+ {{ page.title }} | {{ site.title }}
+
+
+
+ {% include header.html %}
+
+ {{ content }}
+
+ {% include footer.html %}
+
+
+```
+
+### Post Layout (_layouts/post.html)
+
+```html
+---
+layout: default
+---
+
+ {{ page.title }}
+
+ {{ content }}
+
+```
+
+## Plugins
+
+### Common Plugins
+
+```ruby
+# Gemfile
+group :jekyll_plugins do
+ gem 'jekyll-feed' # RSS feed
+ gem 'jekyll-seo-tag' # SEO meta tags
+ gem 'jekyll-sitemap' # XML sitemap
+ gem 'jekyll-paginate' # Pagination
+ gem 'jekyll-archives' # Archive pages
+end
+```
+
+### Using Plugins
+
+```yaml
+# _config.yml
+plugins:
+ - jekyll-feed
+ - jekyll-seo-tag
+ - jekyll-sitemap
+```
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Ruby 3.0+ webrick error | `bundle add webrick` |
+| Permission denied | Use `--user-install` or rbenv |
+| Slow builds | Use `--incremental` |
+| Liquid errors | Check for unescaped `{` `}` |
+| Encoding issues | Add `encoding: utf-8` to config |
+| Plugin not loading | Add to both Gemfile and _config.yml |
+
+## Resources
+
+- [Jekyll Documentation](https://jekyllrb.com/docs/)
+- [Liquid Template Language](https://shopify.github.io/liquid/)
+- [Kramdown Documentation](https://kramdown.gettalong.org/)
+- [GitHub Repository](https://github.com/jekyll/jekyll)
+- [Jekyll Themes](https://jekyllthemes.io/)
diff --git a/skills/markdown-to-html/references/marked.md b/skills/markdown-to-html/references/marked.md
new file mode 100644
index 00000000..caadd69c
--- /dev/null
+++ b/skills/markdown-to-html/references/marked.md
@@ -0,0 +1,121 @@
+# Marked
+
+## Quick Conversion Methods
+
+Expanded portions of `SKILL.md` at `### Quick Conversion Methods`.
+
+### Method 1: CLI (Recommended for Single Files)
+
+```bash
+# Convert file to HTML
+marked -i input.md -o output.html
+
+# Convert string directly
+marked -s "# Hello World"
+
+# Output: Hello World
+```
+
+### Method 2: Node.js Script
+
+```javascript
+import { marked } from 'marked';
+import { readFileSync, writeFileSync } from 'fs';
+
+const markdown = readFileSync('input.md', 'utf-8');
+const html = marked.parse(markdown);
+writeFileSync('output.html', html);
+```
+
+### Method 3: Browser Usage
+
+```html
+
+
+```
+
+---
+
+## Step-by-Step Workflows
+
+Expanded portions of `SKILL.md` at `### Step-by-Step Workflows`.
+
+### Workflow 1: Single File Conversion
+
+1. Ensure marked is installed: `npm install -g marked`
+2. Run conversion: `marked -i README.md -o README.html`
+3. Verify output file was created
+
+### Workflow 2: Batch Conversion (Multiple Files)
+
+Create a script `convert-all.js`:
+
+```javascript
+import { marked } from 'marked';
+import { readFileSync, writeFileSync, readdirSync } from 'fs';
+import { join, basename } from 'path';
+
+const inputDir = './docs';
+const outputDir = './html';
+
+readdirSync(inputDir)
+ .filter(file => file.endsWith('.md'))
+ .forEach(file => {
+ const markdown = readFileSync(join(inputDir, file), 'utf-8');
+ const html = marked.parse(markdown);
+ const outputFile = basename(file, '.md') + '.html';
+ writeFileSync(join(outputDir, outputFile), html);
+ console.log(`Converted: ${file} → ${outputFile}`);
+ });
+```
+
+Run with: `node convert-all.js`
+
+### Workflow 3: Conversion with Custom Options
+
+```javascript
+import { marked } from 'marked';
+
+// Configure options
+marked.setOptions({
+ gfm: true, // GitHub Flavored Markdown
+ breaks: true, // Convert \n to
+ pedantic: false, // Don't conform to original markdown.pl
+});
+
+const html = marked.parse(markdownContent);
+```
+
+### Workflow 4: Complete HTML Document
+
+Wrap converted content in a full HTML template:
+
+```javascript
+import { marked } from 'marked';
+import { readFileSync, writeFileSync } from 'fs';
+
+const markdown = readFileSync('input.md', 'utf-8');
+const content = marked.parse(markdown);
+
+const html = `
+
+
+
+
+ Document
+
+
+
+${content}
+
+`;
+
+writeFileSync('output.html', html);
+```
diff --git a/skills/markdown-to-html/references/pandoc.md b/skills/markdown-to-html/references/pandoc.md
new file mode 100644
index 00000000..6fbe1d0f
--- /dev/null
+++ b/skills/markdown-to-html/references/pandoc.md
@@ -0,0 +1,226 @@
+# Pandoc Reference
+
+Pandoc is a universal document converter that can convert between numerous markup formats, including Markdown, HTML, LaTeX, Word, and many more.
+
+## Installation
+
+### Windows
+
+```powershell
+# Using Chocolatey
+choco install pandoc
+
+# Using Scoop
+scoop install pandoc
+
+# Or download installer from https://pandoc.org/installing.html
+```
+
+### macOS
+
+```bash
+# Using Homebrew
+brew install pandoc
+```
+
+### Linux
+
+```bash
+# Debian/Ubuntu
+sudo apt-get install pandoc
+
+# Fedora
+sudo dnf install pandoc
+
+# Or download from https://pandoc.org/installing.html
+```
+
+## Basic Usage
+
+### Convert Markdown to HTML
+
+```bash
+# Basic conversion
+pandoc input.md -o output.html
+
+# Standalone document with headers
+pandoc input.md -s -o output.html
+
+# With custom CSS
+pandoc input.md -s --css=style.css -o output.html
+```
+
+### Convert to Other Formats
+
+```bash
+# To PDF (requires LaTeX)
+pandoc input.md -s -o output.pdf
+
+# To Word
+pandoc input.md -s -o output.docx
+
+# To LaTeX
+pandoc input.md -s -o output.tex
+
+# To EPUB
+pandoc input.md -s -o output.epub
+```
+
+### Convert from Other Formats
+
+```bash
+# HTML to Markdown
+pandoc -f html -t markdown input.html -o output.md
+
+# Word to Markdown
+pandoc input.docx -o output.md
+
+# LaTeX to HTML
+pandoc -f latex -t html input.tex -o output.html
+```
+
+## Common Options
+
+| Option | Description |
+|--------|-------------|
+| `-f, --from ` | Input format |
+| `-t, --to ` | Output format |
+| `-s, --standalone` | Produce standalone document |
+| `-o, --output ` | Output file |
+| `--toc` | Include table of contents |
+| `--toc-depth ` | TOC depth (default: 3) |
+| `-N, --number-sections` | Number section headings |
+| `--css ` | Link to CSS stylesheet |
+| `--template ` | Use custom template |
+| `--metadata =` | Set metadata |
+| `--mathml` | Use MathML for math |
+| `--mathjax` | Use MathJax for math |
+| `-V, --variable =` | Set template variable |
+
+## Markdown Extensions
+
+Pandoc supports many markdown extensions:
+
+```bash
+# Enable specific extensions
+pandoc -f markdown+emoji+footnotes input.md -o output.html
+
+# Disable specific extensions
+pandoc -f markdown-pipe_tables input.md -o output.html
+
+# Use strict markdown
+pandoc -f markdown_strict input.md -o output.html
+```
+
+### Common Extensions
+
+| Extension | Description |
+|-----------|-------------|
+| `pipe_tables` | Pipe tables (default on) |
+| `footnotes` | Footnote support |
+| `emoji` | Emoji shortcodes |
+| `smart` | Smart quotes and dashes |
+| `task_lists` | Task list checkboxes |
+| `strikeout` | Strikethrough text |
+| `superscript` | Superscript text |
+| `subscript` | Subscript text |
+| `raw_html` | Raw HTML passthrough |
+
+## Templates
+
+### Using Built-in Templates
+
+```bash
+# View default template
+pandoc -D html
+
+# Use custom template
+pandoc --template=mytemplate.html input.md -o output.html
+```
+
+### Template Variables
+
+```html
+
+
+
+ $title$
+ $for(css)$
+
+ $endfor$
+
+
+$body$
+
+
+```
+
+## YAML Metadata
+
+Include metadata in your markdown files:
+
+```markdown
+---
+title: My Document
+author: John Doe
+date: 2025-01-28
+abstract: |
+ This is the abstract.
+---
+
+# Introduction
+
+Document content here...
+```
+
+## Filters
+
+### Using Lua Filters
+
+```bash
+pandoc --lua-filter=filter.lua input.md -o output.html
+```
+
+Example Lua filter (`filter.lua`):
+
+```lua
+function Header(el)
+ if el.level == 1 then
+ el.classes:insert("main-title")
+ end
+ return el
+end
+```
+
+### Using Pandoc Filters
+
+```bash
+pandoc --filter pandoc-citeproc input.md -o output.html
+```
+
+## Batch Conversion
+
+### Bash Script
+
+```bash
+#!/bin/bash
+for file in *.md; do
+ pandoc "$file" -s -o "${file%.md}.html"
+done
+```
+
+### PowerShell Script
+
+```powershell
+Get-ChildItem -Filter *.md | ForEach-Object {
+ $output = $_.BaseName + ".html"
+ pandoc $_.Name -s -o $output
+}
+```
+
+## Resources
+
+- [Pandoc User's Guide](https://pandoc.org/MANUAL.html)
+- [Pandoc Demos](https://pandoc.org/demos.html)
+- [Pandoc FAQ](https://pandoc.org/faqs.html)
+- [GitHub Repository](https://github.com/jgm/pandoc)
diff --git a/skills/markdown-to-html/references/tables-to-html.md b/skills/markdown-to-html/references/tables-to-html.md
new file mode 100644
index 00000000..2e3e6771
--- /dev/null
+++ b/skills/markdown-to-html/references/tables-to-html.md
@@ -0,0 +1,169 @@
+# Tables to HTML
+
+## Creating a table
+
+### Markdown
+
+```markdown
+
+| First Header | Second Header |
+| ------------- | ------------- |
+| Content Cell | Content Cell |
+| Content Cell | Content Cell |
+```
+
+### Parsed HTML
+
+```html
+
+
+
+ First Header
+ Second Header
+
+
+
+
+ Content Cell
+ Content Cell
+
+
+ Content Cell
+ Content Cell
+
+
+
+```
+
+### Markdown
+
+```markdown
+| Command | Description |
+| --- | --- |
+| git status | List all new or modified files |
+| git diff | Show file differences that haven't been staged |
+```
+
+### Parsed HTML
+
+```html
+
+
+
+ Command
+ Description
+
+
+
+
+ git status
+ List all new or modified files
+
+
+ git diff
+ Show file differences that haven't been staged
+
+
+
+```
+
+## Formatting Content in Tables
+
+### Markdown
+
+```markdown
+| Command | Description |
+| --- | --- |
+| `git status` | List all *new or modified* files |
+| `git diff` | Show file differences that **haven't been** staged |
+```
+
+### Parsed HTML
+
+```html
+
+
+
+ Command
+ Description
+
+
+
+
+ git statusList all new or modified files
+
+
+ git diffShow file differences that haven't been staged
+
+
+
+```
+
+### Markdown
+
+```markdown
+| Left-aligned | Center-aligned | Right-aligned |
+| :--- | :---: | ---: |
+| git status | git status | git status |
+| git diff | git diff | git diff |
+```
+
+### Parsed HTML
+
+```html
+
+
+
+ Left-aligned
+ Center-aligned
+ Right-aligned
+
+
+
+
+ git status
+ git status
+ git status
+
+
+ git diff
+ git diff
+ git diff
+
+
+
+```
+
+### Markdown
+
+```markdown
+| Name | Character |
+| --- | --- |
+| Backtick | ` |
+| Pipe | \| |
+```
+
+### Parsed HTML
+
+```html
+
+
+
+ Name
+ Character
+
+
+
+
+ Backtick
+ `
+
+
+ Pipe
+ |
+
+
+
+```
\ No newline at end of file
diff --git a/skills/markdown-to-html/references/tables.md b/skills/markdown-to-html/references/tables.md
new file mode 100644
index 00000000..b0581c69
--- /dev/null
+++ b/skills/markdown-to-html/references/tables.md
@@ -0,0 +1,72 @@
+# Organizing information with tables
+
+You can build tables to organize information in comments, issues, pull requests, and wikis.
+
+## Creating a table
+
+You can create tables with pipes `|` and hyphens `-`. Hyphens are used to create each column's header, while pipes separate each column. You must include a blank line before your table in order for it to correctly render.
+
+```markdown
+
+| First Header | Second Header |
+| ------------- | ------------- |
+| Content Cell | Content Cell |
+| Content Cell | Content Cell |
+```
+
+
+
+The pipes on either end of the table are optional.
+
+Cells can vary in width and do not need to be perfectly aligned within columns. There must be at least three hyphens in each column of the header row.
+
+```markdown
+| Command | Description |
+| --- | --- |
+| git status | List all new or modified files |
+| git diff | Show file differences that haven't been staged |
+```
+
+
+
+If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on GitHub. For more information, see [About writing and formatting on GitHub](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor).
+
+## Formatting content within your table
+
+You can use [formatting](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table:
+
+```markdown
+| Command | Description |
+| --- | --- |
+| `git status` | List all *new or modified* files |
+| `git diff` | Show file differences that **haven't been** staged |
+```
+
+
+
+You can align text to the left, right, or center of a column by including colons `:` to the left, right, or on both sides of the hyphens within the header row.
+
+```markdown
+| Left-aligned | Center-aligned | Right-aligned |
+| :--- | :---: | ---: |
+| git status | git status | git status |
+| git diff | git diff | git diff |
+```
+
+
+
+To include a pipe `|` as content within your cell, use a `\` before the pipe:
+
+```markdown
+| Name | Character |
+| --- | --- |
+| Backtick | ` |
+| Pipe | \| |
+```
+
+
+
+## Further reading
+
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
+* [Basic writing and formatting syntax](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
\ No newline at end of file
diff --git a/skills/markdown-to-html/references/writing-mathematical-expressions-to-html.md b/skills/markdown-to-html/references/writing-mathematical-expressions-to-html.md
new file mode 100644
index 00000000..4691850d
--- /dev/null
+++ b/skills/markdown-to-html/references/writing-mathematical-expressions-to-html.md
@@ -0,0 +1,350 @@
+# Writing Mathematical Expressions to HTML
+
+## Writing Inline Expressions
+
+### Markdown
+
+```markdown
+This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$
+```
+
+### Parsed HTML
+
+```html
+This sentence uses $ delimiters to show math inline:
+
+
+
+```
+
+### Markdown
+
+```markdown
+This sentence uses $\` and \`$ delimiters to show math inline: $`\sqrt{3x-1}+(1+x)^2`$
+```
+
+### Parsed HTML
+
+```html
+This sentence uses
+
+
+ delimiters to show math inline:
+
+
+
+
+```
+
+---
+
+## Writing Expressions as Blocks
+
+### Markdown
+
+```markdown
+**The Cauchy-Schwarz Inequality**\
+$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$
+```
+
+### Parsed HTML
+
+```html
+
+ The Cauchy-Schwarz Inequality
+
+
+
+
+```
+
+### Markdown
+
+```markdown
+**The Cauchy-Schwarz Inequality**
+
+ ```math
+ \left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)
+ ```
+```
+
+### Parsed HTML
+
+```html
+The Cauchy-Schwarz Inequality
+
+
+
+
+```
+
+### Markdown
+
+```markdown
+The equation $a^2 + b^2 = c^2$ is the Pythagorean theorem.
+```
+
+### Parsed HTML
+
+```html
+The equation
+
+```
+
+### Markdown
+
+```
+$$
+\int_0^\infty e^{-x} dx = 1
+$$
+```
+
+### Parsed HTML
+
+```html
+
+```
+
+---
+
+## Dollar Sign Inline with Mathematical Expression
+
+### Markdown
+
+```markdown
+This expression uses `\$` to display a dollar sign: $`\sqrt{\$4}`$
+```
+
+### Parsed HTML
+
+```html
+This expression uses
+ \$ to display a dollar sign:
+
+
+
+
+```
+
+### Markdown
+
+```markdown
+To split $100 in half, we calculate $100/2$
+```
+
+### Parsed HTML
+
+```html
+To split
+ $100 in half, we calculate
+
+
+
+
+```
diff --git a/skills/markdown-to-html/references/writing-mathematical-expressions.md b/skills/markdown-to-html/references/writing-mathematical-expressions.md
new file mode 100644
index 00000000..ae911f9c
--- /dev/null
+++ b/skills/markdown-to-html/references/writing-mathematical-expressions.md
@@ -0,0 +1,76 @@
+# Writing mathematical expressions
+
+Use Markdown to display mathematical expressions on GitHub.
+
+## About writing mathematical expressions
+
+To enable clear communication of mathematical expressions, GitHub supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks.
+
+GitHub's math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide).
+
+Mathematical expressions rendering is available in GitHub Issues, GitHub Discussions, pull requests, wikis, and Markdown files.
+
+## Writing inline expressions
+
+There are two options for delimiting a math expression inline with your text. You can either surround the expression with dollar symbols (`$`), or start the expression with $\` and end it with \`$. The latter syntax is useful when the expression you are writing contains characters that overlap with markdown syntax. For more information, see [Basic writing and formatting syntax](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
+
+```text
+This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$
+```
+
+
+
+```text
+This sentence uses $\` and \`$ delimiters to show math inline: $`\sqrt{3x-1}+(1+x)^2`$
+```
+
+
+
+## Writing expressions as blocks
+
+To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`.
+
+> [!TIP] If you're writing in an .md file, you will need to use specific formatting to create a line break, such as ending the line with a backslash as shown in the example below. For more information on line breaks in Markdown, see [Basic writing and formatting syntax](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#line-breaks).
+
+```text
+**The Cauchy-Schwarz Inequality**\
+$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$
+```
+
+
+
+Alternatively, you can use the \`\`\`math code block syntax to display a math expression as a block. With this syntax, you don't need to use `$$` delimiters. The following will render the same as above:
+
+````text
+**The Cauchy-Schwarz Inequality**
+
+```math
+\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)
+```
+````
+
+## Writing dollar signs in line with and within mathematical expressions
+
+To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly.
+
+* Within a math expression, add a `\` symbol before the explicit `$`.
+
+ ```text
+ This expression uses `\$` to display a dollar sign: $`\sqrt{\$4}`$
+ ```
+
+ 
+
+* Outside a math expression, but on the same line, use span tags around the explicit `$`.
+
+ ```text
+ To split $100 in half, we calculate $100/2$
+ ```
+
+ 
+
+## Further reading
+
+* [The MathJax website](http://mathjax.org)
+* [Getting started with writing and formatting on GitHub](https://docs.github.com/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
\ No newline at end of file