parcadei/continuous-claude-v3

tldr-router

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

First seen Jan 24, 2026

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.

Also in this package

Other skills from parcadei/continuous-claude-v3 · top by installs.

npx skills add parcadei/continuous-claude-v3

Browse all from 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.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 3.9K
License LICENSE
Default branch main
Open issues 30
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,511 B
  • docs SUMMARY.md 95 B

History

  1. First seen on skills.sh
  2. 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:

  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