PulseJet AI

View saved version →

---
name: make-a-music-video
description: Take a song from upload to a compiled AI music video in PulseJet AI, in the order the pipeline enforces, confirming cost before every step that spends credits.
---

Use the PulseJet AI MCP tools in this order. Each stage is a real server-side gate: a later step fails until the earlier one is complete, so do not skip ahead.

1. **Find or create the project.** `list_projects` to see what exists; `create_project` for a new one. Note the project id; every later call needs it.
2. **Get the song in.** For a file the customer has, call `upload_song` with `filename` and `contentType` to receive an `uploadUrl` and `stagingKey`, have the customer PUT the file to that URL, then call `upload_song` again with the `stagingKey`. `trim_song` if only part of the track should be covered.
3. **Analyse.** `analyze_song` (free, but refused on a zero balance), then poll `get_analysis` until it reports BPM, key, sections and lyrics. Offer `update_transcript_line` for any mis-heard lyric, because lyrics feed the script.
4. **Creative direction.** `get_narrative_suggestions` or `brainstorm` for ideas, `list_themes` for the visual style, `update_project` to set them, then `approve_creative_direction`.
5. **Script and shot plan.** `generate_script`, review with `get_scenes` (edit with `update_scenes`), then `generate_shot_plan` and review with `get_shots`.
6. **Stills, then video.** Call `generate` with `stage: "thumbnails"` and `estimate: true`, read the quote (creditsNeeded, creditsAvailable, shortfall, shotsToGenerate) to the customer in plain words, and only on their yes call `generate` with `stage: "thumbnails"`. Check `get_thumbnails`, then `approve_thumbnails`. Repeat the same two calls with `stage: "videos"`: estimate first, state the numbers, wait for a yes, then start. Poll `get_generation_progress` with the returned `runId`; use `render_shot` for one shot that needs another pass. If the estimate says `outOfCredits`, say so and stop; do not start a run the balance cannot cover.
7. **Compile and review.** `compile_video` (this step does not spend credits), then `get_project` for the finished download link. Let the customer review the result. For a shot they want to change, use `get_shots` and the `review-and-fix-shots` skill; do not assign a numerical quality score.

Only five tools currently debit credits: `generate`, `render_shot`, `render_all_pending_videos`, `regenerate_shot_image` and `generate_image_candidate`. `analyze_song`, `generate_script`, `generate_shot_plan`, `generate_scene_thumbnails`, `get_narrative_suggestions`, `brainstorm` and `compile_video` do not (`analyze_song` and `generate_scene_thumbnails` are refused on a zero balance but charge nothing). `generate_scene_thumbnails` nevertheless requires the OAuth spend permission: it starts provider-backed image generation and its planned per-scene debit must not become a scope bypass. Before every step that debits credits: tell the customer what the step costs in plain words and wait for an explicit yes. For `generate` the numbers come from `generate` with `estimate: true` (it starts nothing); for every other spending step call `get_credit_balance` and `get_project`, whose `creditState` says whether the pending work is affordable. Never start a credit-spending step on an assumption.

Never invent project state. Read it with `get_project` or `get_shots` and report what the tool returned.

## Reporting a problem

When a step fails, a result looks wrong, or the customer is unhappy and it is not clear they want it passed on, offer to report it in one sentence rather than filing silently or letting it drop. Read back a one-sentence summary, and once they agree file it with `submit_feedback`, keeping their own words in `message` and passing the project id, the `shotId` and any `errorCode` the failing call returned, so nobody has to ask them for those later. The result carries the ticket key to quote back to them.

Whenever something goes wrong, l

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: review-and-fix-shots
description: Check a PulseJet AI project's generation progress, find shots that failed or look wrong, and fix them with the least spend, then recompile.
---

1. **Read the real state first.** `get_project` for the pipeline state, then `get_generation_progress` for per-shot status, and `get_shots` (use `summary: true` on large projects) for the detail. Report only what came back.
   When the customer asks to see a shot, call `get_shot_image` with its project and shot ids. That result displays the still and clip separately when available. A `video/mp4` URL is a video clip, not an image: do not place it in image Markdown. If the host does not show the media card, offer the separately labelled still and clip links, and do not claim the pixels or player appeared unless visible.
2. **Failed shots.** For a shot stuck in a failed state, `render_shot` re-renders it (`regenerateImage: true` also redoes the still). If it fails permanently and the customer wants to move on, `skip_shot` excludes it so the video can still compile.
3. **Wrong-looking shots.** Edit the prompt with `update_shot` (imagePrompt, negativePrompt, motionDescription) and re-render, or generate an alternative with `generate_image_candidate` and let the customer choose via `accept_image_candidate` / `reject_image_candidate`. Video alternatives use `accept_video_candidate` / `reject_video_candidate`.
4. **Use the customer's own material.** `change_shot_source` to `user_image` or `user_video`, then `upload_shot_image` or `upload_shot_video` through the presigned flow (`filename` + `contentType`, PUT to `uploadUrl`, finish with `stagingKey`). Stills must match the project's aspect ratio exactly.
5. **Order and structure.** `reorder_shots` with every shot id in the new order; `delete_shot` to remove one.
6. **Finish.** `compile_video` once every shot is rendered or skipped, then `get_project` for the download link.

Any re-render, regenerate or candidate step spends credits (compiling does not): check `get_credit_balance`, say what it costs, and get an explicit yes first. Prefer fixing one shot over re-rendering everything; `render_all_pending_videos` is the expensive path and needs its own confirmation.

## Reporting a problem

A shot that fails again after one re-render, a result the customer calls wrong, or anything in this flow that seems broken is worth reporting. If it is not clear the customer wants it passed on, offer in one sentence; read back a one-sentence summary and file it with `submit_feedback` once they agree, with their own words in `message`, the project id, the `shotId` concerned and the `errorCode` the failing call returned. Quote the ticket key from the result back to them.

If a fix is not working out, say that the problem can be reported from this conversation with `submit_feedback`; the customer does not have to go looking for a form.