tldr-overview
Get a token-efficient overview of any project using file tree, code structure, and call graph analysis.
Best use case
tldr-overview is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Get a token-efficient overview of any project using file tree, code structure, and call graph analysis.
Teams using tldr-overview should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tldr-overview/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tldr-overview Compares
| Feature / Agent | tldr-overview | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Get a token-efficient overview of any project using file tree, code structure, and call graph analysis.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# TLDR Project Overview
Get a token-efficient overview of any project using the TLDR stack.
## Trigger
- `/overview` or `/tldr-overview`
- "give me an overview of this project"
- "what's in this codebase"
- Starting work on an unfamiliar project
## Execution
### 1. File Tree (Navigation Map)
```bash
tldr tree . --ext .py # or .ts, .go, .rs
```
### 2. Code Structure (What Exists)
```bash
tldr structure src/ --lang python --max 50
```
Returns: functions, classes, imports per file
### 3. Call Graph Entry Points (Architecture)
```bash
tldr calls src/
```
Returns: cross-file relationships, main entry points
### 4. Key Function Complexity (Hot Spots)
For each entry point found:
```bash
tldr cfg src/main.py main # Get complexity
```
## Output Format
```
## Project Overview: {project_name}
### Structure
{tree output - files and directories}
### Key Components
{structure output - functions, classes per file}
### Architecture (Call Graph)
{calls output - how components connect}
### Complexity Hot Spots
{cfg output - functions with high cyclomatic complexity}
---
Token cost: ~{N} tokens (vs ~{M} raw = {savings}% savings)
```
## When NOT to Use
- Already familiar with the project
- Working on a specific file (use targeted tldr commands instead)
- Test files (need full context)
## Programmatic Usage
```python
from tldr.api import get_file_tree, get_code_structure, build_project_call_graph
# 1. Tree
tree = get_file_tree("src/", extensions={".py"})
# 2. Structure
structure = get_code_structure("src/", language="python", max_results=50)
# 3. Call graph
calls = build_project_call_graph("src/", language="python")
# 4. Complexity for hot functions
for edge in calls.edges[:10]:
cfg = get_cfg_context("src/" + edge[0], edge[1])
```Related Skills
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity
tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.
tldr-deep
Run full 5-layer analysis (AST, call graph, CFG, DFG, slice) on a specific function for deep debugging or understanding.
tldr-code
Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.
system_overview
Show how Continuous Claude works - the opinionated setup with hooks, memory, and coordination.
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.