rag-knowledge-capture-cli

Convert Claude Code CLI sessions into self-contained Markdown chunks for Qdrant embeddings.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/figulazmi/token-monitor --skill rag-knowledge-capture-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rag-knowledge-capture-cli
Source: https://github.com/figulazmi/token-monitor/tree/main/.claude/skills/rag-knowledge-capture-cli
Command: npx skills add https://github.com/figulazmi/token-monitor --skill rag-knowledge-capture-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Claude Code CLI sessions into RAG-optimized, independently embeddable knowledge chunks to feed retrieval systems like Qdrant. It ensures each chunk is self-contained and ready for embedding, saving to .claude/summaries and signaling push to qdrant.sh, while integrating with the CLAUDE.md Session End Protocol.

Core Features & Use Cases

  • RAG-ready chunks: Produces self-contained Markdown chunks per problem-solution pair suitable for embedding.
  • Local persistence: Saves chunks to .claude/summaries with date-slug filenames for easy versioning and retrieval.
  • Workflow integration: Works with CLAUDE.md Session End Protocol to automate summarization before session end.
  • Push signaling: Outputs the exact push-to-qdrant.sh command to send chunks to the Qdrant collection.

Quick Start

Run this skill at the end of a Claude Code session to generate a knowledge document and save it under .claude/summaries with a date-slug filename.

Frequently Asked Questions about rag-knowledge-capture-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save Claude Code CLI sessions as RAG knowledge chunks?▼

To save Claude Code CLI sessions as RAG knowledge chunks, run this skill at session end to transform problem-solution pairs into self-contained 150–400 word Markdown documents. These standalone chunks are then saved to .claude/summaries using a date-slug filename for local persistence and easy retrieval.

How does generating embeddings from CLI sessions work with Qdrant?▼

Generating embeddings from CLI sessions with Qdrant involves creating self-contained Markdown chunks that are structurally optimized for embedding. The skill outputs a push-to-qdrant.sh command, providing the exact shell instruction needed to index the locally saved knowledge chunks into your Qdrant collection.

Does the Session End Protocol support automatic knowledge capture?▼

The Session End Protocol supports automatic knowledge capture by integrating directly with this skill. It triggers the summarization workflow before your Claude Code CLI session ends, ensuring that problem-solution pairs are automatically converted into embeddable chunks without manual intervention.

Can I use this skill to create self-contained chunks for retrieval systems?▼

You can use this skill to create self-contained chunks for retrieval systems by enforcing a strict frontmatter schema. It processes Claude Code sessions into standalone 150–400 word Markdown documents that carry full context independently, making them immediately ready for embedding and retrieval.

What is the best way to format Claude Code session summaries for Qdrant?▼

The best way to format Claude Code session summaries for Qdrant is to use a strict frontmatter schema and chunk them into 150–400 word self-contained documents. This skill applies that formatting automatically, saving the output to .claude/summaries to ensure optimal embedding quality and retrieval accuracy.

Do I need Qdrant installed to generate knowledge chunks from my sessions?▼

You do not need Qdrant installed to generate knowledge chunks, as the skill saves all output locally to .claude/summaries. However, to complete the pipeline and index the generated chunks, you will eventually need a Qdrant collection to execute the provided push-to-qdrant.sh command.