tldr-router
Maps questions to the optimal tldr command. Use this to pick the right layer
pinned to #d07ff4bupdated last month
Ask your AI client: “install skills/tldr-router”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/tldr-routermetahub onboarded this repo on the author's behalf.
If you own github.com/parcadei/Continuous-Claude-v3 on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
3,883
Last commit
last month
Latest release
published
- #agents
- #claude-code
- #claude-code-cli
- #claude-code-hooks
- #claude-code-mcp
- #claude-code-skills
- #claude-code-subagents
- #claude-skills
- #mcp
About this skill
Pulled from SKILL.md at publish time.
Maps questions to the optimal tldr command. Use this to pick the right layer.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d07ff4b· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
7 passed2 warningsDescription qualitywarn
14 words · 76 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
README is present and substantial
45,577 chars · 22 sections · 38 code blocks
Tags / topics declared
9 total — agents, claude-code, claude-code-cli, claude-code-hooks, claude-code-mcp, claude-code-skills (+3)
README has usage / example sections
found: Quick Start · Installation · Installation (+1)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 14 words.
Documentation present and substantive
Documentation present (SKILL.md, 372 words).
Documentation shows usage
Documentation includes 8 code examples.
Release history
1- releasecurrentd07ff4bwarnlast month
Contents
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 overview
Use: 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" ──► search
Intent 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:
- Detect intent from your messages
- Route to appropriate layers
- 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 42
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/tldr-router