agentleFS
ccomkhjccomkhj/skills/loom-transcript/SKILL.md

loom-transcript

Skill10 starsChanged 19 days agoMITView on GitHub

Fetch a public Loom video's transcript from its share link and summarize it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Fetch the transcript: Run the bundled script from this skill's directory:

    line 13
  2. Very specific:

    Add --timestamps only when the user wants to navigate or cite moments in the video — it appends a segments array with per-line start times.

    line 19
  3. Very specific:

    On error, stop: If the JSON has an error field, relay that message to the user verbatim and stop — there is no fallback.

    line 21

≈ “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

Turn a Loom share link into its spoken transcript, then summarize. This skill only fetches; the summarizing is yours to do.

Steps

  1. Get the link. Take the loom.com/share/… URL from the invocation. If none was given, ask for one.
  2. Fetch the transcript. Run the bundled script from this skill's directory:

    python3 loom_transcript.py "<url>"

    Add --timestamps only when the user wants to navigate or cite moments in the video — it appends a segments array with per-line start times.

  3. On error, stop. If the JSON has an error field, relay that message to the user verbatim and stop — there is no fallback. The common cause is a private/workspace-locked video, which cannot be read without the owner's credentials.
  4. Summarize. By default, give a concise summary of the transcript (lead with the video's title). If the user stated how or what to summarize — a focus, a length, a format, "just the action items", "verbatim quote about X" — follow that instead of the default summary.

Done when the user has the summary (or the specific rendering they asked for), or a clear reason it couldn't be fetched.

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.