agentleFS
TheSethRoseTheSethRose/render-skill/skills/render/SKILL.md

render

Skill1 starsChanged 30 days agoMITView on GitHub

Render Markdown files to styled HTML, Word (DOCX), and PDF. Use when the user invokes `/render` or asks to convert, export, or render .md files into HTML, DOCX, or PDF. Not for editing existing Word/PDF files or authoring new documents from scratch.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, publish and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • VercelSkill

    publish

    Publish a single demo to v0 and optionally create Typefully drafts. Use when the user says "publish", "publish to v0", or "create typefully draft" for a demo.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

Files
SKILL.md

Render

Convert Markdown into shareable documents with the bundled script. It needs only uv (pandoc ships inside the pypandoc-binary dependency) and, for PDF, Chrome/Chromium/Edge or WeasyPrint. Paths below are relative to this skill's directory.

uv run scripts/render.py <file.md|dir> [more…] [options]

Options: -f html,docx,pdf (default all three), -o DIR (default: next to each source), -r (recurse directories), --toc, --css FILE (HTML/PDF styling), --reference-docx FILE (Word styles).

Choosing inputs and formats

  • /render path/to/file.md → render that file to all three formats.
  • /render with no argument → use the Markdown file the conversation is about (just written or edited). If several are plausible, ask which; if none, ask for a path.
  • Honor any formats or output directory the user names ("just a PDF" → -f pdf).
  • Outputs overwrite same-named .html/.docx/.pdf next to the source. If one exists and wasn't produced by this skill earlier in the session, mention it before overwriting or use -o.

Behavior worth knowing

  • Input is GitHub-flavored Markdown plus YAML front matter (title, subtitle, author, date become the document header), footnotes, $math$, and smart quotes.
  • Design: editorial and quiet. HTML/PDF use Charter for reading, Inter for headings and labels, one ink-blue accent, and fall back to Georgia/system fonts where those aren't installed. HTML is self-contained (CSS, images embedded) and follows light/dark mode. PDF is printed from the same HTML with print sizing and page numbers.
  • DOCX uses the bundled assets/reference.docx (Georgia body, Aptos headings, Consolas code: fonts recipients have). Rebuild it with uv run scripts/build_reference_docx.py after changing its palette or fonts.
  • Relative image paths resolve from the source file's folder.
  • To change the look, edit assets/style.css or pass --css. For a different Word style, pass --reference-docx (--init-reference-docx ref.docx writes pandoc's plain default to start from).

After rendering

The script prints ok/FAIL per output and exits non-zero on any failure. Report the output paths and any failures. Open or share the files only if the user asks or it's clearly wanted.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.