agentleFS
yangzichaoyangzichao/JustSessions/.claude/skills/demo-video/SKILL.md

demo-video

Skill13 starsChanged 36 days agoMITView on GitHub

Record, edit, and publish the JustSessions homepage demo video with Scripts/DemoVideo, from an isolated copy of the app with sample sessions and a disposable SSH host. Use when re-recording the demo for a new release, changing its takes, cut, narration, or chapters, or remaking the poster or the social card from it.

  • Reads credentials

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use karpathy-coder, ai-act-readiness and 10 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.
  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    ai-act-readiness

    Also in 3 projects that use this

  • Hussain-ElfalahSkill

    c-level-agents

    Also in 3 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 4 projects that use this

  • +8 more from Hussain-Elfalah
  • Other versions28 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 28

    1. liaohch3/claude-tap★ 3.3ksame name
    2. microsoft/hve-core★ 1.6ksame name
    3. alinaqi/maggy★ 711same name
    4. alinaqi/claude-bootstrap★ 708same name
    5. getsentry/junior★ 421same name
    6. hmislk/hmis★ 245same name
    7. Kewton/CommandMate★ 44same name
    8. Hassaan146/claude-skills★ 18same name
    9. yzhao062/agent-config★ 16same name
    10. mrieck/demoday-claude-plugin★ 12same name

    18 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Update editing/timeline/scenes.py to the new takes.

    line 22
  2. Very specific:

    Honesty: Every action is real input to the real app.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 26 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

Demo video

Scripts/DemoVideo/demo-video runs every step. Read docs/development/demo-video.md first: requirements, what each setup step changes on the machine, take order, and teardown. This skill adds the workflow and the judgment calls.

Ask before these

  • record: it moves the pointer and types on the user's screen, and a take aborts if anything else comes to the front. Ask the user to step away and turn on Do Not Disturb, then run it.
  • setup remote and teardown: they change the shared test VM (a dev user, its hostname) and ~/.ssh/config.
  • reset: it opens the demo app's window on the user's screen.

Everything else (setup app|home|editing|sessions, clicks, voiceover, stills, render, web, poster, window-still) runs without taking over the Mac.

Workflow

  1. make build at the commit to show, then demo-video setup. If setup sessions reports the wrong counts, run the CLI that fell short in the demo home with environment/run_in_isolated_tmux.sh and read the screen it prints. A first-run notice or a folder-trust prompt that swallows the typed prompt has been the cause; mark it as seen in fixtures/cli_configs.py.
  2. demo-video record all, then demo-video clicks. After re-recording take A, update REFERENCE in editing/analysis/find_click_positions.py first.
  3. Update editing/timeline/scenes.py to the new takes. Its times are seconds into a take: a line's timestamp in $DEMO_WORK/takes/<take>.driver.log minus RECORDING STARTED in <take>.recorder.log. The mark lines name the moments the cut is built around.
  4. demo-video voiceover only for lines that changed, by id. Kokoro is not deterministic, so regenerating every line changes timing everywhere.
  5. demo-video stills at each scene's key moments; look at every still before rendering. Then demo-video render and watch the master with sound.
  6. Publish (below), then demo-video teardown once the user is done.

Judgment calls

  • Pacing. Moments that matter play at 1×: the click that resumes, the double-click that opens an agent, the drag, typed text. Pointer travel, CLI start-up, and waiting play faster, up to 3.2× in the published cut. Idle time before and after a take is cut.
  • Narration. One short sentence per beat, said as the thing happens on screen. Captions come from the narration's sentence timing and are placed on the whole video's clock, so a line that runs past its scene spills its audio and caption into the next one. Keep each line shorter than the footage it describes.
  • Camera. Zoom in when the point is small text, such as a sidebar row or a CLI's output; the published cut goes up to 1.85×. Between scenes of the same take, start at the camera the previous scene ended on. Check in stills that the pointer and the thing it acts on stay in frame.
  • Sample data. Sessions, projects, and replies are fixtures; change them in fixtures/ and environment/canned_model_server.py, never by recording real work. Before publishing, check the stills for real names, account paths, hostnames, or tokens. Everything on screen should be under ~/Projects in the demo home or on devbox.
  • Honesty. Every action is real input to the real app. Don't fake a state with an overlay or an edit; change the fixtures or the takes instead. Keep website/media/README.md truthful about what is canned.

Publish

  1. demo-video web website/media/justsessions-demo.mp4 and demo-video poster <seconds> website/media/justsessions-demo.jpg. The poster is a frame with no caption that shows the product at its best; it was the split view at 28.0 seconds.
  2. Chapter times: each chapter's data-start/data-end in website/index.html and the table in website/media/README.md come from scene starts in $DEMO_WORK/build/timeline.json.
  3. Length: the 0:53 label and the VideoObject name, duration, and uploadDate in website/index.html, and the length in docs/development/website.md and website/media/README.md.
  4. Provenance in website/media/README.md: recording date, app version and commit, the remote Claude Code version.
  5. Social card, if the poster moment changed or the app looks different: demo-video window-still <seconds> docs/images/demo-split-view.jpg, then recapture website/social/social-preview.png from website/social/preview.html as docs/development/website.md describes, and update the row in docs/images/README.md.
  6. Build the site with make website-check and check the homepage. Chapter jumps need byte-range responses, which python3 -m http.server doesn't send; check them on the published site after deploying.
  7. make verify, then follow AGENTS.md for the pull request.

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.