Claude Skill

media-digest

Reads anything long — a video, podcast, talk, article, PDF or a recording of their own — and hands it back short. Use it when the user points at one and asks what is in it, wants a meeting or lecture they recorded written up, or asks which videos on a topic are worth watching.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download cgoinglove-thursday-agent-skills_media-digest-12bbc84.zip · 29 KB

Install

skills CLI npx skills add https://github.com/cgoinglove/thursday-agent/tree/main/skills/media-digest
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cgoinglove-thursday-agent@llmmart
Git git clone https://github.com/cgoinglove/thursday-agent.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cgoinglove/thursday-agent collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Media digest

Every script is node <this skill's dir>/scripts/<name>.mjs, needs no key and prints a few lines; the text itself goes to a file. Chain them with && in one bash call.

S=<this skill's dir>/scripts
node $S/yt.mjs transcript <url|id>... --out <scratch> [--lang de]   # <id>.txt + <id>.json per video
node $S/yt.mjs search "<query>" [--within hour|day|week|month|year] [--length short|medium|long] [--sort relevance|views|date] [--max 20] --out <scratch>/rows.json
node $S/text.mjs <article url | pdf url | file.pdf> --out <scratch>/<name>.txt
node $S/part.mjs <file> <n>                                         # part n of a long file, one read
node $S/audio.mjs cut <url|file> --out <scratch>/audio [--minutes 10]   # no captions: pieces to transcribe
node $S/digest.mjs <digest.json> --name <page>                      # the page, in your artifacts folder
node $THURSDAY_SKILLS/artifact/scripts/document.mjs pdf <page path>   # a PDF beside it, when asked for one

Two facts decide the work:

  • One bash call shows only so much of what it prints; the rest is cut. So every file these scripts write is split into ## Part N blocks that each fit one read, and the head they print says how many. One part per bash call — two in one call are cut — and the calls for several parts sent together in one step. A question about one thing is grep -n -i on the file first, then only the parts that hit; a summary reads every part. How: references/reading.md.
  • A timestamp is only worth giving when it comes from the file. Each transcript line starts with [m:ss]; cite that time, never one worked out. A ~ marks a time estimated from where the words fall in a piece of audio; cite it with the ~, which still opens the source at that second.

YouTube is read with yt-dlp, which the first yt.mjs or audio.mjs call fetches into projects/ once (~50 MB); after that a video takes a few seconds.

references/page.md is the page's JSON and how an answer is shaped; references/no-captions.md is a video, podcast or recording with no transcript. A meeting or lecture they recorded is written up as notes — what was decided, who does what and by when, each point with its [m:ss] — in the artifact skill's templates/document/notes.md, not as a digest page.

Files (thursday-agent)
  • references
    • no-captions.md 1.6 KB
      Loading…
    • page.md 3.2 KB
      Loading…
    • reading.md 2.9 KB
      Loading…
  • scripts
    • audio.mjs 7.5 KB · in bundle
    • digest.mjs 17.4 KB · in bundle
    • lib.mjs 8.8 KB · in bundle
    • part.mjs 748 B · in bundle
    • text.mjs 9.8 KB · in bundle
    • yt.mjs 15 KB · in bundle
  • SKILL.md 2.6 KB
    ---
    name: media-digest
    description: "Reads anything long — a video, podcast, talk, article, PDF or a recording of their own — and hands it back short. Use it when the user points at one and asks what is in it, wants a meeting or lecture they recorded written up, or asks which videos on a topic are worth watching."
    ---
    
    # Media digest
    
    Every script is `node <this skill's dir>/scripts/<name>.mjs`, needs no key and prints a few
    lines; the text itself goes to a file. Chain them with `&&` in one bash call.
    
    ```bash
    S=<this skill's dir>/scripts
    node $S/yt.mjs transcript <url|id>... --out <scratch> [--lang de]   # <id>.txt + <id>.json per video
    node $S/yt.mjs search "<query>" [--within hour|day|week|month|year] [--length short|medium|long] [--sort relevance|views|date] [--max 20] --out <scratch>/rows.json
    node $S/text.mjs <article url | pdf url | file.pdf> --out <scratch>/<name>.txt
    node $S/part.mjs <file> <n>                                         # part n of a long file, one read
    node $S/audio.mjs cut <url|file> --out <scratch>/audio [--minutes 10]   # no captions: pieces to transcribe
    node $S/digest.mjs <digest.json> --name <page>                      # the page, in your artifacts folder
    node $THURSDAY_SKILLS/artifact/scripts/document.mjs pdf <page path>   # a PDF beside it, when asked for one
    ```
    
    Two facts decide the work:
    
    - **One bash call shows only so much of what it prints; the rest is cut.** So every file these scripts
      write is split into `## Part N` blocks that each fit one read, and the head they print says
      how many. One part per bash call — two in one call are cut — and the calls for several
      parts sent together in one step. A question about one thing is `grep -n -i` on the file first, then only the parts
      that hit; a summary reads every part. How: `references/reading.md`.
    - **A timestamp is only worth giving when it comes from the file.** Each transcript line
      starts with `[m:ss]`; cite that time, never one worked out. A `~` marks a time estimated
      from where the words fall in a piece of audio; cite it with the `~`, which still opens the
      source at that second.
    
    YouTube is read with yt-dlp, which the first `yt.mjs` or `audio.mjs` call fetches into
    `projects/` once (~50 MB); after that a video takes a few seconds.
    
    `references/page.md` is the page's JSON and how an answer is shaped; `references/no-captions.md`
    is a video, podcast or recording with no transcript. A meeting or lecture they recorded is written
    up as notes — what was decided, who does what and by when, each point with its `[m:ss]` — in the
    artifact skill's `templates/document/notes.md`, not as a digest page.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.