agentleFS
Sign inStart free
saffron-healthsaffron-health/libretto/.agents/skills/summarize/SKILL.md

summarize

Skill883 starsChanged 3 months agoMITView on GitHub

Summarize a spec or current changes into a format suitable for sharing on Slack. Use when creating a summary for team communication.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 75 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 8
  2. Distinctive:

    Write concisely using active voice

    line 26
  3. Distinctive:

    Do not reference "this spec" or "this PR" - explain the problem and solution directly

    line 28
  4. Distinctive:

    Keep bullet points short and scannable

    line 29
  5. Distinctive:

    Use technical terms appropriately but avoid jargon

    line 30

“Common” is measured: kept by at least 6 in 10 of the 75 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free