obsidian-wiki-ingest

Ingest documents into an Obsidian wiki with deduplication and cross-links.

Updated Apr 27, 2014
One-click install
npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill obsidian-wiki-ingest-nirajkashyap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-wiki-ingest
Source: https://github.com/Nirajkashyap/nirajkashyap.github.io/tree/main/.agents/skills/obsidian-wiki-ingest
Command: npx skills add https://github.com/Nirajkashyap/nirajkashyap.github.io --skill obsidian-wiki-ingest-nirajkashyap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ingest documents into the Obsidian wiki project with deduplication, frontmatter validation, and cross-links; triggers on user request within the obsidian-wiki project context.

Core Features & Use Cases

  • Automated ingestion workflow that deduplicates sources using a manifest and frontmatter
  • Cross-link maintenance: creates or updates links between related wiki pages
  • Ingest mode flexibility: supports append, full, or raw modes depending on changes

Quick Start

Ingest documents into the Obsidian wiki, deduplicate with a manifest, and maintain cross-links.

Frequently Asked Questions about obsidian-wiki-ingest

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

FAQPage Schema
How do I ingest documents into an Obsidian wiki without creating duplicate entries?

Ingest documents into the Obsidian wiki with automated deduplication by using a manifest and frontmatter validation. The workflow checks existing sources and coordinates updates via append, full, or raw modes to prevent duplicate wiki pages.

What's the best way to maintain cross-links between related Obsidian wiki pages during ingestion?

Maintain cross-links during wiki ingestion by triggering the automated workflow, which validates vault paths and automatically creates or updates links between related wiki pages as new or modified sources are processed.

What is the difference between append, full, and raw modes for Obsidian wiki ingestion?

Append, full, and raw modes are ingestion options that handle new or modified sources differently. These modes determine how document content is processed and written into the Obsidian vault during the wiki-ingest workflow.

Do I need to validate frontmatter and vault paths before ingesting content into an Obsidian wiki?

Frontmatter validation and vault path validation are required steps before ingestion. The workflow checks these automatically to ensure sources are correctly formatted and directed to valid locations within the Obsidian wiki project workspace.

Why does my Obsidian wiki ingestion workflow require a manifest for deduplication?

A manifest is required for deduplication because it tracks previously ingested sources. By checking the manifest against new or modified documents, the workflow prevents duplicate entries and properly logs all updates within the Obsidian wiki.