lossless-flavored-markdown

Normalize directives, Obsidian callouts, and Markdoc tags into a unified component AST.

4|Updated May 4, 2026
One-click install
npx skills add https://github.com/lossless-group/lossless-agent-skills --skill lossless-flavored-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lossless-flavored-markdown
Source: https://github.com/lossless-group/lossless-agent-skills/tree/main/lossless-flavored-markdown
Command: npx skills add https://github.com/lossless-group/lossless-agent-skills --skill lossless-flavored-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standard markdown lacks support for rich, structured content like styled callouts, hoverable citations, and embedded media, while MDX introduces JSX lock-in that ties content to specific frontend frameworks. This skill solves that by providing Lossless Flavored Markdown (LFM), a polyglot extended markdown spec that normalizes multiple syntax styles to a unified component pipeline, so teams can author content in their preferred tool (Obsidian, Astro, etc.) without sacrificing rich rendering capabilities.

Core Features & Use Cases

  • Polyglot syntax normalization: Supports directive syntax, Obsidian callouts, Markdoc tags, and bare URLs, all rendering to the same consistent components so authors can use their preferred writing style without breaking site rendering.
  • Built-in rich content triggers: Includes out-of-the-box support for styled callouts, hex-code citations with hover popovers, auto-embedded media (YouTube, Vimeo, etc.), link preview cards, image galleries, dialog blocks, and Mermaid diagrams.
  • Customizable extensibility: Sites can extend LFM via three non-breaking layers (per-instance attributes, variant registry, CSS theme tokens) to add custom components or adjust styling without forking the core package.
  • Cross-site consistency: Used across all Astro Knots sites to enforce uniform content rendering, frontmatter conventions, and citation rules across team projects.

Quick Start

Use this skill to add a styled warning callout, hex-code citation with hover preview, and embedded YouTube video to a markdown file in your Astro Knots site.

Frequently Asked Questions about lossless-flavored-markdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add styled callouts and hoverable citations in Astro markdown without using MDX?

To add styled callouts and hoverable citations in Astro markdown without MDX, use Lossless Flavored Markdown (LFM) to normalize polyglot syntax like Obsidian callouts and directives into a unified component AST. This enables rich rendering without JSX lock-in.

What is the best way to migrate Obsidian vault content to a publishable Astro site?

Migrating Obsidian vault content to Astro sites is best handled by normalizing Obsidian callouts and polyglot syntax into a unified component pipeline. LFM supports this by mapping your existing markdown syntax to consistent, publishable web components.

Can I customize markdown callout styling and behavior across different Astro sites?

You can customize markdown callout styling and behavior across Astro sites using three non-breaking layers: per-instance attributes, a variant registry, and CSS theme tokens. This allows site-specific adjustments without forking the core package.

How does build-time OpenGraph fetching work for markdown link preview cards?

Build-time OpenGraph fetching for markdown link preview cards works by retrieving metadata during the build process to generate instant hover popovers. LFM automatically handles bare URLs and hex-code citations to create these embedded preview components.

Does LFM support Markdoc tags and directive syntax in the same markdown file?

LFM supports Markdoc tags, directive syntax, and Obsidian callouts within the same markdown file through polyglot syntax normalization. It maps these varied formats to the same consistent components, allowing authors to use their preferred writing style.

What are the limitations of using extended markdown syntax instead of MDX for component rendering?

Using extended markdown instead of MDX for component rendering limits direct JSX manipulation within content files, but avoids framework lock-in. LFM mitigates this by providing built-in triggers for media, Mermaid diagrams, and galleries via a configurable syntax pipeline.