Provides chunking strategies for RAG systems. Generates chunk size recommendations (256-1024 tokens), overlap percentages (10-20%), and semantic boundary detection methods. Validates semantic coherence and evaluates retrieval precision/recall metrics.
SkillScore83Maintained
Automatic
◆AI Engineer pack
Last verified 8/21/2026
What it changes
Passed 19 of 23 test cases with the skill, and 13 of 23 without it.
Without skill57%
With skill83%
Checks it passed that the model alone missed
Specifies 256 tokens for factoid queries.
Specifies 1024 tokens for analytical queries.
Recommends reducing chunk_size by 25 percent.
and 8 more in the full report
6 fixed13 passed either way4 still failing0 broke
Pass-rate lift
+26 pp
Tokens
+55%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/21/2026v119 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
After evaluating our RAG pipeline output on a evaluation dataset, our precision score came back at 0.58, well below our target. The team wants to increase chunk size to 2048 to give the LLM more background. What specific action should we take according to standard chunk tuning procedures?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends reducing chunk_size by 25 percent.
Missed
Passed
case-12 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md189 lines9 files
Chunking Strategy for RAG Systems
Overview
Provides chunking strategies for RAG systems, vector databases, and document processing. Recommends chunk sizes, overlap percentages, and boundary detection methods; validates semantic coherence; evaluates retrieval metrics.
When to Use
Use when building or optimizing RAG systems, vector search pipelines, document chunking workflows, or performance-tuning existing systems with poor retrieval quality.
Instructions
Choose Chunking Strategy
Select based on document type and use case:
Fixed-Size Chunking (Level 1)
Use for simple documents without clear structure
Start with 512 tokens and 10-20% overlap
Adjust: 256 for factoid queries, 1024 for analytical
Recursive Character Chunking (Level 2)
Use for documents with structural boundaries
Hierarchical separators: paragraphs → sentences → words
Customize for document types (HTML, Markdown, JSON)
Structure-Aware Chunking (Level 3)
Use for structured content (Markdown, code, tables, PDFs)
Provides GitHub Copilot CLI task delegation in non-interactive mode with multi-model support (Claude, GPT, Gemini), permission controls, output sharing, and session resume. Use when users ask to hand work to Copilot, compare models, or run Copilot programmatically from Claude Code.