ワンクリックで
summarize
Summarize public content — articles/text, YouTube videos, or podcasts — by fetching text or transcripts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Summarize public content — articles/text, YouTube videos, or podcasts — by fetching text or transcripts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Two-layer memory system with grep-based recall.
Executes tools for AI agents, ensuring correct parameter formats and preventing common execution errors.
Get current weather and forecasts (no API key required). Use the `run_terminal_command` tool for execution.
Use this skill to get documentation for third-party APIs, SDKs or libraries before writing code that uses them to ensure you have the latest, most accurate documentation. This is a better way to find documentation than doing web search. This includes when a user asks for tasks like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any other time the user asks you to write code against an external service and you need current API reference. Fetch the docs with chub before answering, rather than relying on your pre-trained knowledge, which may be outdated because of recent changes to these APIs. Be sure to use this skill when the user asks for the latest docs, latest API behavior, or explicitly mentions chub or Context Hub. Ensure `chub` is available, run `chub --help`, then follow the instructions there.
Monitor environment health by checking URLs with 'curl -o /dev/null --max-time 5 -s -w "%{http_code}\n"' and analyzing failures with LLM.
| name | summarize |
| description | Summarize public content — articles/text, YouTube videos, or podcasts — by fetching text or transcripts. |
Summarize public content from three sources: articles/text, YouTube videos, and podcasts.
Use the tools you already have (web_fetch, run_terminal_command, web_search) — no external CLI needed.
Use this skill when the user asks any of:
Identify the content type from the URL or user description:
| Type | URL patterns / clues |
|---|---|
| Text / Article | Any URL not matching video/podcast patterns, or raw text pasted by user |
| YouTube Video | youtube.com/watch, youtu.be/, youtube.com/shorts/ |
| Podcast | Spotify, Apple Podcasts, podcast RSS feeds, or user explicitly says "podcast" |
Goal: Extract the readable text from a web page and summarize it.
Steps:
web_fetch with the URL to get the page content.Example flow:
web_fetch(url: "https://example.com/article")
→ Read the returned text
→ Generate the summary from the extracted content
If web_fetch fails (e.g. paywall, bot protection), tell the user and suggest they paste the text directly.
Goal: Get the video transcript/subtitles and summarize them.
Steps:
youtube.com/watch?v=VIDEO_ID → extract VIDEO_IDyoutu.be/VIDEO_ID → extract VIDEO_IDrun_terminal_command:curl -s "https://www.youtube.com/watch?v=VIDEO_ID" | grep -o '"captionTracks":\[.*?\]' | head -1
baseUrl, fetch the XML captions:curl -s "CAPTION_BASE_URL" | sed 's/<[^>]*>//g'
yt-dlp (if installed) to extract subtitles:yt-dlp --skip-download --write-auto-sub --sub-lang en,fr --sub-format vtt --convert-subs srt -o "/tmp/yt_%(id)s" "VIDEO_URL" 2>/dev/null && cat /tmp/yt_*.srt
curl -s "https://youtubetranscript.com/?server_vid2=VIDEO_ID"
Important: If no subtitles/captions are available (some videos have none), tell the user clearly: "This video has no available subtitles or auto-generated captions. I cannot transcribe it."
Goal: Get a transcript or show notes and summarize them.
Steps:
Try to find a transcript:
web_search to find a transcript: "PODCAST_NAME EPISODE_TITLE transcript"If a transcript page is found, use web_fetch to extract the text and summarize it.
If no transcript is available, try to get show notes:
web_fetch on the podcast episode page to extract the description/show notes.If the podcast has an RSS feed URL, parse it:
curl -s "RSS_FEED_URL" | grep -oP '<description><!\[CDATA\[.*?\]\]></description>' | head -5
Important: If no transcript or meaningful show notes can be found, tell the user clearly and suggest they provide a direct link to a transcript page or the audio file if they have a transcription tool.
Always structure your summary clearly:
## 📝 Summary: [Title]
**Source:** [Article / YouTube Video / Podcast]
**URL:** [original URL]
### Key Points
- Point 1
- Point 2
- ...
### Summary
[1–2 paragraph summary]
web_fetch first for articles — it's the fastest path.yt-dlp method first if available, fall back to curl scraping.