llamacloud

Plugin llamacloud from marketplace llamacloud-marketplace in jbaham2/llamacloud-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• liteparse

  This skill should be used when the user wants to "use LiteParse", "parse locally without an API key", do "offline/OSS document parsing", or work with the "LiteParse library/CLI/server/WASM". Owns local/OSS no-key document parsing and the LiteParse-vs-cloud-LlamaParse decision; defers cloud/agentic/s

• llamacloud-classify

  This skill should be used when the user wants to "classify documents", "route documents by type", define "document classification rules", or "categorize incoming files" with LlamaCloud Classify. Owns natural-language classification and intake routing; defers segmenting one file into sub-docs to llam

• llamacloud-extract

  This skill should be used when the user wants to "extract structured data from a document", "design/validate an extraction schema", write a "Pydantic/JSON/Zod extract schema", configure "LlamaExtract options/citations", or "pull typed fields from PDFs". Owns LlamaExtract v2 schema design and configu

• llamacloud-index

  This skill should be used when the user wants to "build a Cloud Index", set up a "managed RAG pipeline on LlamaCloud", configure "hybrid search / rerank / metadata filter on LlamaCloud", "ingest documents into a LlamaCloud index", or expose a "managed retrieval endpoint". Owns the end-to-end managed

• llamacloud-parse

  This skill should be used when the user wants to "parse a PDF/document", "use LlamaParse", choose between "LlamaParse tiers / agentic vs fast vs cost", "configure parse output (markdown/JSON)", or "retrieve/parse results". Owns LlamaParse v2 (GA) parsing decisions and config; defers typed-field extr

• llamacloud-self-hosting

  This skill should be used when the user wants to "self-host LlamaCloud", do a "BYOC deployment", "Helm/Kubernetes install LlamaParse/LlamaCloud", work out "self-hosting installation/hardware requirements", or "tune/monitor a self-hosted LlamaCloud". Owns operating the MANAGED LlamaCloud platform ins

• llamacloud-sheets

  This skill should be used when the user wants to "extract from spreadsheets", "use LlamaCloud Sheets", "reason over spreadsheet rows", or "pull tables from messy Excel/CSV" — detecting table regions in disorganized workbooks and turning them into normalized rows. Owns spreadsheet table extraction an

• llamacloud-split

  This skill should be used when the user wants to "split a document", "segment a concatenated/merged PDF", "break one file into logical sub-documents", or do "page/section splitting" of a single combined file into typed sections. It owns LlamaCloud Split (page-range segmentation of one bundled file)

• llamacloud

  This skill should be used when the user is getting started with LlamaCloud or LlamaParse, asks "which LlamaCloud product do I need", "how do I set up LlamaCloud", "get a LlamaCloud / LlamaParse API key", asks about LlamaCloud regions / EU data residency / pricing / credits, or needs routing across t

• llamaindex-cookbooks

  This skill should be used when the user asks "is there an example/cookbook/notebook for X", wants to "find a recipe/sample for this scenario", or says "show me a LlamaIndex example for …" — routing a described scenario to the most relevant LlamaParse cookbooks and LlamaIndex examples-gallery noteboo

• llamaindex-deploy

  This skill should be used when the user wants to "deploy a workflow/agent", "use llamactl", "serve a LlamaIndex Workflow as an HTTP API", or set up "agent deployment / continuous deploy" on LlamaCloud. Owns shipping a Workflow/agent as a running service (install/auth/init/serve/deploy via the CLI, t

• llamaindex-framework

  This skill should be used when the user wants to "build a RAG pipeline with LlamaIndex (OSS)", work with "VectorStoreIndex / query engine", follow the "load-index-store-query" model, consult "LlamaIndex component/module guides", or do "self-managed retrieval in code". Owns the open-source LlamaIndex

• llamaindex-workflows

  This skill should be used when the user wants to "build a LlamaIndex Workflow", design "event-driven agent steps", handle "workflow state / HITL / streaming", or "orchestrate agentic steps with Workflows". Owns the event-driven workflow model (events, steps, Context/state, branching, looping, human-

Slash commands (2)

• /llamacloud:llamacloud-setup

  Guided LlamaCloud onboarding — account, API key, region choice, SDK install, and a first-call smoke test.

• /llamacloud:llamacloud

  Router for the LlamaCloud / LlamaIndex plugin — describe what you're building and get pointed to the right product, skill, and next step.

Subagents (5)

• cookbook-scout

  Use this agent when the user wants to find existing LlamaIndex/LlamaParse examples or cookbooks that match a scenario. Typical triggers include "is there an example for building RAG over X", "find a cookbook for this extraction use case", "what notebooks cover agentic workflows", and "show me a samp

• extraction-schema-designer

  Use this agent when the user wants to design, draft, or validate a LlamaExtract extraction schema from real documents. Typical triggers include "design an extraction schema for these invoices", "what schema should I use to pull fields from this PDF", "review/validate my LlamaExtract Pydantic schema"

• rag-architect

  Use this agent when the user wants a designed RAG or retrieval pipeline and needs the architecture decided. Typical triggers include "design a RAG pipeline for my docs", "should I use Cloud Index or build retrieval myself", "choose chunking/embedding/retrieval settings for my corpus", and "architect

• self-hosting-doctor

  Use this agent when a self-hosted / BYOC LlamaCloud deployment is misbehaving and needs diagnosis. Typical triggers include "my self-hosted LlamaParse pods are crashing", "diagnose my BYOC LlamaCloud Helm deployment", "why is my self-hosted LlamaCloud failing to start", and "check my LlamaCloud Kube

• workflow-builder

  Use this agent when the user wants to scaffold a LlamaIndex Workflow or an agent deployment from a description. Typical triggers include "scaffold a LlamaIndex Workflow that does X", "build me an event-driven agent workflow", "turn this process into a Workflow", and "set up a workflow I can deploy".

MCP servers (1)

• docs

  connects to: https://developers.llamaindex.ai/mcp

Similar plugins