tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.
Profile →npx skills add vibeeval/vibecosystem --skill tldr-router --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 Smart Router Maps questions to the optimal tldr command. Use this to pick the right layer. ## Question → Command Mapping ### "What files/functions exist?" ```bash tldr tree . --ext .py # File overview tldr structure src/ --lang python # Function/class overview ``` **Use:** Starting exploration, orientation ### "What does X call / who calls X?" ```bash tldr context <function> --project . --depth 2 tldr calls src/ ``` **Use:** Understanding architecture, finding entry points ### "How complex is X?" ```bash tldr cfg <file> <function> ``` **Use:** Identifying refactoring candidates, understanding difficulty ### "Where does variable Y come from?" ```bash tldr dfg <file> <function> ``` **Use:** Debugging, understanding data flow ### "What affects line Z?" ```bash tldr slice <file> <function> <line> ``` **Use:** Impact analysis, safe refactoring ### "Search for pattern P" ```bash 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
- Question → Command Mapping
- "What files/functions exist?"
- "What does X call / who calls X?"
- "How complex is X?"
- "Where does variable Y come from?"
- "What affects line Z?"
- "Search for pattern P"
- Decision Tree
- Intent Detection Keywords
- Automatic Hook Integration
- Manual Override
tldr tree . --ext .py # File overview tldr structure src/ --lang python # Function/class overview tldr context <function> --project . --depth 2 tldr calls src/ tldr cfg <file> <function> tldr dfg <file> <function> tldr slice <file> <function> <line> tldr search "pattern" src/ Force specific analysis tldr cfg path/to/file.py function_name
What does the tldr-router skill do?
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill tldr-router --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.