loomlisted

Read and manage Loom videos from the shell via the `loom` CLI, which ships inside this skill (nothing to install). Use whenever the user pastes a loom.com URL or mentions a Loom recording — "summarize this loom", "what did they say in this loom", "pull the transcript of this Loom video", "get the captions/chapters/key takeaways", "what are the action items from this recording", "extract to-dos from my last 10 looms", "list my Loom videos", "search my Looms for X", "who commented on this loom", "download this Loom video", "what's the download URL", "turn this Loom into meeting notes", "rename/archive/move/pin this video", "add a comment at 2:30". Handles transcripts, WebVTT captions, AI summaries, chapter markers, key takeaways, descriptions, comments and threaded replies, AI-extracted tasks, emoji reactions, backlinks, MP4 download URLs, plus library management across videos, folders, spaces, Watch Later and tags. Human-readable text by default, `--json` for parsing, `-o PATH` for long transcripts, `--dry-run
rainearcher/quiver · ★ 0 · AI & Automation · score 73

Install: claude install-skill rainearcher/quiver

# Loom CLI `loom` is a command-line client for Loom's internal GraphQL API. It reads videos, transcripts, captions, AI summaries, chapters, key takeaways, comments and action items, and manages your library — all from the shell, with `--json` on every command so output composes with `jq`. There is no MCP server and nothing to configure in `.mcp.json`. You call the CLI with `Bash`. ## Prerequisites - [`uv`](https://docs.astral.sh/uv/) on PATH (provides `uvx`), **or** `loom` already installed on PATH - `LOOM_COOKIE` — your Loom browser session cookie The CLI itself is **vendored into this skill** at `vendor/`, so there is nothing to install and nothing is fetched from PyPI. `uvx` builds that local copy the first time and caches it. Loom has no official API key, so the tool talks to Loom as you, using your browser session cookie. Getting one: 1. Open [loom.com](https://www.loom.com) in a browser and sign in 2. DevTools (F12) → Application → Cookies → `https://www.loom.com` 3. Copy the **value** of the `connect.sid` cookie (it starts with `s%3A`) 4. `export LOOM_COOKIE='s%3A...'` The `connect.sid=` prefix is added automatically, so either `s%3A...` or `connect.sid=s%3A...` works. Make it permanent by adding the `export` to `~/.zshrc` / `~/.bashrc` or `~/.claude/.env`, then restarting the CLI. The cookie lasts roughly 30 days; when it expires every command exits `3`. Alternatives: `--cookie VALUE` passes a cookie inline, and `LOOM_AUTH_FILE` / `--auth-file PATH` accepts a