Skill Detail

Build managed document parsing pipelines with LlamaCloud Services

Use LlamaCloud Services to parse, index, and manage document knowledge pipelines that feed LlamaIndex retrieval and agent workflows.

Data Extraction & TransformationMulti-Framework
Data Extraction & Transformation Multi-Framework Security Reviewed
⭐ 4.3k GitHub stars ⬇ 83k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill build-managed-document-parsing-pipelines-with-llamacloud-services Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
LlamaCloud Services client, LlamaCloud account/API access, documents or datasets to parse and index
Install & setup
Install the LlamaCloud Services client package, configure LlamaCloud credentials, then use the documented examples to parse documents, manage indexes, and connect outputs to LlamaIndex retrieval workflows.
Author
Run Llama
Publisher
Open Source Project
Last updated
Jun 2, 2026
Quick brief

Use LlamaCloud Services when an operator needs a managed LlamaIndex path for turning files into parsed, indexed, agent-ready knowledge. The workflow is to configure the LlamaCloud client, submit documents or datasets, run parsing and extraction, create or update indexes, and expose the resulting knowledge to retrieval agents or downstream review. Operators can monitor ingestion status, retry failed files, compare parsed output against source documents, and refresh indexes when source material changes. This belongs in ASE because the repeatable skill is not the cloud product by itself: it is the operator pipeline for moving documents through parsing, indexing, and retrieval handoff with source-backed setup. Invoke it instead of using the service manually when agents need a reproducible ingestion path that can be rerun, monitored, and connected to LlamaIndex applications. Keep the boundary at document knowledge operations, not broad cloud account administration. Document the source collection, parsing settings, index target, and downstream retrieval consumer for each run.