tldr-overview
Get a token-efficient overview of any project using the TLDR stack
pinned to #d07ff4bupdated last month
Ask your AI client: “install skills/tldr-overview”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/tldr-overviewmetahub 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.
Get a token-efficient overview of any project using the TLDR stack.
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
11 words · 66 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 11 words.
Documentation present and substantive
Documentation present (SKILL.md, 275 words).
Documentation shows usage
Documentation includes 6 code examples.
Release history
1- releasecurrentd07ff4bwarnlast month
Contents
TLDR Project Overview
Get a token-efficient overview of any project using the TLDR stack.
Trigger
/overviewor/tldr-overview- "give me an overview of this project"
- "what's in this codebase"
- Starting work on an unfamiliar project
Execution
1. File Tree (Navigation Map)
tldr tree . --ext .py # or .ts, .go, .rs
2. Code Structure (What Exists)
tldr structure src/ --lang python --max 50
Returns: functions, classes, imports per file
3. Call Graph Entry Points (Architecture)
tldr calls src/
Returns: cross-file relationships, main entry points
4. Key Function Complexity (Hot Spots)
For each entry point found:
tldr cfg src/main.py main # Get complexity
Output Format
## Project Overview: {project_name}
### Structure
{tree output - files and directories}
### Key Components
{structure output - functions, classes per file}
### Architecture (Call Graph)
{calls output - how components connect}
### Complexity Hot Spots
{cfg output - functions with high cyclomatic complexity}
---
Token cost: ~{N} tokens (vs ~{M} raw = {savings}% savings)
When NOT to Use
- Already familiar with the project
- Working on a specific file (use targeted tldr commands instead)
- Test files (need full context)
Programmatic Usage
from tldr.api import get_file_tree, get_code_structure, build_project_call_graph
# 1. Tree
tree = get_file_tree("src/", extensions={".py"})
# 2. Structure
structure = get_code_structure("src/", language="python", max_results=50)
# 3. Call graph
calls = build_project_call_graph("src/", language="python")
# 4. Complexity for hot functions
for edge in calls.edges[:10]:
cfg = get_cfg_context("src/" + edge[0], edge[1])
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-overview