tldr-expert

Included with Lifetime

$97 forever

Concise summarization and information distillation. Covers executive summaries, code change summaries, PR descriptions, meeting notes, technical briefs, and progressive disclosure patterns. Use when writing PR descriptions, summarizing code changes, creating executive briefs, distilling long discussions, or generating release notes.

Writing & Docs

What this skill does


# TL;DR Expert

## Overview

The TL;DR Expert skill produces clear, concise summaries of technical content. It applies structured patterns to distill complex information into actionable briefs at the right level of detail for the audience.

**When to use:** Writing PR descriptions, summarizing code changes for reviewers, creating executive briefs for stakeholders, distilling long discussions into decisions and action items, or generating release notes.

**When NOT to use:** Writing full documentation (use the `docs` skill), producing marketing copy, creating detailed tutorials, or writing specifications that require exhaustive coverage.

## Quick Reference

| Pattern           | Format                                           | Key Points                                     |
| ----------------- | ------------------------------------------------ | ---------------------------------------------- |
| Executive summary | Conclusion first, then evidence, then details    | Lead with the recommendation; inverted pyramid |
| PR description    | What changed, why, how to test                   | Reviewers read the title and first paragraph   |
| Code change       | Files changed, key decisions, impact areas       | Focus on intent, not line-by-line diff         |
| Meeting notes     | Decisions, action items, open questions          | Skip discussion; capture outcomes              |
| Release notes     | User-facing changes, breaking changes, migration | Write for users, not developers                |
| Technical brief   | Problem, solution, alternatives, recommendation  | One page max; link to details                  |

## Common Mistakes

| Mistake                                   | Correct Pattern                                             |
| ----------------------------------------- | ----------------------------------------------------------- |
| Too verbose; includes every detail        | Cut to 20% of original length while keeping 80% of value    |
| Missing context; assumes reader knows     | Include one sentence of background before the summary       |
| Burying the lead in the third paragraph   | First sentence states the conclusion or key change          |
| No actionable items in meeting notes      | Every meeting summary ends with owners and deadlines        |
| Summarizing HOW instead of WHY            | Lead with intent and impact, not implementation details     |
| No audience awareness                     | Adjust depth: exec = 3 bullets, dev = 1 paragraph           |
| Release notes written for developers      | Focus on what users can do differently, not code changes    |
| PR description says "various fixes"       | List each change with a reason; vague helps no one          |
| Missing breaking changes in release notes | Breaking changes get their own section with migration steps |
| Using jargon for non-technical audience   | Match vocabulary to the reader's expertise level            |

## Delegation

- **Content discovery**: Use `Explore` agent to gather source material
- **Detailed review**: Use `Task` agent for thorough analysis before summarizing
- **Code review**: Delegate to `code-reviewer` agent for change impact assessment

> If the `docs` skill is available, delegate full documentation tasks to it.

## References

- [Summarization patterns, templates, and progressive disclosure](references/summarization-patterns.md)

Files: 2

Size: 14.9 KB

Complexity: 35/100

Category: Writing & Docs

Source: https://github.com/oakoss/agent-skills/tree/main/skills/tldr-expert

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts