Source: raw/reddit-1tl5x2x.md (r/ClaudeAI 2026-05-22 announcement by u/iamgioh) + ai-research/quarkdown-com-2026-05-23.md (quarkdown.com landing page + iamgio/quarkdown GitHub repo + CHANGELOG.md + skills/ tree + LICENSE + uditya-kumar/quarkdown-skill third-party fetch)

Project: Quarkdown — Markdown-based typesetting language with Turing-complete function extensions URL: https://quarkdown.com | Repo: github.com/iamgio/quarkdown Version: 2.1.0 (released 2026-05-23, commit 8ccecd9) License: GPL (root LICENSE file uses verbatim GNU GPL v3 boilerplate language) Maintainer: iamgio = Giorgio Garofalo (u/iamgioh on Reddit) Source type: Product launch / Reddit announcement

[Reddit signal — r/ClaudeAI 2026-05-22] Quarkdown 2.1.0 is a Markdown-based typesetting language (a programmable alternative to LaTeX) that compiles a single .qd source into print-ready PDFs, paged books, reveal.js slides, knowledge-base wikis, or plain HTML. The 2.1.0 release ships an official Claude Code skill bundle in the main repo at skills/quarkdown/ (first commit 3294618 “feat(skills): add skill” on 2026-05-21, two days before the version tag). The skill lets Claude Code drive typesetting workflows end-to-end — pick the right .doctype, write syntactically-correct Quarkdown, avoid failure modes (page-break gotchas, inline vs body calls, paragraph-merge bugs), and shell out to the Quarkdown CLI to produce PDFs and slides without leaving the agent.

Key Takeaways

  • Quarkdown is a real LaTeX alternative — Turing-complete and Markdown-flavored. Born as a CommonMark + GFM extension, the Quarkdown flavor adds functions (.somefunction {arg1} {arg2}), variables, loops, conditionals, layout builders (.row, .clip), math, I/O, and an ever-expanding standard library. A single source compiles to .doctype{plain} (continuous flow, Notion/Obsidian style), .doctype{paged} (paper/book via paged.js), .doctype{slides} (reveal.js), or .doctype{docs} (sidebar-navigated wiki with client-side search). All four targets can produce PDF via paged.js.
  • The official Claude Code skill ships inside the Quarkdown 2.1.0 monorepo, not as a separate package. It lives at iamgio/quarkdown/skills/quarkdown/ (Kotlin/Gradle monorepo also contains 18 sibling subprojects — quarkdown-cli, quarkdown-core, quarkdown-stdlib, quarkdown-lsp, quarkdown-server, etc.). The 2.1.0 CHANGELOG documents the install path ~/.claude/skills/quarkdown and references Anthropic’s docs.claude.com/en/docs/agents-and-tools/agent-skills/overview. This is a real Anthropic-format Claude Code skill bundle (SKILL.md + references), not a README mention.
  • There is also an unofficial third-party Claude Skill for Quarkdown — disambiguate carefully. uditya-kumar/quarkdown-skill (skills.sh listing, install via npx skills add uditya-kumar/quarkdown-skill) was posted to r/ClaudeAI two days before the official 2.1.0 ship (Reddit post 1tjbhxx, May 19-ish). It is a third-party skill, not affiliated with iamgio. Self-reported evals: 100% pass with skill vs 57.9% without on a 26-task suite (iteration 1). Both skills install to the same path (~/.claude/skills/quarkdown/) by Anthropic convention, so users should pick one to avoid a clobber — see Try It below for which to install.
  • Why this is wiki-worthy. Quarkdown is the first serious open-source “professional typesetting” target with an official Claude Code skill from the language maintainer — most existing skill bundles target Anthropic-internal workflows (skills) or generalist tasks (awesome-claude-code). For the wiki’s “Claude as an AIOS” thesis, this is an existence-proof that a language vendor can ship a skill bundle alongside the language itself and have agents drive the full Markdown → PDF / slides / wiki compile loop. Compare to the HTML-effectiveness thesis (Claude emits self-contained .html files) — Quarkdown is the alternative render path for documents where print-grade typography, paged-media rules, real bibliographies, or true slide decks matter.
  • GPL license matters for ingest decisions. The repo’s LICENSE uses verbatim GPL v3 boilerplate language. Quarkdown is free to use, run, and redistribute under GPL terms; embedding the Quarkdown CLI inside a closed-source product likely triggers copyleft. For agency / WEO Marketly internal use this is a non-issue; for any productized resale path it’s worth a license review.
  • Quarkdown 2.0.0 (the bigger release) preceded this by ~2 months. 2.0.0 introduced the docs document type, fully-offline HTML output (fonts/themes bundled, no CDN dependency), parallel rendering across sibling elements, the .icon Bootstrap-Icons function, a plain-text render target (--render plaintext), and a default output dir rename (./output./quarkdown-output). 2.1.0 is the follow-up minor — maintainer’s stated policy is “next minor releases will be smaller and more frequent.”

What the skill actually does

From the third-party uditya-kumar/quarkdown-skill README (the official iamgio skills/quarkdown/SKILL.md body was not extracted in this fetch — see Open Questions). Both skills target the same problem surface, so the structure is informative either way:

CapabilityWhat Claude does with it
Decision guidancePicks .doctype (plain / paged / slides / docs) and theme based on the user’s intent (“write me a paper” → paged, “build a deck” → slides, “scaffold a wiki” → docs).
Syntax disciplineEnforces .fn {arg} named:{value} argument forms, distinguishes inline vs block-body calls, applies :: chaining for piped layout, {...} for tight calls, \ for line continuation.
CookbookMaps user intents (columns, callouts, figures, equations, fragments, footnotes, TOCs, covers, bibliographies, charts) to the correct Quarkdown calls and stdlib functions.
Failure-mode awarenessAvoids known Quarkdown gotchas — double page breaks before #, lazy-line paragraph merging, inline-vs-body call confusion, missing figure captions, page counters appearing in plain documents where they shouldn’t.
TemplatesFour starter .qd templates included as assets/templates/{plain,paged,slides,docs}.qd (third-party skill bundles these explicitly; iamgio’s skill likely does the same since the file tree shows skills/quarkdown/ is a full directory not a single file).
Auto-activationTriggers on .qd files, Quarkdown syntax questions, or natural-language requests for slides / paged PDFs / wikis from Markdown-like sources.

Implementation

Tool/Service: Quarkdown 2.1.0 + official Claude Code skill bundle Setup:

  1. Install Quarkdown CLI (requires Java 17 + Node.js + npm — install script handles them):
    • macOS (Homebrew): brew install quarkdown-labs/quarkdown/quarkdown
    • Linux / macOS (script): curl -fsSL <quarkdown-get-script> | sudo env "PATH=$PATH" bash (installs into /opt/quarkdown with wrapper at /usr/local/bin/quarkdown)
    • Windows (Scoop or install script): see get-quarkdown.com or the README at github.com/iamgio/quarkdown
  2. Install the skill into Claude Code’s user-scope skills directory. Two routes (see Try It for which to pick):
    • Official iamgio route: copy skills/quarkdown/ from the Quarkdown 2.1.0 repo into ~/.claude/skills/quarkdown/. The CHANGELOG documents this path explicitly.
    • Third-party uditya-kumar route: npx skills add uditya-kumar/quarkdown-skill (skills.sh installer; same destination path).
  3. The skill auto-activates when Claude sees .qd files or hears a request for “slides,” “a paged PDF,” “a wiki,” or “a print-ready document” from Markdown source. No /skill-name invocation needed.

Cost: Free and open-source (GPL). Quarkdown itself has zero hosted cost. The skill consumes Claude Code tokens like any other skill — SKILL.md body loads only when activated, references load on demand, so the at-rest cost is ~100 tokens (skill name + description).

Integration notes:

  • Quarkdown ships its own LSP server (quarkdown-lsp in the monorepo) and a VS Code extension. Pairing the LSP with Claude Code’s editor integration gives you in-editor diagnostics + agent-driven authoring in the same workflow.
  • The repo also has its own CLAUDE.md at the root — instructions for contributors to the Quarkdown codebase using Claude Code (not for end-users of the skill). Don’t conflate the two.
  • For wiki / knowledge-base output (.doctype{docs}), Quarkdown competes directly with the beautiful-html-templates surface and the HTML-effectiveness thesis — Quarkdown gives you paged-media + bibliographies + Turing-complete templating; plain HTML gives you maximum flexibility. Pick by output target, not by author preference.
  • License is GPL — fine for internal / agency use. If the document pipeline ever ships as part of a closed-source product, do a license check first.

Try It

  1. Install Quarkdown on macOS first. brew install quarkdown-labs/quarkdown/quarkdown. Confirm with quarkdown --version — should show 2.1.0 or higher.
  2. Pick one skill and stick with it. Both the official iamgio skill (in iamgio/quarkdown/skills/quarkdown/) and the third-party uditya-kumar skill install to ~/.claude/skills/quarkdown/ — second one clobbers the first. For most users the official iamgio skill is the right pick: it ships with the language itself, license-matched, maintained by the language author, and 2.1.0 documents the install path in the CHANGELOG. If you want the higher-eval third-party version, install instead: npx skills add uditya-kumar/quarkdown-skill.
  3. Try a paged PDF. In a Claude Code session: “Write me a 4-page research-paper-style brief on [topic] as Quarkdown, then compile it to PDF.” The skill should pick .doctype{paged}, scaffold a .qd file with title / abstract / sections, and run the Quarkdown CLI to produce a print-ready PDF. Compare the typography to a stock HTML or Markdown-to-PDF output — paged.js handles page breaks, page counters, and figure floats far more cleanly.
  4. Try slides without leaving Claude Code. “Make me a 10-slide deck on [topic] using .doctype{slides}.” Quarkdown compiles to reveal.js — proper slide transitions, fragments, speaker notes, no separate slide tool. Compare the output to the beautiful-html-templates HTML-deck route — both produce 16:9 web decks, but Quarkdown’s source is one .qd file vs a many-file HTML template.
  5. Wire it into Hermes skill bundles (optional). If you run Hermes Agent, the Quarkdown skill is a natural candidate for a /research-paper or /print-deck bundle. Pair with a pandoc skill for cross-format conversion if needed.

Open Questions

  • iamgio’s official skills/quarkdown/SKILL.md body was not extracted in this fetch — only the directory existence (commit 3294618) was confirmed. Does the official skill instruct Claude to do the same things the third-party uditya-kumar skill does (decision guidance + syntax discipline + cookbook + failure-mode awareness + four templates), or does it focus narrower (e.g., compile-loop integration via shell-out to the Quarkdown CLI, with less syntax instruction since the LSP already does that)?
  • Side-by-side installation — both skills install to ~/.claude/skills/quarkdown/. If a user runs npx skills add uditya-kumar/quarkdown-skill after installing iamgio’s official skill, does Anthropic’s skill loader fail loudly, silently overwrite, or namespace them? The wiki should test this once one of us actually installs.
  • Maintainer-handle linkage. The Reddit post is u/iamgioh. The GitHub repo is iamgio (Giorgio Garofalo). These are almost certainly the same person — the Reddit post link-targets quarkdown.com, the repo’s domain. Confirmed-but-not-verbosely-cited: no public statement on iamgio’s GitHub bio explicitly says “u/iamgioh on Reddit” or vice versa. Treat as ^[inferred] until one of us asks directly or finds a cross-link.
  • Skill ecosystem hygiene. The third-party uditya-kumar/quarkdown-skill was published on May 21, 2026 — the same day as iamgio’s skills/quarkdown/ commit. Coincidence or did one trigger the other? If uditya-kumar’s was first by hours and iamgio’s was the response, that’s a notable case of community-skill → official-skill conversion. If iamgio’s was first, the third-party skill is a friendly fork. Neither has a precise public timestamp clean enough to settle this from this fetch alone.