Organize markdown knowledge bases with wikilinks, frontmatter, and hub pages.
npx skills add https://github.com/styrene-lab/omegon --skill flynt
Please help me install this Agent Skill. Skill: flynt Source: https://github.com/styrene-lab/omegon/tree/main/skills/flynt Command: npx skills add https://github.com/styrene-lab/omegon --skill flynt
This Skill helps teams write markdown documentation that remains easy to navigate, connect, and maintain across notes, workspaces, and knowledge bases.
[[wikilinks]] to connect related docs with optional display text.Use the flynt skill to turn this folder of markdown notes into a clean, interlinked documentation workspace with frontmatter, wikilinks, and hub pages.
High-intent search queries and answers about installing and using this skill.
To keep markdown documentation navigable, apply consistent YAML frontmatter for metadata and use case-insensitive [[wikilinks]] to connect related notes. Design directory hierarchies with hub pages so the documentation tree doubles as a navigation graph across tools like mdserve, Obsidian, and GitHub.
Organize a markdown knowledge base by adding consistent YAML frontmatter for titles, status, and tags, then use case-insensitive [[wikilinks]] for graph-friendly cross-linking. Structure directories with hub pages and backlinks to support persistent project organization and mdserve browsing.
Yes, this approach works with mdserve and Obsidian by using stable naming and link patterns. Preparing content with consistent YAML frontmatter and case-insensitive slug resolution ensures the documentation remains navigable across these markdown viewers.
Wikilinks often break due to inconsistent slug resolution or missing YAML frontmatter. Using case-insensitive slug resolution and stable naming patterns ensures graph-friendly cross-linking remains intact when moving markdown files between tools.
You need YAML frontmatter in markdown documentation when you want documents indexed, grouped, and navigable. Consistent frontmatter for titles, status, tags, and dates allows hub pages to aggregate content and supports interlinked document structures.
Yes, you can use directory hierarchies and hub pages for engineering spec docs and design notes. Structuring these documents with graph-friendly cross-linking and backlinks ensures every page links into the larger knowledge graph for persistent project organization.
PieroSierraIngest markdown files from raw/ into structured wiki articles and update the index.
AissenLiuIngests sources into a persistent, interlinked Markdown wiki with YAML frontmatter.
MarsWang42Create and edit Obsidian Flavored Markdown notes with wikilinks, embeds, callouts, and frontmatter.
huidgeConvert a Markdown directory into a static website with a grouped sidebar.