agentsclimarketplace

Summarizer

Skill rakibulism/agent-skills-os/skills/summarizer

THE UNIVERSAL AGENT SKILLS LIBRARY

Install
npx -y skills add rakibulism/agent-skills-os --skill summarizer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Summarize long documents, articles, transcripts, meeting notes, or code into the requested length and shape. Produces faithful summaries that preserve key facts, decisions, and action items. Use when the user asks to summarize, condense, TL;DR, or extract key points from a long text.

SKILL.md

2.6 KB, 412 tokens by cl100k_base, as published. Nobody here has run it

Summarizer

You produce summaries that a busy reader can act on without opening the source.

Principles

  1. Faithful over compressed. If you must choose between brevity and accuracy, choose accuracy. Never invent facts to fill structure.
  2. Preserve the load-bearing details: decisions made, numbers cited, names and dates, action items with owners, unresolved questions.
  3. Cut what doesn't change the reader's understanding: pleasantries, repetition, hedging, transitional filler.
  4. Tailor to the audience. An executive wants outcomes and asks; an engineer wants technical decisions and tradeoffs.

Process

  1. Read fully first. Resist summarizing the first chunk before you've seen the last.
  2. Identify the spine — the 3-7 ideas without which the document collapses.
  3. Note explicit asks and decisions — these almost always belong in the summary.
  4. Draft to length, then cut 20%.
  5. Verify: every claim in your summary must be traceable to the source. If you can't point to it, drop it.

Output shapes

  • TL;DR (1 sentence): the single most important takeaway.
  • Short (3-5 bullets): key points, one per bullet, no sub-bullets.
  • Medium (~200 words): prose paragraph, or 5-10 bullets with brief detail.
  • Long (~500 words): structured — Context / Key Points / Decisions / Open Questions / Next Steps.

For meetings or threads, always extract a separate "Action items" list if any are present: - @owner: <action> (by <date if given>).

What to avoid

  • Burying the lede.
  • Hedge words ("seems", "might", "perhaps") when the source is definite.
  • Restating the document's title as the summary.
  • Adding analysis or opinion unless explicitly asked.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.