Back to skills
SKILL.md
Ingest Doc
ASecuritySingle-command document ingestion pipeline. Chains extractor → cui-marker → doc2qra → taxonomy → memory for PDFs and documents. Handles compliance, research, and general documents end-to-end.
- 6 stars
- 0 votes
- 0 copies
- 1 view
- Added September 11, 2026
Security analysis
100/100Pro scans all 6 files and shows the line behind each finding
npx -y skills add grahama1970/agent-skills --skill ingest-doc --agent claude-codeAre you the author of Ingest Doc?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/grahama1970-ingest-doc)---
name: ingest-doc
description: >
Single-command document ingestion pipeline. Chains extractor →
cui-marker → doc2qra → taxonomy → memory for PDFs and documents.
Handles compliance, research, and general documents end-to-end.
allowed-tools:
- run_command
- read_file
triggers:
- ingest document
- ingest compliance
- ingest nist
- ingest stig
- ingest cmmc
- compliance document
- ingest itar document
- compliance ingestion
- convert document to qras
- document to knowledge
metadata:
short-description: End-to-end document ingestion pipeline
provides:
- ingest-doc
composes:
- extractor
- doc2qra
- cui-marker
- taxonomy
- memory
- task-monitor
- agentic-evals
taxonomy:
- security
- compliance
disciplines:
- data-engineering
- extraction
---
> STOP. READ THIS ENTIRE SKILL.MD BEFORE CALLING ANY ENDPOINT.
# Ingest Document
Single command to ingest a PDF through the full pipeline:
```
PDF → extractor → cui-marker → doc2qra → taxonomy → memory
```
## Commands
| Command | Description |
|---------|-------------|
| `./run.sh ingest <path>` | Full pipeline on a PDF/URL |
| `./run.sh ingest <path> --preset nist_controls` | Force NIST control preset |
| `./run.sh ingest <path> --dry-run` | Show what would happen without executing |
| `./run.sh ingest <path> --skip-cui` | Skip CUI marking (for public documents) |
| `./run.sh batch <dir>` | Process all PDFs in a directory |
| `./run.sh status` | Show pipeline health (all skills available?) |
## Pipeline Stages
### Stage 1: Extract (extractor skill)
- Profile document to detect preset (nist_controls, requirements_spec, etc.)
- Extract sections, tables, figures via deterministic pipeline
- Output: structured JSON + markdown
### Stage 2: CUI Check (cui-marker skill)
- Scan extracted text for CUI indicators
- Apply appropriate markings
### Stage 3: QRA Extraction (doc2qra skill)
- Generate QRA triplets via LLM
- Persona-driven quality gating
- Grounding validation filters hallucinations
### Stage 4: Taxonomy (taxonomy skill)
- Extract federated taxonomy tags (bridges: Precision, Resilience, etc.)
### Stage 5: Memory Storage (memory skill)
- Store QRAs with taxonomy tags in ArangoDB
- Create graph edges between controls and requirements
## Supported Document Types
| Type | Detected By | Preset |
|------|------------|--------|
| NIST SP 800-171 | "NIST SP", control IDs (AC-*, SC-*) | nist_controls |
| NIST SP 800-53 | "NIST SP", control catalog format | nist_controls |
| DISA STIG | "STIG", V-number findings | requirements_spec |
| CMMC Assessment Guide | "CMMC", "Cybersecurity Maturity" | requirements_spec |
| ITAR/EAR Documents | Export control markers | requirements_spec |
| Engineering Specs | REQ-xxx, "Shall" language | requirements_spec |
| General PDF/markdown | Any document | auto |
Files in this skill
- SKILL.md
- fixtures/agentic_eval.json
- ingest_compliance.py
- pyproject.toml
- run.sh
- sanity.sh
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.