Demo & Video Producer

What it does

Demo & Video Producer is a Cursor agent playbook named video-producer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The video-producer agent writes what you say on camera. social-media-strategist writes LinkedIn text. This role owns the 90s product demo, a Loom walkthrough outline, and three honest titles.

90-second demo script, Loom outline, YouTube titles. Writes spoken demo scripts, shot lists, and titles. Does not invent view counts. You still hit record.

Why it exists

A pile of agent files is not a team. video-producer exists so one job, demo & video producer, has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: Product Demo & Loom Scripts; Eugene Schwartz 5 Stages of Customer Awareness; Marketing Deliverable Auto-Save & Repo Sync. Commands that adopt this role: /demo-script: 90-Second Demo and Loom Script; /whats-new: Ship-to-Customer Narrative; /launch: Product Launch Strategy & Multi-Channel Kit.

When to use it

• Need a demo and keep rambling
• YouTube or Loom with no script
• Launch video that must match CURSOR.md

When not to use it

• Do not ask video-producer to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/video-producer is on disk.
2. Run /demo-script: 90-Second Demo and Loom Script, or start a chat and tell Cursor to adopt the video-producer role.
3. The agent should read: Product Demo & Loom Scripts; Eugene Schwartz 5 Stages of Customer Awareness; Marketing Deliverable Auto-Save & Repo Sync.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are video-producer. Need a demo and keep rambling. Read demo-video-scripts before you edit."

Or let the pipeline invoke it: /demo-script: 90-Second Demo and Loom Script.

Capabilities you should actually see: Spoken 90-second scripts with timing

Example output

• video-producer should leave files or a written verdict, not a vibe check. Spoken 90-second scripts with timing Shot lists and on-screen text
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Spoken 90-second scripts with timing
• Shot lists and on-screen text
• Loom outlines for feature walkthroughs
• YouTube title options without fake social proof
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using video-producer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.