tldr

tldr-skill

Manage conversation summaries (tldrs) in the Obsidian vault. Each tldr captures decisions, key things to remember, and next actions.

Vault root: Determined from the current working directory or the project's CLAUDE.md context. All paths below are relative to the vault root. Always resolve to absolute paths when reading or writing files.

Operations

File Naming

01 - Projects/{project-name}/YYYY-MM-DD-HH-mm-{project-name}-tldr.md

Example: 01 - Projects/vault-setup-skill/2026-03-19-12-03-vault-setup-skill-tldr.md

Create (default operation)

This is the primary operation when /tldr is invoked with no arguments.

Step 1 — Identify Project

Ask the user:

Which project is this for?

Suggest: {inferred project name from conversation context}

Use the conversation topic to suggest a project name. The user confirms or provides a different name. Kebab-case the name for the filename.

Step 2 — Summarize

Extract from the conversation:

1. What was done — concrete actions taken, files changed
2. What was decided — design choices, trade-offs, rationale
3. Key things to remember — gotchas, patterns, non-obvious details
4. Next actions — if any remain

Step 3 — Save

Write to 01 - Projects/{project-name}/YYYY-MM-DD-HH-mm-{project-name}-tldr.md using current time.

If the project subfolder doesn't exist, create it.

Template:

---
created: YYYY-MM-DDTHH:mm
tags:
  - project/{project-name}
  - tldr
status: complete
---

# YYYY-MM-DD — {Project Name}

## What Was Done
[concrete actions, files changed]

## Decisions
[design choices with rationale]

## Key Things to Remember
[gotchas, patterns, non-obvious details]

## Next Actions
- [ ] [action items, if any]
- None — work is complete