askill
tldr

tldrSafety 95Repository

Generate a concise TLDR.md summary of the current session's key findings, decisions, and outcomes. Use when the user says "/tldr", "write a tldr", "summarize this session", "create a summary", or wants a shareable document capturing what happened in this conversation. Produces a clean, engineer-friendly markdown file ready to share before diving into full analysis.

0 stars
1.2k downloads
Updated 3/2/2026

Package Files

Loading files...
SKILL.md

TLDR

Generate a TLDR.md file summarizing the current session for sharing with other engineers.

Process

  1. Check for existing file — Read ./.stoobz/TLDR.md if it exists. If found:

    • Preserve previous content under a ## Previous Session heading
    • Add new content as the primary (top) section with updated timestamp
    • This creates a rolling history — latest session first
  2. Review the full conversation to extract:

    • What was investigated/built — the problem or task
    • Key findings — discoveries, root causes, data points
    • Decisions made — choices and their rationale
    • Actions taken — code changes, config updates, commands run
    • Open items — unresolved questions, next steps, follow-ups
  3. Write .stoobz/TLDR.md in the current working directory using the format below.

  4. Confirm the file path and offer to adjust if needed.

Output Format

# TLDR: {One-line title}

**Date:** {YYYY-MM-DD}
**Session:** {branch or context identifier}
**Author:** Claude + {user}

---

## Context

{1-2 sentences: what prompted this work and why it matters}

## Key Findings

- {Finding 1 — be specific, include numbers/names}
- {Finding 2}
- {Finding 3}

## Decisions

| Decision           | Rationale |
| ------------------ | --------- |
| {What was decided} | {Why}     |

## Changes Made

- {File or system changed}: {what changed}

## Open Items

- [ ] {Next step or unresolved question}
- [ ] {Follow-up needed}

---

_Generated from Claude Code session — see full conversation for details._

Rules

  • Brevity over completeness — if it takes more than 2 minutes to read, it's too long
  • Specifics over generalities — include actual file names, numbers, error messages, not vague descriptions
  • Skip sections with no content — if no decisions were made, omit the Decisions table
  • No jargon expansion — engineers reading this know the stack; don't explain what Oban or Ecto are
  • One file, flat structure — no subdirectories, no companion files
  • Write to ./.stoobz/TLDR.md in the current working directory unless the user specifies a different path

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

78/100Analyzed 3/2/2026

Well-structured skill with clear process, output format, and rules. Good actionability with numbered steps and specific output template. Reusability slightly reduced due to specific path (.stoobz/) and command trigger (/tldr). Includes tags and clear when-to-use guidance. Slightly internal due to specific repo context and Claude Code reference.

95
85
58
70
82

Metadata

Licenseunknown
Version-
Updated3/2/2026
Publisherjstoobz

Tags

llm