Results for “document ingestion”

Build LlamaIndex applications that retrieve relevant material before generating answers, a method called RAG. Connect documents, websites, and databases to support document questions, conversational search, structured summaries, and checks of answer relevance and source consistency.

• Building question answering over internal documents
• Creating a chatbot that remembers the conversation
• Searching information across files, websites, and databases

Guides building AI applications that search documents before answering questions, an approach called RAG. Covers importing files and web data, creating searchable indexes, adding conversational interfaces, and evaluating whether answers match the retrieved material.

• Build a question-answering system for internal documents
• Create a chatbot that remembers conversation context
• Search information across files, web pages, and databases

Convert PDF, Office, and other documents into Markdown that preserves useful text structure. Use batch conversion and literature organization to prepare files for search, text analysis, or AI systems that retrieve information from documents.

• Convert PDF and Office files to Markdown
• Batch-convert a document folder
• Organize research papers with source metadata

Re-ingest-correctness SOP for production RAG. Activate when a calling agent builds, reviews, or debugs an ingestion pipeline that runs more than once over a changing corpus — scheduled re-index, incremental updates, CI re-ingest, or a "retrieval has duplicates / shows deleted docs" bug. Encodes the rule — **ingestion must be idempotent: a document's content hash decides insert/update/skip, so re-running over unchanged docs is a no-op** — plus the docstore + doc-hash upsert machinery (LlamaIndex `IngestionPipeline` + `DocstoreStrategy`), the delete-propagation problem, and cross-framework equivalents (LangChain `index()` + `RecordManager`, manual hash table). ENHANCE overlay over [[llamaindex]]: the IngestionPipeline exists in the base skill but the re-ingest-correctness contract is not surfaced.

The English summary is being prepared. Showing the original description.

Design scheduled AI workflows for document ingestion, batch processing, and model training using Prefect, Airflow, or Dagster. Compare orchestration tools and plan task dependencies, retries, caching, and monitoring through implementation fragments.

• Schedule document ingestion and RAG index refreshes
• Design batch workflows for LLM requests
• Connect model training with quality evaluation

Tune cognee ingestion speed, query response time, and LLM costs by adjusting concurrency, text chunk sizes, request limits, and model choices. Estimate ingestion costs before processing and assess options for background work and deployment scaling.

• Estimating costs before importing documents
• Adjusting ingestion speed and request limits
• Reducing query response time

Provides Retrieval-Augmented Generation (RAG) implementation patterns with LangChain4j for Java. Generates document ingestion pipelines, embedding stores, vector search, and semantic search capabilities. Use when building chat-with-documents systems, document Q&A over PDFs or text files, AI assistants with knowledge bases, semantic search over document repositories, or knowledge-enhanced AI applications with source attribution.

The English summary is being prepared. Showing the original description.

CRE Document Ingestion suite — 4 specialist skills for classifying and extracting structured data from deal documents including rent rolls, T-12 financials, and offering memoranda.

The English summary is being prepared. Showing the original description.

Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph. Use when chunking PDFs, HTML, plain text, or Markdown; extracting entities and relationships from text with an LLM (SimpleKGPipeline, neo4j-graphrag); loading JSON via apoc.load.json; building Document→Chunk→Entity graph structures; or connecting LangChain/LlamaIndex document loaders to Neo4j. Covers neo4j-graphrag SimpleKGPipeline, LLM Graph Builder web UI, entity resolution, chunking strategies, and graph schema design for RAG pipelines. Does NOT handle structured CSV/relational import — use neo4j-import-skill. Does NOT handle GraphRAG retrieval after ingestion — use neo4j-graphrag-skill. Does NOT handle vector index creation — use neo4j-vector-search-skill.

The English summary is being prepared. Showing the original description.

Data framework for building LLM applications with RAG. Specializes in document ingestion (300+ connectors), indexing, and querying. Features vector indices, query engines, agents, and multi-modal support. Use for document Q&A, chatbots, knowledge retrieval, or building RAG pipelines. Best for data-centric LLM applications.

The English summary is being prepared. Showing the original description.

Run cognee in Docker, starting with a prebuilt image for local document ingestion and questions. It also covers Docker Compose profiles for adding the UI, MCP server, Postgres, and Neo4j, plus persistent data storage.

• Try cognee locally using a prebuilt Docker image
• Test document ingestion and questions through the API
• Start the UI, MCP server, and databases with Docker Compose

Import text, files, URLs, repositories, and database content into cognee memory. This skill explains input handling, storage organization, extraction options, and cost estimates, while helping diagnose unsupported arguments and document update errors.

• Importing documents, URLs, or database content
• Organizing stored information by project or topic
• Estimating tokens and cost before importing

Build a workflow for importing large collections of audio, email, documents, or chats into knowledge pages. Test varied samples first, track progress in a persistent JSON file, and verify outputs before marking work complete.

• Importing a large email export into knowledge pages
• Converting document collections into linked pages
• Resuming imports that span multiple sessions

Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows. USE FOR: ManagedCode.MarkItDown integration; document ingestion flows; Office or rich-text conversion to Markdown; indexing and summarization pipelines. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.

• Saving documents and conversations to a knowledge base
• Consolidating duplicate notes
• Synchronizing knowledge across storage systems

Turn a captured source document into linked LLM Wiki pages for sources, entities, concepts, and combined insights. Update the index and log, preserve the original material, and flag contradictions with existing knowledge instead of silently replacing it.

• Adding a captured document to an LLM Wiki
• Organizing people, organizations, and concepts
• Recording conflicts with existing wiki information

Organize research sources in self-hosted Open Notebook, then search them, ask questions with citations, create notes, transform text, or generate podcasts with multiple speakers. Supports REST API automation and configuration of local or cloud AI providers.

• Collect PDFs and web sources in a research notebook
• Ask questions about selected sources with citations
• Apply custom summaries and text transformations

Create and review company procedures and operational guides, then audit internal wikis for outdated pages, missing owners, broken connections, and inconsistent terminology. Produce structured drafts, step checks, and a prioritized list of documents to improve.

• Drafting procedures for employee onboarding
• Checking operational guides before use
• Prioritizing outdated wiki pages for revision

Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.

• Preparing a final penetration test report
• Rewriting an executive summary for nontechnical readers
• Creating a reusable security reporting template

Building robust document ingestion — chunking, metadata, and multi-format pipelines for search and RAG.

The English summary is being prepared. Showing the original description.

Convert a document to clean markdown suitable for chunking and embedding in a RAG pipeline.

The English summary is being prepared. Showing the original description.

Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.

The English summary is being prepared. Showing the original description.

Operate cognee from the terminal to store, retrieve, update, and remove information. Covers dataset and configuration management, ingestion cost estimates, session history access, and commands for inspecting or applying database migrations.

• Storing documents and asking questions from the terminal
• Estimating token usage and cost before importing data
• Managing datasets and saved configuration

Route articles, meeting notes, videos, documents, and conversations to specialized workflows for saving in GBrain. Preserve sources, add citations, and update related people, companies, concepts, and timelines with links back to the saved material.

• Save an article with its sources and related concepts
• Update attendee pages from meeting notes
• Organize video and podcast transcripts