cms-lab

Plugin cms-lab from marketplace cms-f26 in columbia-university-school-of-the-arts/cms-f26. Commands read from the repo's manifest — 3 days ago.

Skills (8)

• absa

  Week 5 workshop: read five critic reviews of a film the student chooses with aspect-based sentiment analysis. The student writes the categories and annotates one review by hand first; then Claude annotates all five, every opinion quoted verbatim and checked by absa.py, and the result becomes a chart

• editor

  Open the fleet editor: a page on the student's own machine that shows their workflow as a pipeline and opens each agent, workflow stage, and skill in a form, with a draft from Claude and a Save that writes only what meets the course contract. Run it in Claude Code in the fleet repository.

• frame-diff

  Show what a video encoder stores for each frame and how the decoder rebuilds it: framediff.py re-encodes the student's clip as P-frames and renders labeled panels (decoded video, motion vectors, what each frame stores, the decoder's prediction, the previous frame) over a timeline of bytes stored per

• init

  Ready the student's machine for the CMS course lab: check and install every tool the course has introduced so far (git and GitHub sign-in, Python, FFmpeg, yt-dlp's JavaScript runtime, ImageMagick for on-screen text, Git LFS, monolith, mpv for stepping through video frame by frame, a recent yt-dlp, a

• research-repo

  Week 7: make the student's fleet repository the home of their research, with their working thesis, an intake folder, sources stored in Git LFS, and the gate that checks each source's note on every push. Brings the clone they already have up to the course starter by merging it, writes the first thesi

• scene-detect

  Build and investigate an interactive shot-boundary detector for the CMS video workshop: invent a rule, tune sliders, inspect FFmpeg clips, and compare methods when the instructor releases them. Works in a local lab folder, ~/cms-lab/scene-detect, not in a repository.

• tmdb

  Week 4 workshop: ask The Movie Database a question about film history, such as the rise and fall of a genre, after stating in one sentence how each thing is counted, then read the chart against that definition. Works in ~/cms-lab/tmdb, not in a repository, and keeps the API token in a .env file.

• workflow

  From Week 10: turn the student's corrected workflow/workflow.md into a workflow that runs: one stage per step under workflow/stages/, each saying what it reads, makes, runs, and how it is checked, built to the course's stage contract. Run it in Claude Code in the fleet repository. Safe to run again.