cc-insights

Index and analyze Claude Code conversation histories for semantic search and insights.

7|3|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/cskiro/annex --skill cc-insights
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-insights
Source: https://github.com/cskiro/annex/tree/main/skills/cc-insights
Command: npx skills add https://github.com/cskiro/annex --skill cc-insights

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sentence-transformers, chromadb, jinja2, click, python-dateutil, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automate analysis of Claude Code conversations to surface patterns, file hotspots, and actionable insights with a semantic search interface.

Core Features & Use Cases

  • RAG-Powered Semantic Search: Find conversations by meaning, not just keywords
  • Automatic Insight Reports: Pattern detection and trend visuals
  • Dashboard-friendly: Interactive views for ongoing monitoring

Quick Start

Process Claude Code conversations in your project, then search or generate weekly insights.

Frequently Asked Questions about cc-insights

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

FAQPage Schema
How do I search Claude Code conversations by meaning instead of keywords?

Semantic search uses sentence-transformers to convert conversations into vector embeddings stored in ChromaDB, enabling you to find relevant discussions by intent rather than exact phrase matches. This skill indexes your project histories automatically and supports fast retrieval by topic.

Can I analyze conversation patterns across my Claude Code project history?

Yes, this skill indexes conversations from ~/.claude/projects incrementally and detects patterns to generate automated insights, including weekly reports, file heatmaps, and trend analysis that surface which files and topics dominate your interactions.

What's the best way to identify file hotspots in my Claude Code workflow?

File heatmaps visualize which files appear most frequently across your conversations, helping you spot areas needing attention. The skill generates these automatically during analysis using incremental indexing of your project histories.

Do I need to manually index my conversations or does this happen automatically?

Indexing is incremental and automated. The skill processes conversations from your project directory, updates the vector database, and prepares data for search and reporting without requiring manual intervention between runs.

Can I generate weekly reports from my conversation data?

Yes, this skill generates weekly insight reports using Jinja2 templating and pattern detection. Reports extract trends and actionable findings from indexed conversations, formatted for dashboard integration and team sharing.

What prerequisites do I need before using semantic search on conversations?

You need Claude Code conversations stored in ~/.claude/projects. The skill handles environment setup including ChromaDB initialization, sentence-transformer model loading, and incremental indexing—no manual database configuration required.