agentsclimarketplace
Sign in

Summarize source

Skill sumitaich1998/jarvisvr/skills/research/summarize-source

Condense a single source — a URL, article, document, or pasted text — into key points the user can read at a glance. Use for "summarize this", "TL;DR", "give me the key points", or as a summarizer sub-agent merging one of several sources. Triggers: summarize, tldr, key points, gist, condense, brief me on this, what's the takeaway.From its SKILL.md

Install
npx -y skills add sumitaich1998/jarvisvr --skill summarize-source

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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 575 tokens by cl100k_base, as published. Nobody here has run it

Summarize Source

Produce a faithful, compact summary of one source and present it as a sectioned panel (or open the original in a document_viewer). This is also the unit of work for a summarizer sub-agent in a fan-out (protocol §9.2 handoff).

Steps

  1. Acquire the content. Provided text → use directly. A URL → web_search (or fetch via provider) to obtain the page text.
  2. Extract structure: a one-line thesis, 3–5 key points, and any numbers / dates / names worth keeping.
  3. Compose the summary. Lead with the thesis; bullet the points; preserve source attribution. Stay faithful — never add claims the source doesn't make.
  4. Render a panel with sections, or show_document to open the original alongside.
  5. Speak a 1-sentence TL;DR; offer the full panel for detail.

Output

panel (show_panel, props per registry.json):

{ "widget_type": "panel",
  "props": { "title": "Summary — Quest 4 review",
             "body": "Strong display gains, same comfort tradeoffs.",
             "sections": [
               { "heading": "Key points", "text": "1) Brighter pancake lenses 2) Better passthrough 3) Heavier" },
               { "heading": "Source", "text": "TechNews, 2026" } ],
             "scrollable": true } }

Spoken TL;DR:

{ "text": "TL;DR: a meaningful display upgrade, but comfort is unchanged.", "final": true }

As a sub-agent (fan-out)

When merging several sources, each summarizer sub-agent (a1.1, a1.2, …) summarizes one source and returns its {thesis, points, source}; the parent research-agent reconciles overlaps and dedupes before handing to result-synthesis / present-data.

Edge cases

  • Paywalled / unreachable URL → summarize the snippet you have and flag that it's partial; never invent the body.
  • Very long doc → summarize hierarchically (per-section, then overall) and open it in document_viewer with page_count set.
  • Conflicting claims within the source → present them as the source's open question, don't resolve silently.
  • Code/tabular content → use code_viewer / data_table instead of prose.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. 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.