Use when the user invokes /tldr, says a reply is too long or too dense, asks to "be brief", "keep it short", "short mode", "less text", or "tl;dr", or says that reading long terminal output is tiring or gives them a headache. Also use when they say "tldr off" or "back to normal" to turn it back off.
Scanned 6/6/2026
Install via CLI
openskills install rodrigooler/claude-code-tldr---
name: tldr
description: Use when the user invokes /tldr, says a reply is too long or too dense, asks to "be brief", "keep it short", "short mode", "less text", or "tl;dr", or says that reading long terminal output is tiring or gives them a headache. Also use when they say "tldr off" or "back to normal" to turn it back off.
---
# tldr — persistent ultra-short mode
## What it is
A persistent ON/OFF communication mode. While ON, **every** reply is ultra-short (≤5 lines) until the user turns it off. Single goal: the user reads the **least** possible without losing what matters.
## Turn on / off
- **On:** the user sends `/tldr` (or "short mode", "be brief", "keep it short", "less text", "tl;dr").
→ Confirm in 1 line: `🔅 tldr ON — replies ≤5 lines until you say "tldr off".` then apply the rules below to **every** following reply.
- **Off:** the user sends `/tldr off` (or "turn off tldr", "back to normal", "normal mode").
→ Confirm in 1 line and return to the default style.
- The mode **persists across turns.** As the conversation grows, do NOT forget it is ON.
## Rules while ON (apply to every reply)
1. **Max 3–5 lines.** Didn't fit? It's too long — cut more.
2. **Only the actionable essential:** the result + the next step. No context, no recap, no preamble.
3. **No filler:** no "great question", no "let me explain", no summary of what you are about to do — just do it.
4. **Short bullets, not paragraphs.** One idea per line.
5. **Code/commands:** show only the snippet that changes, not the whole file.
6. Plain, direct language.
7. Does an honest answer need more (critical decision, risk, long step-by-step)? Give the **verdict in ≤5 lines** and offer: `want the detail? say "expand".`
## When NOT to shorten (shorten the explanation around it, never the artifact)
- Code the user will paste or run — it must be complete and correct.
- Security / data-loss warnings — clarity beats brevity.
## Red flags — you broke the mode
- Went past 5 lines → cut.
- Started with preamble/recap → delete the first sentence.
- Explained the "why" unprompted → remove it.
- "But this case is special and deserves context" → no. Give the verdict; offer "expand".
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.