tldr

**Quick judgment**: This skill is a solid, efficient way to access tldr-pages (simplified man pages). It is well-suited for quickly answering CLI usage questions with minimal tokens and clear examples, and should generally be preferred over pulling full man or `--help` output. **Strengths** - Very token-efficient compared to manual pages, ideal for chat-based assistants. - Example-centric documentation matches how users typically ask for CLI help (“How do I do X?”). - Simple interface (`tldr <command>`, `--update`, `--list`) makes tool invocation straightforward. **Risks / Limitations** - Coverage is incomplete: some less common commands or very new tools may lack tldr pages. - tldr pages intentionally omit many edge-case flags and advanced usage details; for deep configuration or debugging, falling back to `man`/`--help` is still necessary. - For potentially destructive commands (e.g., `rm`, `dd`, `mkfs`), examples may be correct but still dangerous if run blindly; an assistant should add contextual warnings and sanity checks. **Recommended scenarios** - Default tool for answering most “how do I use this CLI command?” questions. - Generating succinct, example-based instructions in programming/devops support chats. - First step in CLI explanation workflows, with fallback to `man`/`--help` only when tldr lacks a page or required detail.