tldr-router

parcadei/continuous-claude-v3 · updated Apr 8, 2026

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill tldr-router
0 commentsdiscussion
summary

Maps questions to the optimal tldr command. Use this to pick the right layer.

skill.md

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:

  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 42

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.835 reviews
  • Noor Robinson· Dec 12, 2024

    tldr-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Dec 8, 2024

    I recommend tldr-router for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aarav Iyer· Dec 8, 2024

    We added tldr-router from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Alexander Zhang· Nov 27, 2024

    Useful defaults in tldr-router — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Amelia Mehta· Nov 7, 2024

    I recommend tldr-router for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kwame Singh· Oct 26, 2024

    tldr-router reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Alexander Anderson· Oct 18, 2024

    tldr-router has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Olivia Lopez· Sep 13, 2024

    We added tldr-router from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Sep 1, 2024

    Useful defaults in tldr-router — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Pratham Ware· Aug 20, 2024

    tldr-router has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 35

1 / 4