agentleFS
Sign inStart free
bloxy-studiosbloxy-studios/shorts-studio/skills/analyze/SKILL.md

analyze

Skill0 starsChanged 42 days agoMITView on GitHub

Real audiovisual analysis of a source video — transcript coverage, speech activity, pauses, audio events, scene cuts, persistent face tracks with head-orientation and mouth-activity evidence, speaker↔face links, and timestamped frame sheets that you inspect and annotate. Produces evidence and ranked moment candidates. Use when the user wants to understand a video's strongest moments or before any clip selection.

70 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, write and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 6 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 projects that use this

  • H-mmerSkill

    submit

    Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • JosBen74Skill

    osint

    OSINT-sökning och informationsinhämtning från öppna källor för Länsstyrelsen VG

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure the source is ingested and transcribed (ingest, transcribe.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “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

Analyze

Rules: ${CLAUDE_PLUGIN_ROOT}/references/rules.md. CLI: "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio".

0. Engine check

The commands below run the Shorts Studio engine. Installed as the Claude Code plugin it is already present and shorts-studio is on the Bash PATH. If shorts-studio doctor is not found (for example, this skill was added with npx skills add), ask the user before installing anything, then:

  • Claude Code: /plugin marketplace add bloxy-studios/shorts-studio → /plugin install shorts-studio@shorts-studio.
  • Other agents: git clone --depth 1 https://github.com/bloxy-studios/shorts-studio ~/.shorts-studio/engine and read every ${CLAUDE_PLUGIN_ROOT} path below as ~/.shorts-studio/engine.

Then run shorts-studio doctor --setup once (project-local runtime; never sudo or global installs).

Steps

  1. Ensure the source is ingested and transcribed (ingest, transcribe; see the clip skill).
  2. shorts-studio analyze <project> — prints coverage, scenes, face tracks, and sheet paths.
  3. Inspect every overview sheet image with Read. Increase density where something happens: shorts-studio analyze <project> --tiles 48 (more frames) and candidate previews. Record each real visual observation with shorts-studio analyze note <project> --kind <kind> --at <time> --detail "<what you saw>" --confidence <0-1> --sheet <id>. Kinds: reaction, action, on-screen-text, screen-demo, gesture, laughter, scene, quality-issue, gaze.
  4. shorts-studio candidates <project> --count N --duration A-B and shorts-studio candidates preview <project> --top N; read the previews; refine with candidates note (truthful titles/hooks, boundaries, reject weak ones).
  5. Summarize for the user: ranked moments with times, why each holds, evidence type (transcript / audio / visual-cv / visual-agent), confidence, and coverage limitations.

Honesty

  • analysisLevel is audiovisual-agent only where you recorded observations; audiovisual-cv for deterministic CV/audio evidence; transcript-only when there is no usable picture — then say reactions and visual jokes are unverified.
  • Sampled frames are not frame-by-frame viewing. Say how many frames were inspected.

Completion check

analysis/<source>/coverage.json exists with transcript full, audio full, and visual agent-inspected (or you stated why it is cv-only/none), and analysis/candidates.json lists ranked candidates with evidence.

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.

Check your setup, free