npx skills add smithery/parcadei --skill tldr-router
parcadei/continuous-claude-v3
tldr-router
Maps questions to the optimal tldr command. Use this to pick the right layer
Installation
npx skills add parcadei/continuous-claude-v3 --skill tldr-router
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and d…
14.7K installsReact Router v7/v8 patterns with Clerk — rootAuthLoader, getAuth in loaders, clerkMiddleware, p…
12.7K installsGenerate or edit images via OpenRouter with the Gemini 3 Pro Image model. Use for prompt-only i…
9.9K installsUse when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg bloc…
4.2K installsStart or patch Dynamo router modes and run router endpoint smoke checks. Use for round-robin, K…
1.9K installsFull Sentry SDK setup for React Router Framework mode. Use when asked to "add Sentry to React R…
1.6K installsAlso in this package
Other skills from parcadei/continuous-claude-v3 · top by installs.
npx skills add parcadei/continuous-claude-v3
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,511 B -
docs
SUMMARY.md95 B
History
- First seen on skills.sh
- First recorded snapshot · 472 installs
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:
- 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