agentleFS
PicsArtPicsArt/media-studio/skills/footage-analysis/SKILL.md

footage-analysis

Skill1 starsChanged 10 days agoMITView on GitHub

Watch the user's own talking footage and turn it into facts you can build on - its moments worth keeping, who is on screen, and a transcript whose sentences set every cut - read every source at once and follow the job receipts. Use when a use case needs to know what happens in an interview, podcast, vlog, talk or any footage of people speaking, and when. A screen recording's pictures are read by the screen-recording-analysis skill; only its spoken narration is transcribed here.

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, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If that fails too, tell the user the service is down and to try again shortly.

    line 27
  2. Distinctive:

    With several sources, read them all at once: Every video gets its own probe, watch and transcript, and none waits for another.

    line 33
  3. Distinctive:

    When people speak, the two reads have different jobs:

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Media analysis

Know what the footage shows, and when, before you build on it. This skill reads people talking to camera, an interview, a podcast or a vlog; read references/talking-footage.md before you watch it. A screen recording is read from its pixels, as the screen-recording-analysis skill says. When it carries the user's own narration, that speech is transcribed here like any talking footage, and nothing in it is watched.

Watch

  1. picsart_media_probe on the file: dimensions, duration, and whether it has audio. It reports container facts only, never what is shown.
  2. picsart_media_describe_video with the use case's request as its question, asking for JSON, not prose. It charges credits on every call, so the use case gets consent before it runs. Read its answer. Apply picsart-video-rules's SPEND rule to each tool's billing contract.
  3. Unless the probe reports hasAudio: false, and when the narration is worth quoting, picsart_media_transcribe the file. The probe leaves hasAudio out when it cannot tell, and that is not a no.

The probe and the watch do not depend on each other; run them at the same time. The watch is critical. If it fails, or its answer is not the JSON you asked for, retry the same call once. If that fails too, tell the user the service is down and to try again shortly. Never guess the content from nothing.

The watch and the transcript reply with a job receipt, not the result: follow it as picsart-video-rules says.

With several sources, read them all at once. Every video gets its own probe, watch and transcript, and none waits for another. A photo gets only the probe, for its size: it has no speech and nothing happens in it over time.

Talking footage

When people speak, the two reads have different jobs:

  • The transcript is the only source of where a thought starts and stops. Transcribe every spoken source, with speakers: "auto" when more than one person may speak. Save the result verbatim as transcript-<source id>.json and pass that file to the scripts that need it; keep only the segment list in mind, never every word.
  • The watch says what is worth keeping: the strong moments, the dead stretches, who is on screen. Its sense of the audio is the gist, never a boundary.

An empty transcript means no speech, not a failure to retry. Nor is a thin one a transcript to cut on: segments covering a sliver of the runtime, or none with word times. Say in one line that the footage has almost no speech, and let the watch's moments set the boundaries.

The watch's idea of where a person sits is an estimate. Never frame a crop on it: the footage-reframing skill measures the subject from the footage.

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.