Skip to main content
skill CX Codex

tldr-overview — Claude Code skill: project overview without token

The skill maps an unfamiliar project through the TLDR stack: file tree, code structure, call graph and complexity hot spots.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add parcadei/Continuous-Claude-v3 --skill tldr-overview -a claude-code
Open on GitHub

What tldr-overview does

Trigger it with /overview or /tldr-overview, or just ask for an overview of the project. The skill runs four steps: a file tree, functions and classes per file, a cross-file call graph, and cyclomatic complexity for the entry points it finds. Output lands in one block with Structure, Key Components, Architecture and Complexity Hot Spots sections, plus a line showing token cost against reading raw files.

Under the hood it shells out to tldr tree, tldr structure, tldr calls and tldr cfg. Language comes from a flag such as --lang python or --ext .py. There is a Python route too: get_file_tree, get_code_structure, build_project_call_graph and get_cfg_context from tldr.api. So the TLDR tool itself has to be installed, otherwise the steps have nothing to call.

The author lists when not to reach for it: you already know the project, you are working on one specific file, or you are in test files where full context matters. That last one is worth taking seriously — a structural summary of tests will miss what you actually need.

What it helps with

  • map an unfamiliar repo before the first edit
  • find entry points and how files connect
  • spot functions with high cyclomatic complexity
  • cut token spend on reading raw source
  • understand project layout before a refactor

Example prompts for the agent

  • /tldr-overview
  • give me an overview of this project
  • what's in this codebase

How to install tldr-overview

1Skills CLI (Vercel)

npx skills add parcadei/Continuous-Claude-v3 --skill tldr-overview -a claude-code

2Manually: put the files in place

~/.claude/skills/tldr-overview/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/tldr-overview/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about tldr-overview

How do I install tldr-overview in Claude?

Run npx skills add parcadei/Continuous-Claude-v3 --skill tldr-overview -a claude-code. The skill lands in ~/.claude/skills/tldr-overview/SKILL.md.

What does tldr-overview do?

It builds a project overview through the TLDR stack: file tree, code structure, call graph and complexity of key functions. You get a compact report instead of reading the whole repo.

What does the skill need to run?

A working TLDR install — the skill calls tldr tree, tldr structure, tldr calls and tldr cfg. Set the project language with a flag like --lang python.

Source text

SKILL.md · MIT
---
name: tldr-overview
description: Get a token-efficient overview of any project using the TLDR stack
---

# 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])
```

© parcadei · MIT · parcadei/Continuous-Claude-v3

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set77

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor