developing-llamaindex-systems
Production-grade agentic system development with LlamaIndex in Python. Covers semantic ingestion (SemanticSplitterNodeParser, CodeSplitter, IngestionPipeline), retrieval strategies (BM25Retriever, hybrid search, alpha weighting), PropertyGraphIndex with graph stores (Neo4j), context RAG (RouterQueryEngine, SubQuestionQueryEngine, LLMRerank), agentic orchestration (ReAct, Workflows, FunctionTool), and observability (Arize Phoenix). Use when asked to "build a LlamaIndex agent", "set up semantic...
Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security
Installation for Agentic Skill
View all platforms →skilz install SpillwaveSolutions/developing-llamaindex-systems/developing-llamaindex-systemsskilz install SpillwaveSolutions/developing-llamaindex-systems/developing-llamaindex-systems --agent opencodeskilz install SpillwaveSolutions/developing-llamaindex-systems/developing-llamaindex-systems --agent codexskilz install SpillwaveSolutions/developing-llamaindex-systems/developing-llamaindex-systems --agent geminiFirst time? Install Skilz: pip install skilz
Works with 14 AI coding assistants
Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...
Extract and copy to ~/.claude/skills/ then restart Claude Desktop
git clone https://github.com/SpillwaveSolutions/developing-llamaindex-systemscp -r developing-llamaindex-systems ~/.claude/skills/Need detailed installation help? Check our platform-specific guides:
Related Agentic Skills
mastering-langgraph
by SpillwaveSolutions
Build stateful AI agents and agentic workflows with LangGraph in Python. Covers tool-using agents with LLM-tool loops, branching workflows, convers...
using-claude-code-cli
by SpillwaveSolutions
Invoke Claude Code CLI from Python orchestrators and shell scripts. Use when asked to"spawn claude as subprocess", "automate claude cli", "run cla...
python-testing
by athola
Python testing with pytest, fixtures, mocking, and TDD workflows.Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage,te...
python-async
by athola
Master Python asyncio, concurrent programming, and async/await patternsfor high-performance applications.Triggers: asyncio, async/await, coroutines...
Agentic Skill Details
- Owner
- SpillwaveSolutions (GitHub)
- Repository
- developing-llamaindex-systems
- Forks
- 1
- Type
- Technical
- Meta-Domain
- development
- Primary Domain
- python
- Market Score
- 99
Agent Skill Grade
A Score: 99/100 Click to see breakdown
Score Breakdown
Areas to Improve
- Missing TOC in SKILL.md
- Verbose complete examples
- Limited input/output examples
Recommendations
- Add trigger phrases to description for discoverability
- Add table of contents for files over 100 lines
Graded: 2026-01-19
Developer Feedback
I took a look at your developing-llamaindex-systems skill and wanted to share some thoughts.
Links:
The TL;DR
You're at 99/100, solid A territory. This is based on Anthropic's best practices for Claude Code skills. Your strongest area is Spec Compliance (15/15) — frontmatter is clean, triggers are specific, and the skill metadata is dialed in. The weakest spot is Writing Style (9/10), mostly around code example length rather than clarity.
What's Working Well
- Trigger coverage is excellent — You've got 15+ activation phrases like "build a LlamaIndex agent," "implement hybrid search," and specific component names (PropertyGraphIndex, SemanticSplitterNodeParser). This means developers will actually find this skill when they need it.
- Progressive Disclosure architecture is solid — 509-line SKILL.md as hub with 6 focused reference files (400-600 lines each) plus executable scripts. That's the right structure for token efficiency.
- Decision trees + Troubleshooting pattern works — The Diagnose→Fix→Verify flow is practical. You're not just explaining concepts; you're giving people a path to solve problems.
- Real problem coverage — Semantic chunking, knowledge graphs, query routing, observability. You're hitting gaps that actually exist in how people use LlamaIndex.
The Big One: Add a Table of Contents to SKILL.md
Why it matters: SKILL.md is 509 lines but jumps straight into content. Developers skimming your skill can't quickly navigate to what they need. This is friction in a document that long.
The fix: Add a ## Contents section right after the title listing all major sections: Quick Start, Architecture Overview, Decision Trees, Common Patter...
AI-Detected Topics
Extracted using NLP analysis
Browse Category
More development Agentic SkillsReport Security Issue
Found a security vulnerability in this agent skill?
Report Security Issue
Reporting issue with:
developing-llamaindex-systems
https://github.com/SpillwaveSolutions/developing-llamaindex-systemsThank you for helping keep SkillzWave secure. We'll review your report and take appropriate action.
Note: For critical security issues that require immediate attention, please also email security@skillzwave.ai directly.