---
name: Summarize
slug: summarize-3
category: Writing
description: Summarize creates concise Slack-ready writeups from a spec or current changes. Use it when you need a short problem-and-solution summary for team communication.
github: "https://github.com/saffron-health/libretto/tree/main/.agents/skills/summarize"
language: TypeScript
stars: 877
forks: 67
install: "npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/summarize ~/.claude/skills/summarize"
installs_to: ~/.claude/skills/summarize
source_path: .agents/skills/summarize/SKILL.md
collection_size: 23
category_size: 1012
collection_url: "https://dirskills.com/collections/saffron-health/libretto"
added: 2026-08-22T05:21:21.742Z
last_synced: 2026-08-22T05:21:21.742Z
canonical_url: "https://dirskills.com/skills/summarize-3"
---

# Summarize

Summarize creates concise Slack-ready writeups from a spec or current changes. Use it when you need a short problem-and-solution summary for team communication.

**Install:**

```bash
npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/summarize ~/.claude/skills/summarize
```

## README

Summarize the given spec or current changes into a format suitable for sharing on Slack.

Read the spec file or use git diff to understand the current changes if no spec is provided.

Output the summary in this exact format:

```
**Problem:** Right now, we ...
- <bullet point explaining issue>
- <bullet point explaining issue>
- ...

**Solution:** <one sentence explaining the solution>
- <bullet point explaining change>
- <bullet point explaining change>
- ...
```

Guidelines:

- Write concisely using active voice
- Focus on what matters to teammates who have no context
- Do not reference "this spec" or "this PR" - explain the problem and solution directly
- Keep bullet points short and scannable
- Use technical terms appropriately but avoid jargon