llm-tldr

Compresses code from 16 languages into token-efficient, fast-queryable summaries for AI agents.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/lev-os/lev-content --skill llm-tldr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-tldr
Source: https://github.com/lev-os/lev-content/tree/main/sources/skills/lev-find-llm-tldr
Command: npx skills add https://github.com/lev-os/lev-content --skill llm-tldr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the challenge of AI agents struggling with large codebases by providing highly compressed and rapidly searchable code intelligence, drastically reducing token usage and query times.

Core Features & Use Cases

  • Token Optimization: Achieves up to 95% token savings by analyzing code into structured formats.
  • Speed Enhancement: Delivers 300x faster queries compared to raw code analysis.
  • Codebase Understanding: Enables AI agents to perform tasks like debugging, refactoring, and semantic search across multiple languages.
  • Use Case: An AI agent needs to debug a complex issue in a large Python project. Instead of processing thousands of lines, it uses llm-tldr to get a concise, relevant code context, significantly speeding up the debugging process.

Quick Start

Use llm-tldr to get a summary of the main function in the current project.

Frequently Asked Questions about llm-tldr

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

FAQPage Schema
How do I reduce token usage when AI agents analyze large codebases?

To reduce token usage during codebase analysis, you can compress code into structured formats using AST analysis and call graphs. This approach achieves up to 95% token savings, enabling efficient semantic search and debugging across 16 languages without hitting context limits.

What is the best way to speed up semantic search and debugging in large multi-language projects?

The best way to speed up semantic search and debugging is generating compressed code intelligence via program slicing and data flow analysis. This method delivers queries 300x faster than raw code analysis, providing concise contextual insights for AI agents.

Can I use AST analysis and call graphs to optimize refactoring tasks across different programming languages?

Yes, AST analysis and call graphs can optimize refactoring tasks across 16 programming languages. By extracting structured code intelligence and control flow data, AI agents query relevant contexts rapidly, bypassing the need to process raw codebases entirely.

Does token optimization for code analysis work without hitting context window limits?

Token optimization for code analysis works without hitting context limits by compressing codebases into fast-queryable intelligence structures. Analyzing control flow and data flow reduces the token payload by 95%, ensuring AI agents stay within operational context windows.

How do I query program slicing and data flow logic for complex debugging tasks?

Querying program slicing and data flow logic for debugging requires pre-computed code intelligence structures. By compressing the codebase into structured formats, AI agents retrieve specific control flow paths instantly, bypassing thousands of lines of raw code.