tldr-overview
Quickly map out a new codebase's structure, architecture, and complexity areas.
Install
mkdir -p .claude/skills/tldr-overview && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4065" && unzip -o skill.zip -d .claude/skills/tldr-overview && rm skill.zipInstalls to .claude/skills/tldr-overview
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Get a token-efficient overview of any project using the TLDR stackKey capabilities
- →Generate project file tree
- →Extract code structure including functions and classes
- →Build cross-file call graphs
- →Identify high-complexity code hot spots
How it works
It maps the project by generating a file tree, extracting code structure, building a call graph, and calculating cyclomatic complexity for key functions.
Inputs & outputs
When to use tldr-overview
- →Onboarding to a new project
- →Mapping project architecture
- →Identifying high-complexity code areas
- →Documenting project structure
About this skill
TLDR Project Overview
Get a token-efficient overview of any project using the TLDR stack.
Trigger
/overviewor/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)
tldr tree . --ext .py # or .ts, .go, .rs
2. Code Structure (What Exists)
tldr structure src/ --lang python --max 50
Returns: functions, classes, imports per file
3. Call Graph Entry Points (Architecture)
tldr calls src/
Returns: cross-file relationships, main entry points
4. Key Function Complexity (Hot Spots)
For each entry point found:
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
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])
When not to use it
- →When already familiar with the project
- →When working on a specific file
- →When analyzing test files
Limitations
- →Test files are excluded from the overview
- →Complexity analysis is limited to identified entry points
How it compares
It provides a structured architectural overview rather than requiring manual exploration of individual files.
Compared to similar skills
tldr-overview side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tldr-overview (this skill) | 1 | 6mo | Review | Beginner |
| fact-check | 7 | 7mo | Review | Intermediate |
| agent-researcher | 4 | 6mo | Review | Intermediate |
| research-engineer | 2 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
fact-check
leonardomso
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation
agent-researcher
ruvnet
Agent skill for researcher - invoke with $agent-researcher
research-engineer
davila7
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
research-reviewer
galz10
Expertise in reviewing technical research for objectivity, evidence, and completeness. Use to ensure the "Documentarian" standard is met.
learn-from-pr
dotnet
Analyzes a completed PR to extract lessons learned from agent behavior. Use after any PR with agent involvement - whether the agent failed, succeeded slowly, or succeeded quickly. Identifies patterns to reinforce or fix, and generates actionable recommendations for instruction files, skills, and documentation.
skill-neovim-research
benbrastmckie
Research Neovim APIs, plugin patterns, and Lua development. Invoke for lua-language research tasks.