Ingest sources into a persistent, interlinked Markdown wiki with frontmatter validation.
npx skills add https://github.com/rnben/hermes-skills --skill llm-wiki-rnben
Please help me install this Agent Skill. Skill: llm-wiki Source: https://github.com/rnben/hermes-skills/tree/main/plugins/research-skills/skills/llm-wiki Command: npx skills add https://github.com/rnben/hermes-skills --skill llm-wiki-rnben
Build and organize a persistent, interlinked knowledge base from scattered sources into a navigable wiki.
Instruct the agent to initialize a wiki at the configured path and begin ingesting your first sources.
High-intent search queries and answers about installing and using this skill.
To build an interlinked Markdown wiki, you ingest scattered sources into a structured repository. The system converts raw inputs into cross-referenced pages with frontmatter validation, wikilinks, and taxonomy tagging to create a persistent knowledge base.
Organizing a knowledge base with wikilinks and frontmatter involves applying a schema to validate metadata and cross-reference pages. This maintains consistency across the Markdown repository by auditing structure, applying taxonomy tags, and enforcing linting rules.
Querying a Markdown knowledge base allows you to retrieve synthesized notes across topics. The system answers queries against the ingested wiki content, leveraging the cross-referenced wikilinks and structured taxonomy to return relevant information.
Yes, the wiki builder supports log rotation and frontmatter validation. It enforces a three-layer architecture of raw sources, wiki content, and schema while maintaining versioned history and auditing the structural consistency of the Markdown files.
Yes, you can use Obsidian with an interlinked Markdown wiki because the system generates standard Markdown files with wikilinks and taxonomy tagging. This format is fully compatible with Obsidian and similar knowledge-base tools for navigating cross-referenced notes.
A Markdown wiki needs a three-layer architecture to separate raw sources from the schema and final wiki content. This separation ensures that ingested knowledge remains structured, cross-referenced pages stay consistent, and the persistent knowledge base maintains its integrity during queries.
ryancnelsonDelegate Confluence wiki operations to a specialized sub-agent with structured JSON outputs.
Strategic-AutomationIngest sources into an interlinked Markdown wiki with linting and queries.
AissenLiuIngests sources into a persistent, interlinked Markdown wiki with YAML frontmatter.
anilcan-karaOrganize and maintain an interlinked Markdown wiki with frontmatter metadata and taxonomy tagging.
