How do I install the Tldr Router skill?

Run npx skillmds@latest add majiayu000/tldr-router in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Tldr Router skill do?

Maps questions to the optimal tldr command. Use this to pick the right layer It is listed under Coding & Dev Tools on SkillMD.

Is Tldr Router safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tldr Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tldr Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tldr Router?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tldr Router by majiayu000 — Agent Skill

Name: Tldr Router
Rating: 4.2 (5 reviews)
Author: majiayu000

File 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

---name: tldr-routerdescription: Maps questions to the optimal tldr command. Use this to pick the right layer--- # 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 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: 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: ```bash # 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 ```

Frequently asked questions

Tldr Router