Skip to content
Back to search

tough-crowd

MarketplaceWorks with Claude CodeGitHub

Your agent directs the film. Three blind judges decide what gets reshot. A director layer for HyperFrames.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/reuben-alex--tough-crowd/badge.svg)](/listings/reuben-alex--tough-crowd)

HTML

<a href="/listings/reuben-alex--tough-crowd"><img src="/api/listings/reuben-alex--tough-crowd/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need Node 22 or newer, FFmpeg 5.1 or newer, the HyperFrames skills (`npx hyperframes skills`) and a harness that can start subagents. Claude Code can.

Install it from inside Claude Code:

/plugin install tough-crowd --marketplace Reuben-Alex/tough-crowd

Or clone this repository and load it from the folder:

claude --plugin-dir /path/to/tough-crowd

Then ask for a film:

/tough-crowd:direct Make a 15-second launch film for our notes app. Warm, quiet, no voice-over.

You get the film, a `PANEL.md` with every judge's verdict on every shot, and a delivery note that leads with anything the panel still rejects.

<details> <summary>FFmpeg is installed but not found</summary>

Set `FFMPEG_PATH` and `FFPROBE_PATH` to the two executables. The tool uses those before it looks on `PATH`. </details>

<details> <summary>Using another harness</summary>

Point the harness at `skills/direct/` and run the tool with `node /path/to/tough-crowd/bin/tough-crowd.mjs`. The panel needs a way to start fresh agents that share no context with the author. </details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines
  1. {
  2. "name": "tough-crowd",
  3. "owner": {
  4. "name": "Reuben-Alex"
  5. },
  6. "plugins": [
  7. {
  8. "name": "tough-crowd",
  9. "source": "./",
  10. "description": "Direct product films shot by shot on HyperFrames and have a blind panel of judges accept or reject each shot."
  11. }
  12. ]
  13. }
README.md · README · 252 lines
  1. <p align="center">
  2. <img src="docs/assets/banner.svg" alt="Tough Crowd. Your agent directs the film. Three blind judges decide what gets reshot." width="100%">
  3. </p>
  4. <p align="center">
  5. <a href="LICENSE"><img alt="Licence: Apache-2.0" src="https://img.shields.io/badge/licence-Apache--2.0-3b82f6"></a>
  6. <img alt="Node 22 or newer" src="https://img.shields.io/badge/node-%E2%89%A5%2022-5fbf8f">
  7. <img alt="No runtime dependencies" src="https://img.shields.io/badge/dependencies-0-5fbf8f">
  8. <a href="https://hyperframes.heygen.com"><img alt="Built on HyperFrames" src="https://img.shields.io/badge/built%20on-HyperFrames-1c1c20"></a>
  9. <img alt="Works as a Claude Code plugin" src="https://img.shields.io/badge/Claude%20Code-plugin-1c1c20">
  10. <img alt="Status: early" src="https://img.shields.io/badge/status-early-ef6a5b">
  11. </p>
  12. <p align="center">
  13. <a href="#quick-start">Quick start</a> ·
  14. <a href="#how-it-works">How it works</a> ·
  15. <a href="#what-the-judges-see">What the judges see</a> ·
  16. <a href="#does-it-work">Does it work?</a> ·
  17. <a href="#the-tool">The tool</a> ·
  18. <a href="#limits">Limits</a>
  19. </p>
  20. ---
  21. Coding agents can already render video. What they make tends to look like slides: a centred
  22. card, even pacing, no camera, and an agent that marks its own work as finished.
  23. **Tough Crowd** is a plugin that fixes the second half of that. It makes the agent direct a
  24. product film shot by shot on [HyperFrames](https://hyperframes.heygen.com), then puts the film
  25. in front of three judges who have never seen the code, the conversation or each other. Any shot
  26. two of them reject goes back to be fixed.
  27. <p align="center">
  28. <img src="docs/assets/demo.gif" alt="A 15-second product film for a made-up notes app called Tally: messy meeting notes turn into a clean task list." width="720">
  29. </p>
  30. <p align="center"><sub>
  31. A 15-second film for Tally, a product that does not exist, directed and built by a coding agent.<br>
  32. This is the cut after three panel runs. The judges still reject its second shot, and the agent had to say so on delivery.
  33. </sub></p>
  34. ## Why
  35. - **Agents are generous critics of their own work.** A fresh judge with only the brief and the
  36. frames is not.
  37. - **One judge is noisy.** Three judges and a majority are steadier.
  38. - **"Make it better" is not a note.** Judges must give a time, a place in the frame, the problem
  39. and the change, so the agent has something exact to fix.
  40. - **A film that was changed after judging was never judged.** The tool checks the delivered file
  41. against the one the panel saw.
  42. ## Quick start
  43. You need Node 22 or newer, FFmpeg 5.1 or newer, the HyperFrames skills (`npx hyperframes skills`)
  44. and a harness that can start subagents. Claude Code can.
  45. Install it from inside Claude Code:
  46. ```
  47. /plugin install tough-crowd --marketplace Reuben-Alex/tough-crowd
  48. ```
  49. Or clone this repository and load it from the folder:
  50. ```
  51. claude --plugin-dir /path/to/tough-crowd
  52. ```
  53. Then ask for a film:
  54. ```
  55. /tough-crowd:direct Make a 15-second launch film for our notes app. Warm, quiet, no voice-over.
  56. ```
  57. You get the film, a `PANEL.md` with every judge's verdict on every shot, and a delivery note
  58. that leads with anything the panel still rejects.
  59. <details>
  60. <summary>FFmpeg is installed but not found</summary>
  61. Set `FFMPEG_PATH` and `FFPROBE_PATH` to the two executables. The tool uses those before it looks
  62. on `PATH`.
  63. </details>
  64. <details>
  65. <summary>Using another harness</summary>
  66. Point the harness at `skills/direct/` and run the tool with
  67. `node /path/to/tough-crowd/bin/tough-crowd.mjs`. The panel needs a way to start fresh agents that
  68. share no context with the author.
  69. </details>
  70. ## How it works
  71. ```mermaid
  72. flowchart LR
  73. A[Brief] --> B[One idea]
  74. B --> C[Shot list]
  75. C --> D[Build on<br>HyperFrames]
  76. D --> E{Blind panel<br>3 fresh judges}
  77. E -- "2 of 3 reject a shot" --> F[Fix those<br>shots only]
  78. F --> E
  79. E -- "nothing rejected,<br>or 3 runs used" --> G[Deliver the judged file<br>and PANEL.md]
  80. ```
  81. | Step | What happens |
  82. | --- | --- |
  83. | 0. Brief | The request is saved word for word as `BRIEF.md`. The judges read this, not the agent's summary of it |
  84. | 1. Source | A public product is captured with HyperFrames, not redrawn from memory |
  85. | 2. One idea | One sentence: the single thing the viewer watches change |
  86. | 3. Direction | `DIRECTION.md` holds the shots. Each one names its hero, its share of the frame, the hold, and what causes the next move |
  87. | 4. Stage and type | One of three stage presets and three type pairings, all from fonts HyperFrames already bundles |
  88. | 5. Build | With the HyperFrames skill. Every object has its own pose in every shot |
  89. | 6. Stock check | `npx hyperframes check` passes |
  90. | 7. Panel | Three fresh judges, three runs at most. See below |
  91. | 8. Deliver | The judged file, `PANEL.md`, and a note that leads with anything still rejected |
  92. ### The house rules
  93. 1. **Judges are blind.** Each is a new agent given one brief and a folder of frames. No code, no
  94. conversation, no earlier rounds, no other judge's answer.
  95. 2. **Majority rejects.** A shot two of three judges reject is rejected.
  96. 3. **Three runs at most,** with new judges every time. Only rejected shots force another run.
  97. 4. **Fix what was rejected.** Accepted shots are left alone.
  98. 5. **The delivered file is the judged file.** `verify` compares checksums and refuses a film the
  99. panel did not see.
  100. 6. **Rejections are said out loud.** After the third run a film may be delivered with open
  101. rejections, and the delivery note must lead with them.
  102. ## What the judges see
  103. Not the video. Each judge gets time-stamped frame sheets at four frames a second, plus closer
  104. strips across every shot change:
  105. <p align="center">
  106. <img src="docs/assets/frame-sheet.jpg" alt="A frame sheet: twelve time-stamped frames from 6.0 to 8.75 seconds showing note lines turning into task rows one at a time." width="820">
  107. </p>
  108. And this is the kind of note that comes back. It is a real one, from the film above:
  109. > **P0** · 2.5 to 4.8 s · whole frame.
  110. > The bottom 35 to 40% of the frame is dead stage for 2.3 s. The "lunch?? thai pizza" line sits
  111. > about 40 px from the top edge in soft focus, so the one non-task line is the most prominent
  112. > note above the prompt.
  113. > **Change:** reframe so the prompt bar sits on the lower third, with four or five full note
  114. > lines above it and a clean margin of at least 90 px at the top.
  115. `tally` turns the three answers into one `PANEL.md`:
  116. ```
  117. # Panel result: round 3 of 3
  118. **Rejected shots: 1 of 5.**
  119. **Reaches the bar: no** (0 of 3 judges).
  120. **Not judged: motion at speed, and sound.**
  121. ```
  122. ## Does it work?
  123. Not yet, on the evidence so far. Two trials of five planned are done, and they split. The full
  124. record is in [`bench/results.md`](bench/results.md).
  125. Each brief goes to two agents: one with the stock HyperFrames skills, one with Tough Crowd.
  126. Three new judges then compare the two films under neutral names.
  127. | | Brief 1: Tally, a notes app | Brief 2: Ferry, a command-line tool |
  128. | --- | --- | --- |
  129. | Blind comparison | Tough Crowd preferred, 3 of 3, each "clearly" | Stock preferred, 3 of 3, each "clearly" |
  130. | The project owner, also blind | Tough Crowd | Stock |
  131. | Criteria Tough Crowd won | Composition, payoff, stage, typography, rhythm, story | Story only |
  132. | Rejected shots in its own three panel runs | 2 of 5, then 1, then 1 | 3 of 4 every run, a different set each time |
  133. | Judges who saw it alone and said it reaches the bar | 0 of 9 | 0 of 9 |
  134. What that shows:
  135. - **Brief 1 does not count as transfer.** The skill's worked example used the same product. The
  136. example has since moved to a product outside the test set; brief 2 is the first real test,
  137. and it was lost.
  138. - **The fix loop can churn.** On brief 1 it moved the film. On brief 2 each revision fixed the
  139. shots it was told about and broke or exposed others.
  140. - **Neither film reached the bar.** Judges preferred one film or the other, but all eighteen who
  141. saw a Tough Crowd film on its own said it falls short of a top-tier studio launch film.
  142. The test stops after a second lost brief, by the rule in [`bench/PROCEDURE.md`](bench/PROCEDURE.md).
  143. ## The tool
  144. ```
  145. tough-crowd packet <film> --brief BRIEF.md --direction DIRECTION.md [--round <n>] [--silent] [--refs <dir>]
  146. tough-crowd packet <film> --ab <other film> --brief BRIEF.md [--silent]
  147. tough-crowd tally <packet folder> [--panel-out <file>]
  148. tough-crowd verify <film> [--panel <PANEL.md>]
  149. ```
  150. | Command | Does | Exit code |
  151. | --- | --- | --- |
  152. | `packet` | Writes the judges' brief and time-stamped frame sheets under `.director/panel/`. With `--ab`, two films under neutral names | 0, or 2 on bad input |
  153. | `tally` | Reads the three answers and writes `PANEL.md` | 0 nothing rejected, 1 a shot is rejected, 2 on bad or missing answers |
  154. | `verify` | Confirms the file is the one judged and prints what the delivery note must lead with | 0, or 2 if it is not the judged file |
  155. Run the commands from the film's project folder: `packet` writes under `.director/` there, and
  156. `tally` and `verify` use the `PANEL.md` there. `--refs <dir>` shows the judges reference frames
  157. you supply as examples of the look you want. `skills/direct/references/panel.md` has the full
  158. procedure.
  159. The package is not on npm yet. Run it with `node bin/tough-crowd.mjs`.
  160. ## What it is not
  161. It does not render, capture, generate voice or music, or replace HyperFrames. HyperFrames does
  162. all of that. Tough Crowd is the director and the screening room, nothing else.
  163. ## Limits
  164. - **Judges see stills.** They cannot judge motion at speed or sound, and every `PANEL.md` says so.
  165. A person watching the film is still the only check on how it feels.
  166. - **Judges are noisy.** Three judges and a majority reduce that; they do not remove it.
  167. - **It costs more.** In the trial each panel run used about 260k tokens (three judges at about
  168. 87k each). The fully judged film came to about 1.25 million tokens, against about 284k for the
  169. stock build.
  170. - **Films up to about 30 seconds**, landscape. Longer films are not what the panel is tuned for.
  171. - **Public products only** for capture. Logged-in screens have to be supplied by the person.
  172. ## What's inside
  173. ```
  174. skills/direct/ the directing skill: the pass, staging rules, stage and type presets
  175. bin/, src/ the tool: packet, tally, verify
  176. templates/ the briefs the judges read
  177. examples/stages/ a HyperFrames project showing the three stage presets
  178. bench/ five test briefs, the procedure, and the results
  179. docs/superpowers/ the design and the build plan
  180. ```
  181. ## Roadmap
  182. - Run the three remaining test briefs, unless a second brief is lost first.
  183. - Stronger staging rules for camera movement, and stage presets with more depth.
  184. - Publish to npm.
  185. ## Development
  186. ```
  187. node --test
  188. ```
  189. The tests need FFmpeg. `examples/stages/` is a HyperFrames project showing the three stage
  190. presets; check it with `npx hyperframes check` from that folder.
  191. ## Licence
  192. Apache-2.0. HyperFrames is a separate project by HeyGen, also Apache-2.0. Tough Crowd is not
  193. affiliated with or endorsed by HeyGen or Anthropic.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.