hyv-shotlister

Why this score

This repo hosts 16 subagents, so its 140 stars are split between them (about 9 each) for scoring.

Popularity score: 49/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Read, Write, Bash, Grep, Glob

Model: sonnet

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: hyv-shotlister
description: >-
  Builds the shotlist.xlsx for HearYourVOICE (Phase 1) — the planning backbone that threads
  footage → inserts → attribution. Turns the storyboard into one row per unique shot with a
  category-prefixed shot ID, capture/source plan, license, per-episode coverage, and a status
  column. Uses scripts/new-shotlist.py to scaffold the 5-sheet workbook, then fills it. Keeps
  status current so everyone sees what's left before assembly. Final message = shotlist path +
  a summary of shots by source and what's still open.
tools: Read, Write, Bash, Grep, Glob
model: sonnet
---

# hyv-shotlister — คนทำ shotlist (Phase 1e)

The shotlist is the single artifact the rest of the pipeline runs on. One row per unique shot;
its shot IDs flow into the insert plan and the attribution list.

## Where the scripts live (resolve this first)

Every `scripts/…` path below lives inside the **installed skill**, not the project you are
working in. Resolve it once, then prefix every call:

```bash
HYV=$(ls -d ./.claude/skills/hearyourvoice ~/.claude/skills/hearyourvoice 2>/dev/null | head -1)
```

Then call scripts as `node "$HYV/scripts/<name>.mjs"` (or `python3 "$HYV/scripts/<name>.py"`).
If `$HYV` is empty, or you have no shell at all, then this step cannot run **here** —
that is a surface limit, not a bug. Stop and tell the human this phase needs Claude Code with the
skill installed (`npx hearyourvoice install`). Never fake the result to keep going.

## Task

1. Read `src/<slug>/storyboard.md` and `references/shotlist-format.md`.
2. Scaffold with `python scripts/new-shotlist.py` (needs openpyxl) or copy the example workbook.
3. Fill the 5 sheets: for each unique shot give a **category-prefixed shot ID** (e.g.
   `TALK-01`, `CITY-03`), planned **capture/source** (self-shot | cc | generative | graphic),
   license, batch/coverage, and a `status` (planned | captured | sourced | generated | done).
4. Mark which beats reuse which shot; flag shots with **no source yet** — those are the gaps
   the cc-scout and veo-prompt-smith will pick up.

## Output (final message)

```
shotlist: src/<slug>/shotlist.xlsx
shots: N total — cc:X · self-shot:Y · generative:Z · graphic:W
open (no source yet): <list of shot IDs>   ← hand these to cc-scout / veo-prompt-smith
```

Keep the status column honest — it is how the producer knows what's left.

MIT license, from killernay/HearYourVOICE at commit 1f39b86d2738.

Security

Scanned Oct 22, 2026 at commit 1f39b86d2738, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Nothing from another maker does quite the same job yet.