upload-ingest

Convert local documents to Markdown, chunk content, and ingest into Milvus.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mengsi16/brain-base --skill upload-ingest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upload-ingest
Source: https://github.com/mengsi16/brain-base/tree/main/skills/upload-ingest
Command: npx skills add https://github.com/mengsi16/brain-base --skill upload-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When upload-agent receives a local document ingestion request, this workflow triggers the doc-converter for format conversion and dispatches the results to knowledge-persistence for chunking and Milvus ingestion. It runs in parallel with get-info-workflow and avoids external补库 chains.

Core Features & Use Cases

  • Validates input files and supported formats, coordinating a robust end-to-end ingest workflow.
  • Dispatches doc-converter to convert documents to a common Markdown representation and prepares raw/archived outputs.
  • Coordinates knowledge-persistence to chunk content, generate QA-ready frontmatter, and perform Milvus ingestion.
  • Returns an ingestion summary with per-document results and failure details to enable retry and auditing.

Quick Start

Provide local document paths to ingest and the system will validate, convert formats, generate frontmatter, chunk, and store results.

Frequently Asked Questions about upload-ingest

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

FAQPage Schema
How do I ingest local documents into Milvus for vector search?

Document chunking and Milvus ingestion prepare local files by converting them to Markdown, generating QA-ready frontmatter, and splitting content into chunks for vector database storage. This process produces queryable knowledge assets without requiring external web research.

How do I batch import a directory of local files for vector database storage?

Batch import local file directories by providing directory paths to the ingestion workflow. The system validates supported formats across the directory, triggers doc-converter for Markdown conversion, and coordinates chunking and Milvus ingestion, returning a summary with per-document results and failure details.

What file formats are supported for document ingestion and conversion to Markdown?

Document ingestion validates input files against supported formats before triggering doc-converter. The doc-converter transforms valid local documents into a common Markdown representation, preparing raw and archived outputs for downstream chunking and Milvus vector database ingestion.

Does the document ingestion workflow require external web research to process files?

No, the document ingestion workflow processes local files end-to-end without requiring external web research. It handles format validation, Markdown conversion, frontmatter generation, chunking, and Milvus persistence entirely through internal orchestration of doc-converter and knowledge-persistence components.

How do I handle failed document ingestion when uploading files to Milvus?

Failed document ingestion attempts are captured in the returned ingestion summary, which includes per-document results and specific failure details. This enables targeted retry and auditing of individual files without reprocessing the entire batch import directory.