tldr-overview
Get a token-efficient overview of any project using file tree, code structure, and call graph analysis.
Profile →npx skills add vibeeval/vibecosystem --skill tldr-overview --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Trigger
- Execution
- 1. File Tree (Navigation Map)
- 2. Code Structure (What Exists)
- 3. Call Graph Entry Points (Architecture)
- 4. Key Function Complexity (Hot Spots)
- Output Format
- When NOT to Use
- Programmatic Usage
tldr tree . --ext .py # or .ts, .go, .rs tldr structure src/ --lang python --max 50 tldr calls src/ tldr cfg src/main.py main # Get complexity
What does the tldr-overview skill do?
Get a token-efficient overview of any project using file tree, code structure, and call graph analysis.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill tldr-overview --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.