Quarkdown vs Skrun

Quarkdown is an open-source typesetting system built on Markdown that eliminates the need for separate tools like LaTeX, Notion, GitBook, or Beamer. Write once in a single extended Markdown syntax and compile to paged PDFs, knowledge bases, documentation sites, or interactive presentations. The system includes Turing-complete scripting that lets you define reusable functions, avoiding repetitive formatting work across large document sets. A live reactive preview updates as you type, making the editing loop feel modern rather than the traditional LaTeX compile-and-pray cycle. Maintained by Giorgio Garofalo under GPL-3.0, Quarkdown hit 201 points on Hacker News this week and is positioning itself as a serious unified alternative to the fragmented academic and developer document toolchain. Not AI-native, but exactly the kind of leverage tool that saves hours every week for anyone writing technical docs, research papers, or slide decks.

Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.