# Kg Draft To HTML
> Render a long-form draft from drafts/*.md into a self-contained HTML page at drafts/html/.html, in the same house style as the mailing-list digests (Georgia, 640px, inline CSS, "Best, Andrew" sign-off). A faithful format conversion only — the draft's words, order and structure are never edited, summarised or rewritten. Triggers on `/kg-draft-to-html []` or "make an HTML version of this draft" / "render the draft to HTML".
- Skill: `frutik/kg-draft-to-html` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add frutik/kg-draft-to-html`
- Raw SKILL.md: https://api.skillmd.com/api/skills/frutik/kg-draft-to-html/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: frutik (https://skillmd.com/u/frutik)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/frutik/kg-draft-to-html
---
# Awesome Search — Draft to HTML
Turns one hand-written draft in `drafts/` into a single standalone HTML file
that can be pasted into an email, attached, or opened in a browser.
This is a **published artifact, not a vault note** — like `kg-readme-writer`'s
README.md and `kg-mail-list`'s digests. Vault conventions (approval, History
entries, `kg-reviewer`, wikilink resolution) do not apply, and the output is
written outside `obsidian/vault/`.
## When to use
- `/kg-draft-to-html []`
- "make an HTML version of this draft", "render the draft to HTML",
"turn drafts/foo.md into HTML"
- No draft given → list the `.md` files in `drafts/` and ask which one.
Never guess, and never render all of them unasked.
## Output
- `drafts/html/.html`, where `` is the draft's filename without
`.md` (`drafts/llm-judge-agreement-plain-talk.md` →
`drafts/html/llm-judge-agreement-plain-talk.html`). Create `drafts/html/`
if missing.
- One file per draft. Re-running overwrites it — the draft is the only truth,
and the HTML is a derived file that is never hand-edited. If someone has
hand-edited the HTML, those edits are lost; say so before overwriting when
you have reason to suspect it.
## The hard rule: convert, never rewrite
This skill is a **renderer, not an editor**. Every word, sentence, heading,
table row, list item and link in the draft comes out in the same order with
the same wording. Specifically, do not:
- summarise, tighten, expand or re-voice any passage;
- strip statistics, counts or numbers — unlike `kg-mail-list`, whose no-stats
rule exists because it *derives* an email from History entries, this skill
reproduces a document the author already wrote;
- rewrite `[[wikilinks]]` into site links, or resolve them at all — they stay
verbatim as plain text (the script reports any it finds so the author can
decide);
- reorder sections, drop a trailing section, add a preamble, or invent a
subtitle, dateline or byline the draft does not have;
- fix the draft's typos, grammar or facts. If something looks wrong, mention
it in your summary and leave the file alone — the fix belongs in the
Markdown, not in the HTML.
The only additions to the author's text are the fixed `` (title +
inline CSS) and the fixed footer sign-off, both described below.
## Procedure
1. Resolve which draft to render (argument, or ask). Accept a bare name
(`llm-judge-agreement-plain-talk`) as well as a path.
2. Run the renderer from the repo root:
```sh
python3 claude-skills/kg-draft-to-html/scripts/draft_to_html.py drafts/.md
```
It is stdlib-only Python 3, no dependencies. `-o ` overrides the
default output location. **Use the script rather than hand-writing the
HTML** — hand conversion of a 300-line essay is where paraphrase and
dropped paragraphs creep in.
3. Read the script's report: output path, the `` it picked, and any
`[[wikilinks]]` left verbatim.
4. Spot-check the output — that the last section of the draft is present,
that tables and blockquotes rendered as such, and that no `&` or
stray `<` escaping artefacts appear.
5. Stage the file with `git add drafts/html/<stem>.html` (add-only — never
commit or push; that stays the user's call).
6. Report: which draft was rendered, where the HTML went, the page title, and
any wikilinks or unsupported constructs worth the author's attention.
## Page shape
Same house style as `mails/<year>.<week>.html` — self-contained, minimal,
valid HTML with no external stylesheets, scripts, fonts or images, so it
renders correctly with no network access.
```html
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title><the draft's first H1, markup stripped>
...
...
Best,
Andrew