Skills reference
These Claude Code skills come from the Vidmatic MCP server: a skill is a set of instructions the server hands your agent. Several of them record narrated demos.
How Claude Code skills run
In Claude Code each skill is a slash command named /mcp__vidmatic__<name>. In Cursor, ask the agent to call get_skill(name="<name>") and follow what comes back. The server serves skills, so an update reaches you the next time you run one, and nothing is copied into your repository.
Skills run in your repository, on your machine. Vidmatic does the video processing on its side, so no skill runs ffmpeg on your machine.
From a recording to work
| Skill | What it does | Claude Code | Cursor |
|---|---|---|---|
workstream_from_video | Turn a screen recording into one GitHub issue grounded in your code, then work it and prove it. | /mcp__vidmatic__workstream_from_video | get_skill(name="workstream_from_video") |
issue_intel | Read a recording and post what the user actually asked for, R1 to Rn, as one issue comment. | /mcp__vidmatic__issue_intel | get_skill(name="issue_intel") |
add_issue | File one or more issues in your own tracker, up to ten per run, grounded in your code, each queued on its own workstream board. | /mcp__vidmatic__add_issue | get_skill(name="add_issue") |
dispatcher | One loop run every 10 minutes from the folder that holds your checkouts: it files queued change requests in the right repo, then hands the ready issues of each repo you enable to one orchestrator that ships them in parallel lanes. | /mcp__vidmatic__dispatcher | get_skill(name="dispatcher") |
change_request_dispatcher | The older change request watcher: now runs one dispatcher tick that only files queued requests, and points you at the dispatcher loop. | /mcp__vidmatic__change_request_dispatcher | get_skill(name="change_request_dispatcher") |
Following the work
| Skill | What it does | Claude Code | Cursor |
|---|---|---|---|
workstream | Mirror your coding session live on Agent Workstreams, stage by stage. | /mcp__vidmatic__workstream | get_skill(name="workstream") |
workstreams | Nudge every stuck workstream: your agent checks each one and moves it forward or closes it. | /mcp__vidmatic__workstreams | get_skill(name="workstreams") |
auto-implement-beta | Beta: dispatch each subagent with a brief and evals; it finishes only with evidence they pass. No issue URL works every open issue in the repo. | /mcp__vidmatic__auto-implement-beta | get_skill(name="auto-implement-beta") |
auto-job-dispatcher | The older one-repo factory loop: now runs one dispatcher tick that only ships ready issues in the repo you are in, and points you at the dispatcher loop. | /mcp__vidmatic__auto-job-dispatcher | get_skill(name="auto-job-dispatcher") |
optimize | Find the detours in finished coding sessions, on your own machine. | /mcp__vidmatic__optimize | get_skill(name="optimize") |
Video proof and demos
| Skill | What it does | Claude Code | Cursor |
|---|---|---|---|
record | Record and narrate a demo of the change you just shipped, delivered to your Inbox. | /mcp__vidmatic__record | get_skill(name="record") |
before_after | Record one half of a before and after pair for a bug fix. | /mcp__vidmatic__before_after | get_skill(name="before_after") |
demo_user_journey | A narrated demo of the shortest new-user journey to a first win. | /mcp__vidmatic__demo_user_journey | get_skill(name="demo_user_journey") |
explain_implementation | On request: a narrated explainer of how a shipped change was built, from the ask through the decisions to the code. | /mcp__vidmatic__explain_implementation | get_skill(name="explain_implementation") |
audit_ux | A narrated UX critique of a live page, each finding circled on screen. | /mcp__vidmatic__audit_ux | get_skill(name="audit_ux") |
Your first run: record --init
/mcp__vidmatic__record --init is the first thing to run on a new machine. It records a short test demo, publishes it and prints its public link, which proves the whole pipeline. If your app needs a sign-in, it also saves that sign-in once so later skills can reuse it. The saved sign-in lives on your machine under ~/.vidmatic/sessions/. An unused one lasts about a day; when it expires, run record --init again.