tldr

Generate code trees, structure maps, and call graphs via the tldr CLI.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill tldr-jsai23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tldr
Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/util/skills/tldr
Command: npx skills add https://github.com/JSai23/claude-tooling --skill tldr-jsai23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token-efficient code analysis reference designed to provide structured intelligence about large codebases without bloating prompts, helping developers make better decisions with limited context.

Core Features & Use Cases

  • Provides file trees, code structure maps, and cross-file call graphs via the tldr CLI.
  • Supports analysis across languages (Python, TypeScript, Go, Rust) with focused tooling for structure, imports, and flows.
  • Use cases include understanding architecture, identifying hotspots, and guiding refactors with compact, token-efficient outputs.

Quick Start

Run tldr on your repository to generate a concise codebase map and call-graph.

Frequently Asked Questions about tldr

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

FAQPage Schema
How do I analyze a large codebase without exceeding token limits?

Token-efficient code analysis solves this by generating concise code trees, structure maps, and cross-file call graphs. This compact output delivers structured code intelligence without bloating prompts.

How do I generate a call graph across multiple files in a Python project?

Cross-file call graphs for Python projects are generated by running the tldr CLI. It maps function calls and control flows across files, producing a compact structure map of your codebase architecture.

Does this code analysis tool support TypeScript and Go projects?

Yes, the code analysis tool supports TypeScript, Go, and Rust projects alongside Python. It provides focused tooling for structure, imports, and control flows across all supported languages.

What is the best way to understand code structure before refactoring?

Generating a code structure map is the best way to understand architecture before refactoring. It identifies hotspots and visualizes imports and flows, guiding refactors with token-efficient outputs.

Do I need to install the tldr CLI to use this code analysis Skill?

Yes, you need the tldr CLI installed and available on your PATH to use this Skill. It executes commands like tree, structure, search, extract, and context to analyze your repository.

Why does analyzing large repositories fail with standard code search?

Standard code search bloats prompts with excessive tokens, breaking context limits. Token-efficient analysis prevents this by extracting only structured intelligence, delivering compact call graphs and structure maps.