agentleFS
eddmanneddmann/jeeves/skills/summarise/SKILL.md

summarise

Skill2 starsChanged 9 months agoMITView on GitHub

Extract and summarise content from URLs, YouTube videos, podcasts, and files. Use when the user shares a link, asks "what's this about", "summarise this", wants a transcript, or references web/video/podcast content.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. kn-neeraj/agent-skills★ 2same name
    2. marcuskrogh/skills★ 1same name
    3. mindscrape9/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --extract to get clean text, then summarise as the agent.

    line 18
  2. Distinctive:

    When content is very long and would use too many tokens, let summarize do it directly.

    line 30
  3. Very specific:

    Use CLI summarisation (without --extract) for very long content to save tokens

    line 40
  4. Very specific:

    Model errors: Check that the relevant API key env var is set (e.g.

    line 48

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

Summarise Skill

Extract clean content or generate summaries from URLs, YouTube videos, podcasts, and files using @steipete/summarize via buns.

Usage

buns run --allow-host="*" --allow-env="*" --memory=512 --timeout=120 workspace/skills/summarise/scripts/summarize.ts -- [FLAGS] "URL_OR_FILE"

Extract Content (preferred)

Use --extract to get clean text, then summarise as the agent. This avoids a redundant LLM call.

# Web page or article
... -- --extract "URL"

# YouTube with timestamps
... -- --extract --timestamps "YOUTUBE_URL"

Summarise via CLI

When content is very long and would use too many tokens, let summarize do it directly.

... -- "URL"                     # default xl summary
... -- --length short "URL"      # brief summary

Tips

  • Prefer --extract for most use cases — the agent can summarise in its own voice
  • Use CLI summarisation (without --extract) for very long content to save tokens
  • --timestamps adds time markers to YouTube/podcast transcripts
  • --json returns structured output with metadata

Troubleshooting

  • No transcript: YouTube video may not have captions
  • Timeout: Increase --timeout for long videos or slow sites
  • Model errors: Check that the relevant API key env var is set (e.g. ANTHROPIC_API_KEY)

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.