Tldr Router
- 460 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
tldr-router is an agent skill that maps codebase exploration questions to the optimal tldr CLI command layer for file trees, call graphs, and complexity checks.
About
tldr-router is a parcadei/continuous-claude-v3 smart router that picks the right tldr command for a developer question. It maps file and function discovery to tldr tree and tldr structure, call relationship queries to tldr context and tldr calls, and complexity checks to tldr cfg. Example invocations include tldr tree with --ext filters, tldr structure src/ --lang python for class overview, tldr context with --depth for call chains, and tldr cfg for cyclomatic complexity of a function. Developers and coding agents reach for tldr-router at the start of repo exploration or architecture triage when manual grep would be slower than layered tldr commands.
- tldr-router
Tldr Router by the numbers
- 460 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #902 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill tldr-routerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 460 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
Which tldr command should I use for repo exploration?
Use tldr-router for development tasks
Who is it for?
Developers and agents exploring unfamiliar repositories who need the correct tldr command for orientation or call-graph questions.
Skip if: Codebases without the tldr CLI installed or tasks requiring full semantic search outside tldr's command set.
When should I use this skill?
A developer asks what files exist, who calls a function, or how complex a symbol is in a tldr-enabled repo.
What you get
Selected tldr CLI invocations with correct flags for tree, structure, context, calls, or complexity queries.
- Routed tldr command invocations
- Exploration output from tree, context, or cfg
By the numbers
- Maps questions to 5 tldr command families: tree, structure, context, calls, and cfg
Files
TLDR Smart Router
Maps questions to the optimal tldr command. Use this to pick the right layer.
Question → Command Mapping
"What files/functions exist?"
tldr tree . --ext .py # File overview
tldr structure src/ --lang python # Function/class overviewUse: Starting exploration, orientation
"What does X call / who calls X?"
tldr context <function> --project . --depth 2
tldr calls src/Use: Understanding architecture, finding entry points
"How complex is X?"
tldr cfg <file> <function>Use: Identifying refactoring candidates, understanding difficulty
"Where does variable Y come from?"
tldr dfg <file> <function>Use: Debugging, understanding data flow
"What affects line Z?"
tldr slice <file> <function> <line>Use: Impact analysis, safe refactoring
"Search for pattern P"
tldr search "pattern" src/Use: Finding code, structural search
Decision Tree
START
│
├─► "What exists?" ──► tree / structure
│
├─► "How does X connect?" ──► context / calls
│
├─► "Why is X complex?" ──► cfg
│
├─► "Where does Y flow?" ──► dfg
│
├─► "What depends on Z?" ──► slice
│
└─► "Find something" ──► searchIntent Detection Keywords
| Intent | Keywords | Layer |
|---|---|---|
| Navigation | "what", "where", "find", "exists" | tree, structure, search |
| Architecture | "calls", "uses", "connects", "depends" | context, calls |
| Complexity | "complex", "refactor", "branches", "paths" | cfg |
| Data Flow | "variable", "value", "assigned", "comes from" | dfg |
| Impact | "affects", "changes", "slice", "dependencies" | slice/pdg |
| Debug | "bug", "error", "investigate", "broken" | cfg + dfg + context |
Automatic Hook Integration
The tldr-read-enforcer and tldr-context-inject hooks automatically: 1. Detect intent from your messages 2. Route to appropriate layers 3. Inject context into tool calls
You don't need to manually run these commands - the hooks do it for you.
Manual Override
If you need a specific layer the hooks didn't provide:
# Force specific analysis
tldr cfg path/to/file.py function_name
tldr dfg path/to/file.py function_name
tldr slice path/to/file.py function_name 42Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
Which tldr command shows files and functions?
tldr-router maps orientation questions to tldr tree for file overviews and tldr structure src/ --lang python for function and class listings in a project.
How does tldr-router handle call relationship questions?
tldr-router routes call questions to tldr context with --depth for chains and tldr calls for understanding architecture and entry points in a codebase.