hiivmind-corpus-add-source

Name: hiivmind-corpus-add-source
Availability: InStock
Author: hiivmind

Add documentation sources to a corpus via CLI-guided prompts and config.yaml updates.

1|Updated Dec 7, 2025

Search Tags:#git #documentation #semantic-search #corpus #content-indexing #web-sources #source-management

Ready to run

npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-add-source

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hiivmind-corpus-add-source
Source: https://github.com/hiivmind/hiivmind-corpus/tree/main/skills/hiivmind-corpus-add-source
Command: npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-add-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through adding a new documentation source to a corpus, handling type detection, extraction settings, and config updates to expand a corpus efficiently.

Core Features & Use Cases

Phase-driven workflow for adding sources (git, local, web, Obsidian vaults, llms-txt, generated-docs, and PDFs).
Automatic source typing, extraction configuration, and config.yaml updates to keep corpora up to date.
Error handling and post-setup guidance to assist navigation and indexing.

Quick Start

Run hiivmind-corpus-add-source in your project directory and follow the prompts to add a new source.

Frequently Asked Questions about hiivmind-corpus-add-source

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

FAQPage Schema

How do I add a new documentation source to an existing corpus?▼

To add a new documentation source to your corpus, run the tool in your project directory and follow the CLI-guided prompts to collect source metadata, handle conflicts, and write the new entry into config.yaml.

What documentation source types are supported for corpus content indexing?▼

Corpus content indexing supports git, local, web, Obsidian vaults, llms-txt, generated-docs, and PDFs, applying automatic source typing and extraction configuration during the discovery phase.

Do I need a config.yaml file to integrate a new documentation source?▼

Yes, you need a running config.yaml file and repository access to integrate a new documentation source, as the tool requires this environment to validate metadata and write the updated source configuration.

Can I use this tool to add an Obsidian vault as a web source for semantic search?▼

Yes, you can add an Obsidian vault as a recognized source type alongside git, web, and PDFs, enabling semantic search by updating the corpus config with the correct extraction settings.

What happens if there are source management conflicts when adding documentation?▼

During source management, the tool provides error handling and uses CLI-guided prompts to resolve conflicts, ensuring the new documentation source is validated before updating the config.yaml file.

What is the best way to manage web sources and local PDFs in a documentation corpus?▼

The best way to manage web sources and local PDFs in a documentation corpus is using a phase-driven workflow that automates type detection, extraction configuration, and config.yaml updates for efficient indexing.