← All AgentBay walkthroughsAGENTBAY WALKTHROUGH · SYNTHETIC INPUT

Turn release notes into a readable web page

Turn release notes into a readable page, with the table and code examples intact.

Tested with Codex CLI 0.163.0.

START HERE

Install this skill with AgentBay

Read markdown-to-html SKILL.md ↗ · Pinned publisher instructions

Get the finder once. Install AgentBay for your app, then open a fresh chat.
Install this one skill. Use the button below. The prompt includes this publisher’s exact source and revision. Ask AgentBay to check the instructions, license and prerequisites before installing.
Confirm it is active. Start a fresh agent session if needed. Check that the selected skill appears in Skills, then ask your agent to read its SKILL.md and required resources. In Claude desktop, upload and enable its complete ZIP; a filesystem copy does not activate it.

To follow along, download the starter project, unzip it and open that folder in your agent. Complete the local setup below, then give your agent this task.

Here’s the task to give your agent

Want a few skills? Add them to your selection, review the exact list, and copy instructions for only those choices. Paste the commands into your terminal, then confirm the skills appear in your agent.

What you’re starting with

Inspect the Markdown first. It contains a useful table and code examples alongside a raw script, an unsafe link and a tracking image. Keep the harmless <script> text inside code while removing executable markup.

Here’s what to do

Keep the source fixed. Ask the agent to use the pinned Markdown-to-HTML skill, parse the document and sanitize the resulting HTML. In the recorded Codex run, only the converter and its generated page changed. Then the unchanged parser checks ran independently.

Check the result

The heading, table, list, code block and safe link survive in a complete English HTML document. The active markup and external image do not. All eight independent content checks pass.

Parse Markdown, then sanitize the resulting HTML. Keep code examples as readable text.

Start with the instructions

Read the actual markdown-to-html SKILL.md ↗

github/awesome-copilot · pinned 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Reviewed October 31, 2026.

Good for: Converting Markdown into HTML with tables and fenced code
Choosing a parser and sanitizing its output before display
Needs: Node 24 and the pinned marked and sanitize-html packages
Python 3 for the supplied independent HTML checks
Scope: Synthetic release notes containing tables, fenced code and raw HTML
Local HTML output using the fixture’s parser and sanitizer

The input and actual output

Download the synthetic project and unchanged checks (ZIP). It contains no installed third-party skills. Install the pinned upstream skill separately after reviewing its license.

Trail Notes 1.2
GFM table + code preserved
8 content checks pass

Inspect the actual solution: build.mjs · page.html.

Keep code examples without keeping an executable script

A document can legitimately explain what a script tag looks like. That should not make the tag run.

Try this: Inline code: `<script>` · raw HTML: <script>globalThis.untrusted = true</script>
Checked result: The inline text remains; the executable script element is removed.

The independent HTML parser checks both conditions on the actual generated page. This case shares the Markdown walkthrough’s recorded run and receipt.

Inspect the shared test receipt →

Checks performed

Heading, two-row GFM table, list, fenced code and safe link retained
Raw scripts, event handlers, unsafe URL schemes and external images absent
English metadata and responsive viewport present; literal <script> inside code remains text

Test receipt, installed-file hashes and source binding (JSON)

App test results

Runtime-specific status
Runtime	Result
Codex CLI 0.163.0	passed
Codex desktop	not tested — manual desktop check pending
Claude Code	not tested — no authenticated run recorded
Claude desktop	not tested — manual desktop check pending

Repeat it in a clean project

Unzip the input into a new directory. Follow the setup below; JavaScript examples use Node 24 and Python examples specify their packages. Install only the selected source skill at the pinned revision above. Open a fresh agent session and confirm its skill list contains the installed skill; ask it to read SKILL.md before changing the input.

npm ci
Ask your agent to implement build.mjs only, then generate page.html
npm run build
python3 verify.py

Run the checks, then compare your output with the recorded result.