Tldr Overview Skill for Claude
Get a token-efficient overview of any project using the TLDR stack
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill tldr-overviewThe instruction itself
10 sections, as written by the authorTLDR 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])
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take parcadei/tldr-overview from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.