agentleFS
osspakistanosspakistan/agent-skills/skills/fewwords-summarizer/SKILL.md

fewwords-summarizer

Skill0 starsChanged 40 days agoMITView on GitHub

Content summarization and briefing skill for articles, YouTube videos, blog posts, and web content. Use whenever the goal is to summarize, explain, distill, or brief an article or video — whether the user provides a URL or pastes raw text/content directly.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before loading any rules or prompts, you MUST have the full content in hand:

    line 37
  2. Very specific:

    If the user provided a URL: Read references/fetching.md immediately and execute the fetch commands via terminal/bash:

    line 40
  3. Very specific:

    DO NOT: use default LLM web fetchers (like web_fetch, built-in browser, or Google search), as robots.txt and network restrictions will fail …

    line 41
  4. Very specific:

    If that fails or is empty, try curl -sL "https://r.jina.ai/<URL>"

    line 44
  5. Very specific:

    If proxies fail, try direct curl -sL "<URL>"

    line 45
  6. Distinctive:

    Only if all fetch attempts fail: Stop immediately and ask the user to paste the raw text.

    line 46
  7. Distinctive:

    Do not explain your classification or announce the steps.

    line 74
  8. Very specific:

    TITLE line: Always start with plain TITLE: (do not bold the prefix).

    line 80
  9. Very specific:

    Block quotes: Use markdown quote format (> Quote) without enclosing quotation marks ("...").

    line 83
  10. Distinctive:

    Attribution ban: Never say "the author" or "this article".

    line 86
  11. Distinctive:

    Never mention "Fewwords", this skill, or which strategy was used

    line 104
  12. Distinctive:

    Never invent facts, quotes, or statistics not present in the source

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Fewwords Summarizer

A summarization skill for AI agents. Covers articles, YouTube videos, podcasts, and any web content. Routes each through a unified content-type classifier, then applies the right prompt.

The core idea: medium doesn't matter. An article about a product review and a YouTube video about the same product are the same job. The classifier works by purpose, not by format.


When to use this skill

Trigger this skill whenever the user's intent is to summarize, brief, explain, digest, or extract key takeaways from content:

  • Common requests:
    • "Summarize this article/page"
    • "Give me a brief / rundown on this"
    • "Explain this article / what is this video about?"
    • "TL;DR of this URL"
    • "What are the key points / takeaways?"
    • "Should I buy / read / watch this?"
  • Accepted inputs:
    1. URL: An article link, blog post, documentation page, news story, or YouTube video URL.
    2. Raw content: Text pasted directly into chat, article excerpts, transcripts, or notes.

Flow

Step 1 — Acquire Content (FIRST ACTION)

Before loading any rules or prompts, you MUST have the full content in hand:

  • If the user pasted raw text / transcript: Proceed directly to Step 2.
  • If the user provided a URL: Read references/fetching.md immediately and execute the fetch commands via terminal/bash:
    • DO NOT use default LLM web fetchers (like web_fetch, built-in browser, or Google search), as robots.txt and network restrictions will fail or return truncated search snippets.
    • MANDATORY ORDER:
      1. Try curl -sL "https://curl.md/<URL>"
      2. If that fails or is empty, try curl -sL "https://r.jina.ai/<URL>"
      3. If proxies fail, try direct curl -sL "<URL>"
    • Only if all fetch attempts fail: Stop immediately and ask the user to paste the raw text. Never hallucinate or write a partial summary from search snippets.

Step 2 — Classify Content

Once the full text is acquired, read references/classifier.md.

Match the primary purpose of the text (not the medium) and identify which prompt file to load.

Step 3 — Load Strategy Prompt

Load only the single prompt file determined by the classifier:

Content TypePrompt File
Essay / Analysis / Educationreferences/prompts/essay-analysis.md
Tutorial / How-Toreferences/prompts/tutorial-howto.md
News / Announcementreferences/prompts/news-announcement.md
Review / Comparisonreferences/prompts/review-comparison.md
Interview / Podcastreferences/prompts/interview-podcast.md
Opinion / Commentaryreferences/prompts/opinion-commentary.md
Light / Generalreferences/prompts/light-general.md

Step 4 — Draft & Apply Writing Quality

Now load references/writing-quality.md.

Draft the summary using the structure from Step 3, and run the pattern checklist from writing-quality.md to prune AI clichés, formulaic openers, and fluff.

Do not explain your classification or announce the steps. Output only the clean summary.


Universal formatting (applies to all types)

  • TITLE line: Always start with plain TITLE: (do not bold the prefix).
  • Human names in bold: Sam Altman
  • Companies, products, tools in italic: Apple, VSCode
  • Block quotes: Use markdown quote format (> Quote) without enclosing quotation marks ("...").
  • Dev terminology / code: Inline backticks for commands, APIs, specs: npm install, 128GB, TCP/IP.
  • Paragraphs: 2-3 sentences max, with one sentence per line and a blank line after each sentence.
  • Attribution ban: Never say "the author" or "this article". Speak the facts directly.
  • Deduplication: State repeated points exactly once.

What this skill does not cover

  • Reddit threads
  • Paywalled content (tell user to paste the text)
  • YouTube Shorts (reject: "This is a Short. Not enough content to summarize.")
  • Videos with no transcript or metadata (tell user what's available and ask)

Notes for agents

  • Load reference files lazily — only what the classifier selects
  • references/writing-quality.md is the only file that always loads
  • Never mention "Fewwords", this skill, or which strategy was used
  • Never invent facts, quotes, or statistics not present in the source

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.