agentsclimarketplace

Llamaindex

Skill magnus919/agent-skills/llamaindex

Curated collection of AI agent skills for Hermes and other agent frameworks

Install
npx -y skills add magnus919/agent-skills --skill llamaindex

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Expert skill for building LLM applications with the LlamaIndex framework — RAG pipelines, multi-agent orchestration, event-driven workflows, knowledge graph construction, production deployment, and evaluation. Use when working with LlamaIndex or comparing RAG and agent orchestration frameworks.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

11.8 KB, as published. Nobody here has run it

LlamaIndex Expert Skill

LlamaIndex is an MIT-licensed Python framework for building LLM applications over your data. In 2026, it has evolved from a RAG indexing library into an event-driven workflow framework with integrated production runtime (llama-deploy), agent orchestration (AgentWorkflow), knowledge graph construction (PropertyGraphIndex), and OpenTelemetry-native observability.

The framework is organized around seven core primitives: Reader (data loaders), Document/Node (chunked content model), Index (data structures over Nodes), Retriever (relevant Node selection), Query Engine (retriever + synthesis), Agent (LLM with tools), and Workflow (event-driven orchestration).

Key Principles

These principles govern every decision when building with LlamaIndex. Read them before proceeding to the reference guides.

  1. Decouple retrieval chunks from synthesis chunks. The embedding representation that retrieves well differs from the context representation that generates well. Use SentenceWindowNodeParser + MetadataReplacementNodePostProcessor for this pattern.
  2. Rerank before you generate. Hybrid retrieval + reranker is the minimum viable production RAG configuration.
  3. Agents are Workflows. FunctionAgent and AgentWorkflow are pre-configured Workflows. Drop to raw Workflow when you need custom control flow.
  4. Graphs are not just vector stores. PropertyGraphIndex adds structural path traversal that vector similarity cannot provide — combine both for maximum retrieval quality.
  5. Evaluate in the same process. Span-attached evaluation preserves the connection between the output and the retrieval context that produced it.

Where to Start

The pipeline has 9 phases from Ingest to Deploy. If you're joining mid-stream with existing work, find your entry point:

You already have...Start at phaseWhat to do
Nothing — blank projectIngestSet up data loading, then proceed through the full pipeline
Documents in a directoryChunkChoose a chunking strategy, build your index
A working vector indexRetrieveAdd hybrid search, reranking, metadata filters
An existing RAG pipeline to hardenDeployAdd observability, llama-deploy, production debugging
A need to measure and improve qualityEvaluateSet up evaluators, ParamTuner, span-attached scoring
Nothing — comparing frameworksSee Framework Routing GuideDon't start the pipeline — pick the right tool first

Pipeline Mode

Different tasks need different levels of rigor. Match your scope to a mode:

ModeWhenPhases to runSkip
QuickSingle query, one source, explorationIngest → Chunk → Index → RetrieveReranking, metadata filters, observability, evaluation
FullProduction RAG, multiple sources, complianceIngest → Chunk → Index → Retrieve → Agent/Workflow → Deploy → EvaluateNothing — run all phases
EvaluateBenchmarking, regression testingIngest → Chunk → Index → EvaluateRetrieve, Agent, Workflow, Deploy (run offline)
GraphKnowledge graph constructionIngest → Chunk → Graph → RetrieveAgent, Workflow, Deploy (query via graph index directly)

Rule of thumb: if you're shipping to users, run Full mode. If you're exploring, run Quick. If you're measuring, run Evaluate.

Quick Reference

PhaseTaskApproachReference
IngestLoad dataSimpleDirectoryReader("./data").load_data()references/architecture.md
ChunkParse documents into nodesSentenceSplitter(chunk_size=1024)references/rag-strategies.md
IndexBuild vector indexVectorStoreIndex.from_documents(docs)references/rag-strategies.md
RetrieveHybrid search + rerankBM25Retriever + CohereRerankreferences/rag-strategies.md
AgentMulti-agent orchestrationAgentWorkflow(agents=[...])references/agent-patterns.md
WorkflowEvent-driven pipelineclass MyFlow(Workflow): @stepreferences/workflows.md
GraphKnowledge graphPropertyGraphIndex.from_documents(docs)references/property-graph-index.md
EvaluateRAG evaluationFaithfulnessEvaluator().evaluate_response(...)references/evaluation-observability.md
DeployProduction deploymentdeploy_workflow(workflow=MyFlow())references/production-deployment.md

When to Use This Skill

Load this skill any time you are:

  • Building a RAG pipeline over enterprise or personal data
  • Comparing LlamaIndex with LangChain, Haystack, or DSPy
  • Designing multi-agent systems with handoff between specialist agents
  • Deploying an LLM application to production with observability
  • Constructing knowledge graphs from unstructured documents
  • Debugging common LlamaIndex failures (retrieval miss, handoff bug, async issues)

When NOT to Use LlamaIndex — Framework Routing Guide

This skill is part of a portfolio of framework skills. When deciding which framework fits, use this routing table:

ScenarioReach forWhy
I have documents I need to queryLlamaIndexData ingestion, hybrid retrieval, reranking, and knowledge graphs are first-class primitives
I have agents I need to orchestrateLangGraphState-machine semantics, time-travel debugging, and human-in-the-loop pauses are the core design
I have a tool I need to wrap as an agentPydanticAIType-safe agent definitions with dependency injection, minimal abstraction over LLM calls
Data-heavy RAG over PDFs, SQL, Slack, 200+ sourcesLlamaIndexLlamaHub connectors, LlamaParse for documents, hybrid retrieval out of the box
Complex multi-agent state machines with checkpointsLangGraphGraph topology control — supervisor, subgraphs, hierarchical teams, built-in checkpointer
Agent-centric app where type safety matters more than data pipelinesPydanticAIAgents as Pydantic models, DI, structured outputs — the data layer is your code
Document parsing quality matters (tables, charts, handwriting)LlamaIndexLlamaParse is purpose-built for this
Production NLP search pipelinesHaystackPipeline composition model is more mature for search-specific workloads
Optimization-driven prompt programmingDSPyCompiled prompt programs, not retrieval pipelines

Reference Files

ReferenceLoad whenFile
Core ArchitectureUnderstanding the 7 primitives, Settings, data flowreferences/architecture.md
RAG StrategiesBuilding RAG pipelines from basic to advancedreferences/rag-strategies.md
Agent PatternsMulti-agent orchestration with AgentWorkflowreferences/agent-patterns.md
WorkflowsEvent-driven step composition and durable executionreferences/workflows.md
Production & Deploymentllama-deploy, debugging, failure modesreferences/production-deployment.md
Property Graph IndexKnowledge graph construction and hybrid retrievalreferences/property-graph-index.md
Evaluation & ObservabilityMetrics, tracing, span-attached scoringreferences/evaluation-observability.md
Integration EcosystemVector stores, LlamaHub, LlamaParse, ecosystemreferences/integration-ecosystem.md
FAQ & TroubleshootingCommon errors and their fixesreferences/faq-and-troubleshooting.md
Worked RAG ExampleComplete end-to-end pipeline from ingest to deployreferences/example-rag-pipeline.md
Evaluation WorkflowParamTuner, evaluators, batch scoring, best practicesreferences/evaluation-workflow.md

Template Files

TemplateWhen to useFile
Basic RAGSingle-source query, getting startedtemplates/basic-rag.py
Agentic RAGMulti-source data with agent routingtemplates/agentic-rag.py
Custom WorkflowCustom control flow, branching logictemplates/custom-workflow.py
Production DeployWrapping a workflow as a microservicetemplates/production-deploy.py

Scripts

ScriptPurposeFile
check-setupVerify LlamaIndex installation and configurationscripts/check-setup.py

Troubleshooting — Structured Recovery Guide

When something goes wrong, find your symptom and follow the recovery path:

Retrieval & Answer Quality

SymptomLikely causeImmediate fixPermanent fixReference
Answers are poor or hallucinatedNo reranker on hybrid retrievalAdd CohereRerank(top_n=5) as node_postprocessorReranking is mandatory for any production RAGreferences/rag-strategies.md
Retrieval misses obvious contentDefault chunking breaks semanticsSwitch to SemanticSplitterNodeParser(breakpoint_percentile_threshold=95)Tune chunk size with ParamTunerreferences/rag-strategies.md
Wrong tenant's data returnedMissing metadata filtersAdd MetadataFilters(filters=[ExactMatchFilter(key="tenant_id", ...)])Always wire metadata filters at retriever levelreferences/rag-strategies.md
Only one type of query works wellSingle retrieval strategyCombine BM25 + vector via hybrid retrieverAdd RouterQueryEngine for query-type routingreferences/rag-strategies.md

Agent & Workflow Failures

SymptomLikely causeImmediate fixPermanent fixReference
Agent waits silently after handoffAgentWorkflow handoff bugExtend FunctionAgent.take_step to re-locate last user messageApply the handoff fix on all production agentsreferences/agent-patterns.md
Workflow doesn't runForgot awaitAdd await before w.run(...) and all step callsAll step methods are async coroutinesreferences/workflows.md
Step executes but result is lostState not persistedUse ctx.store.edit_state() for shared stateOnly ctx.store survives across stepsreferences/workflows.md
Crash loses all progressNo checkpoint snapshotsAdd Context.to_dict() save on step completionDurable workflows need explicit checkpointingreferences/workflows.md

Deployment & Observability

SymptomLikely causeImmediate fixPermanent fixReference
llama-deploy deployed but requests time outRedis not runningStart redis-serverRedis is mandatory — control plane won't route without itreferences/production-deployment.md
Spans missing in observability UIInstrumentation called too lateMove instrument() call before workflow instantiationAlways instrument before creating any Workflow objectreferences/production-deployment.md
Wrong data returned (cross-tenant)Missing metadata filtersAdd tenant filter to all retrieversFilter at retriever level, not in post-processingreferences/production-deployment.md

Recovery Workflow

For any failure, follow this cycle:

  1. Identify the symptom from the tables above
  2. Apply the immediate fix — this gets you running
  3. Implement the permanent fix — this prevents recurrence
  4. Verify with evaluation — run FaithfulnessEvaluator on a held-out query set
  5. Document the fix — add the root cause to references/faq-and-troubleshooting.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.