agentleFS
Sign inStart free
surfmind-spacesurfmind-space/awesome-surfmind/skills/summarize/SKILL.md

summarize

Skill8 starsChanged 5 months agoMITView on GitHub

Creates a summary that adapts to the source, such as an article, email thread, chat, PDF, document, image, or transcript, while surfacing the key points, decisions, and takeaways. Use when the user says "summarize", "TLDR", "key points", "recap", "overview", or "condense this".

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openclaw-performance, plugin-sdk-impact and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • clawdbotSkill

    openclaw-performance

    Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.

    Also in 7 projects that use this

  • clawdbotSkill

    plugin-sdk-impact

    Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.

    Also in 7 projects that use this

  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 18 projects that use this

  • molt-botSkill

    discord-e2e

    Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.

    Also in 10 projects that use this

  • molt-botSkill

    openclaw-repair-sweep

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    Also in 10 projects that use this

  • +2 more from molt-bot

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 1

    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:

    If the source doesn't match a listed pattern, infer the closest shape.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 81 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

Produce a summary that fits the source. There is no single template: first pick the source, then detect what kind of content it is and shape the summary to match.

1. Choose the source

Priority order: selected text, then an attached file, PDF, or image, then the visible page content. Summarize only what is actually present. Never invent details, quotes, numbers, names, dates, or outcomes that are not in the source. If the context is incomplete or truncated, summarize what is available and note the gap.

2. Adapt to the content type

Content typeCaptureShape the output as
Article / blog / web pageThesis, main arguments, supporting evidence, conclusionOne-line TL;DR + three to six bullets
Documentation / referenceWhat it's for, key steps or APIs, caveatsShort bullets grouped by topic
Email threadParticipants, the ask, decisions, open questions, action items + owners"Bottom line" line, then Decisions / Open questions / Action items
Chat / messaging conversationWho's talking, the topic, what was agreed, next stepsTopic-grouped bullets; keep the resolution explicit
PDF / long document / reportPurpose, section findings, recommendationsHeaded sections or nested bullets
Spreadsheet / data / tableWhat it measures, notable totals, outliers, trendsBullets, keeping key figures exact
Image / screenshot / chartWhat it depicts, labels, the takeaway it conveysOne to three sentences; describe only what is visible
Transcript (video / call / podcast)Topic, key points per speaker or segment, conclusions, action itemsBullets, optionally timestamped
Code / PR / diffWhat it does, notable changes, risksBullets by change

If the source doesn't match a listed pattern, infer the closest shape. Lead with the takeaway, then the supporting points.

3. Length and format

Scale to the source: a few sentences for something short, a tight bulleted brief for something long. Lead with the single most important takeaway. Prefer bullets for scannability; reserve flowing prose for very short sources. Preserve exact figures, dates, names, and decisions verbatim. It's a summary, not a rewrite. Stay concise.

Example

Source: a long launch-planning email thread (selected text).

Bottom line: Team agreed to ship the v2 dashboard on July 9, gated on the billing fix landing first.

Decisions

  1. Launch moved from July 2 to July 9 (Maria)
  2. Marketing holds the blog post until QA signs off

Open questions

  1. Who owns the migration runbook? (raised by Sam, unanswered)

Action items

  1. Land billing fix by July 7: Alex
  2. Full regression pass: Priya

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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