Sloosh

View saved version →

---
name: ad-variants
description: Make sets of product ad images with Sloosh in feed and story sizes, such as several angles or hooks for one offer, with an optional headline and call to action on the image. When the image needs words, it makes a clean plate for each placement first, then text variants on the chosen plate, and checks the spelling of every word. Use when the user wants ad creative, ad variants, the same ad in several aspect ratios or a headline on an ad image and the Sloosh tools are connected. Not for one product photo with no copy (use product-imagery) or for changes to an image Sloosh already made (use creative-iteration). Not for resizing a finished ad the user already has (use the sloosh-image reframe-outpaint or sloosh-ads reference-ad-remix skill if it is installed). For a full product launch with ad copy for each placement, use the sloosh-shopify launch-ads skill if it is installed. For sale banners, hook test grids, comparison, review or before and after ads, use the sloosh-ads skills if they are installed.
---

# Ad variants

Use this skill to plan a set of Sloosh ad images. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

This skill makes images only. It posts nothing to an ad platform.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_generation` or `generate` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its colours, type style and channels.
- If the user gives a photo of a person, a third-party image, a reference ad or a style reference, ask the user to confirm they may use it. For a person, ask the user to confirm that the person agreed to appear in an AI-made ad. Ask before any quote. Do not use a photo of a child or of a public figure. If the user declines or cannot confirm, explain why and stop.
- Use a reference ad only for its layout and style. Never copy its logos, characters or words.

## Steps

1. Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
2. Collect the brief: the product, the offer or message, the placements, how many variants and the exact words for the image, if any. Ask only for what is missing.
3. Map each placement to an aspect ratio. Use 9:16 for Reels, TikTok and Stories. Use 1:1 or 4:5 for feeds. For other placements, use the table in `references/placements.md`.
4. Decide which one thing changes between variants, such as the hook, the background or the layout.
5. Get product images the same way as the `product-imagery` skill:
    - For a local file, follow the server's upload instruction.
    - For a public HTTPS URL, use `import_asset`.
    - To reuse an asset, find it with `list_assets`.

   Look at the product photo with `view_asset`. List what must stay exact: the label text, the logo, the colours and the shape.
6. Optional: search `list_spaces` for a published ad grid or ad poster Space. Choose by the Space description from `get_space`. If one fits, offer it and follow the `published-spaces` skill instead. If the user brings a finished image to resize, search `list_spaces` for an aspect ratio change Space and follow the `published-spaces` skill.
7. Call `list_models` with mode `image_gen`. Pick a model that takes a reference image and supports every aspect ratio you need. Use one model for the whole set, so the images match. Do not choose a model or estimate a price from memory.
8. If the user wants no words on the image, make one round of 

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

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: asset-manager
description: Find, import, check and name the images, videos and audio files in the user's Sloosh workspace, so other skills get a correct asset reference. Use when the user asks to find an asset they made or uploaded before, such as the photo from yesterday or their logo, to bring a file or a public link into Sloosh, to see what an asset shows, to get the outputs of an earlier generation or Space run, or to save Sloosh files on their computer, and the Sloosh tools are connected. It makes nothing new and costs nothing. Not for new images or videos (use product-imagery or product-video), not for changes to a result (use creative-iteration) and not to run a ready-made recipe (use published-spaces).
---

# Asset manager

Use this skill to find, import, look at and name assets in the user's Sloosh workspace. An asset reference is a kind and an id. Kind workspace is the library. Kind generated is a Sloosh output. Other skills pass these references to their tools. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

This skill costs nothing. It finds, imports and reads assets. It starts no generation and no Space run. The skill that makes something quotes its own work and asks for approval.

## Before you start

- If the Sloosh tools are not available (no `get_connection` or `list_assets` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- Call `get_connection` once in the conversation if you have not called it yet. It names the workspace this connection uses.
- For the file types, size limits and the upload steps, read the `assets` guide with `get_guide`.

## When to use it

- Another skill needs a product photo, a logo, a style reference, a start frame, a source video or an audio file, and the user has not given one yet.
- The user points at something that already exists, such as "the photo I uploaded yesterday" or "my logo".
- A card message names a generated asset, and the next step needs its link.
- The user wants the outputs of an earlier generation or Space run, or wants the files on their computer.

To make a new product photo, use the `product-imagery` skill. For a clip, use the `product-video` skill. For an ad set, use the `ad-variants` skill. To change a result, use the `creative-iteration` skill. To run a ready-made recipe, use the `published-spaces` skill.

## Rights

- Import or upload only files the user owns or may use.
- Before you import a photo of a person, a third-party image, a social post or another brand's ad, ask the user to confirm they may use it. For a person, ask the user to confirm that the person agreed to appear in AI-made work.
- Before you import an audio file with a person's voice, ask the user to confirm that the person agreed to its use. Before you import music, ask the user to confirm they own it or hold a licence for it.
- Do not import a photo of a child or of a public figure.
- If the user declines or cannot confirm, explain why and stop.

## Steps

1. Find out what the asset is for. Note its role, such as product photo, logo, style reference, start frame, end frame, source video or audio. Note its type: image, video or audio. Ask only for what is missing.
2. Get the asset from its source:
    - A local file: follow the server's upload instruction for this client. Wait for the asset ids that the upload returns, or for the user's message with them. Never guess an id.
    - A public HTTPS link to the file itself: call `import_asset` with the link and a name from the naming rule below. A web page link is not a file link. Ask the user for the direct file link, such as the image address.
    - A link to an Instagram Reel, 

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

View saved version →

---
name: batch-pipeline
description: Run one published Sloosh Space over many inputs, such as a list of products, a folder of product photos or the rows of a table, with one run per item, in rounds of at most 8 runs with one approval per round. Use when the user wants the same Space or recipe on every item, says for all 40 products, every colour, the whole catalogue or batch, and the Sloosh tools are connected. Not for one run of a Space (use published-spaces), not for a single direct image (use product-imagery), not for changes to a result the user has already seen (use creative-iteration), and not to build a new Space, which this skill does not do.
---

# Batch pipeline

Use this skill to run one published Sloosh Space over a list of items. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

One Space run makes one item's outputs. The Space fixes its own models and steps. This skill does not build or change a Space, and it does not join outputs into one file.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_space` or `run_space` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
- Note the allowance left from `get_connection`. It is in millicredits. Divide it by 1000 to get credits. It is a daily allowance, and `get_connection` says when it resets.
- If the user gives a credit budget for the batch, note it too.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its voice in any brief you write.

## Steps

### Choose the Space

1. Call `list_spaces` with a search term from the request. Narrow by output type when you know it. Pass scope own when the user asks for their own Spaces.
2. Call `get_space` on the best matches. Describe one to three options in plain words and let the user choose. Choose by the description, the output type and what the form needs.
3. If no Space fits, tell the user. This skill does not build a Space. For one or two stills, offer the `product-imagery` skill.
4. Call `get_space_input_schema` for the chosen Space. Sort its fields into two groups: the fields that change per item, such as the product photo or the product name, and the fields that stay the same for every item, such as the aspect ratio or the style.

### Build the item list

5. Get the list from the user: names in chat, image URLs, workspace assets or the rows of a table they share. Give each item a short, unique item id from its own data, such as the SKU, the product name or the file name. Use only lowercase letters, digits and hyphens. If two items give the same id, add the row number.
6. Ask for the values of the fields that stay the same once. Ask for missing per-item values once, as one list. For a select field, pick one of its options. Do not type free text into a select.
7. Before you import or pass a person's photo, a third-party image, reviews, a reference ad or a style reference, ask the user to confirm they may use it. Ask once for the whole list, before any quote. Do not use a photo of a child or of a public figure. If the user cannot confirm an item, drop that item and tell the user.
8. For each image, reuse an asset from `list_assets`, use `import_asset` for a public URL, or follow the server's upload instruction for a local file. Look at each image with `view_asset` before its round. Drop an image that does not show the item, and tell the user.
9. Show the user the item list with each item id and its per-i

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

View saved version →

---
name: creative-iteration
description: Improve an image or video that Sloosh already made and the user has seen, in up to 3 rounds. It fixes one thing with an edit, re-rolls near a good option, blends two results, tries another model or seed, or goes back a step, with a quote for each round. Use when the user reacts to a Sloosh result, such as "the label is wrong", "more like the second one", "try again but warmer" or "make the video slower", and the Sloosh tools are connected. Not for a first image or clip (use product-imagery or product-video), and not for a retouch of a photo or a change to a clip the user brought (use the sloosh-image image-edit-retouch skill or the sloosh-video video-extend-edit skill if it is installed).
---

# Creative iteration

Use this skill to improve a Sloosh result the user has already seen. Each round makes one focused change, keeps what worked and gets its own quote. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_generation` or `generate` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Keep its colours, voice and claims in every fix.
- If the user adds a new reference in a round, ask the user to confirm they may use it. This applies to a photo of a person, a third-party image, a reference ad or a style reference. Ask before any quote. Do not use a photo of a child or of a public figure as a person reference. If the user declines or cannot confirm, explain why and stop.

## Steps

1. Find the result. For a generated asset named in a card message, call `get_asset` with its kind and id. Use the returned URL. Reuse other assets from `list_assets`. Call `import_asset` for a public HTTPS URL. For a local file, follow the server's upload instruction for this client.
2. Look at the result with `view_asset`. For a video, `view_asset` has no preview. Ask the user what they see in the card, or look at the start-frame still if one exists. Name the defect or the wish in one sentence. Say what changes and what stays. Ask the user to confirm.
3. Get the original prompt and settings from the conversation. The `quote_generation` result repeats them in its input. If they are lost, write the prompt again from what you see. Ask the user for the model and the seed if they matter.
4. Classify the feedback and choose one route: edit one thing, shift the feel, re-roll near a good result, blend two results, edit or extend a clip, or go back a step. Read `references/routes.md` for the route table, the model choice and the prompt skeletons.
5. If the direction is wrong, do not patch. Follow the `product-imagery` or `product-video` skill with the corrected brief. For a set of ad sizes, follow the `ad-variants` skill.
6. If the user wants many directions from one image, or the same defect came back after a round, search `list_spaces` for a Space built for it. Search for terms such as variation grid, relight or skin retouch. Choose by the description from `get_space`. Use the Space path below. If no Space fits, use the direct path.
7. Write the fix prompt. Keep the exact-keep lines of the original prompt. For a short or vague change, call `enhance_prompt`. Show the user the rewrite. Do not call it for a video edit or extend.

## Direct path

1. Call `list_models` with the mode the route needs: `image_

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

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: launch-film
description: Direct and render a premium SaaS or product launch film in Remotion on the user's computer, from voiceovers, reference videos, brand assets, a website URL and a local SFX library, with match cuts on every scene change, 3D website fly-overs, kinetic type, SFX cue sheets and mastered 1080p or 4K delivery. Use when the user wants a launch video, a product promo, SaaS motion graphics, a cinematic animation of their site or app, a match-cut edit to a voiceover, or the next part of a multi-part launch film, even if they never say Remotion. Not for a single generated clip, talking-head or UGC edits, caption-only clips or slideshows, a 10 to 40 s walkthrough or feature announcement rebuilt from the app's real screens with no voiceover and no Remotion project (use saas-product-video), a 10 to 20 s physical product reveal (use product-reveal) a stylised beat-synced film under 30 s (use sloosh-motion-director) or a film built in code with no voiceover (use motion-film-code), when the Sloosh motion pack is installed.
---

# Launch film

You are the director, motion designer, editor and sound designer of a short premium launch film. The output is an MP4 (1080p, and 4K when asked) whose every scene boundary is a designed match cut, whose visuals lock to the voiceover's real word timings, whose UI is a faithful rebuild of the product, and whose sound comes only from the user's own SFX library (no music unless the user asks).

The method was proven on the Sloosh launch film (see `references/examples/`). It works because three things are measured instead of guessed: **what the voiceover says and when** (transcription), **where things are in each image** (pixel measurements for match cuts) and **what each sound does over time** (envelope peaks). Keep that discipline.

## Requirements

This skill runs on the user's computer. Before you start, check that you can run shell commands and that these are installed: Node.js with `npx`, `ffmpeg`, and Python 3 with numpy and Pillow. `scripts/transcribe.sh` needs `whisper-cli` and a speech model at `${WHISPER_MODELS:-~/.cache/whisper-cpp}/ggml-small.en.bin`; it stops with setup steps when either is missing. Ask the user before you install whisper-cpp (`brew install whisper-cpp` on macOS) or download the model from https://huggingface.co/ggerganov/whisper.cpp.

- If you cannot run shell commands on the user's own computer (a remote sandbox does not count), tell the user that the film needs a coding agent that runs on their computer. Offer the `product-video` skill for a single generated clip instead.
- Remotion is free for individuals, non-profits and companies with up to three employees. Larger for-profit companies need a Remotion company license. Tell the user this once before you scaffold the project.
- For Remotion API details beyond this skill, Remotion publishes its own agent skills (`npx skills add remotion-dev/skills`). Suggest them; do not install them unasked.

Paths in this skill are relative to this skill's folder.

## Inputs to gather

Look in the user's folder before you ask anything. Typical contents:

| Input | Used for |
|---|---|
| Voiceover audio (`PART 1.mp3`, ...) | the timeline; the edit is cut to it |
| Reference videos | rhythm, transitions, layout language |
| Asset notes, script, images, generated clips | story beats and imagery |
| Logo (SVG preferred) | wordmark animation, end card |
| Website URL | brand tokens, real UI, real feature names |
| SFX library folder | the only sound source |
| Pasted "master prompts" | creative direction; translate palettes to the brand |

Run `python3 scripts/inventory.py <folder> [<sfx_folder>]` for a one-shot summary (durations, codecs that need transcoding, image sizes, documents). Ask the user only when something is really missing (for example, no voiceover and no script). Otherwise pick sensible defaults and say what you chose.

## Pipeline

Do these steps in order. Each step names the script or reference to

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

Referenced files: 80 — file references are metadata, not package contents.

View saved version →

---
name: product-imagery
description: Make new product photos with Sloosh, such as studio packshots, lifestyle scenes and hero shots of the user's own product, with the label, logo, colour and shape kept exact. Use when the user asks for a product image, a packshot, a lifestyle shot, a hero image, to put their product in a new scene or to improve an image prompt, and the Sloosh tools are connected. Not for ad sets with copy or several placement sizes (use ad-variants), for video (use product-video) or for changes to an image Sloosh already made (use creative-iteration). For shots of several products from a Shopify store, use the sloosh-shopify catalog-shoot skill if it is installed. For angle sets, colourways or marketplace white-background checks, use the sloosh-ecommerce skills if they are installed. To place a photo into a supplied scene photo and relight it, to shoot in the look of style references, or to edit, reframe or upscale an existing image, use the sloosh-image skills if they are installed.
---

# Product imagery

Use this skill to plan a Sloosh image request: one to four product photos, such as a packshot, a lifestyle scene or a hero shot. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_generation` or `generate` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its colours, style and brand line in the prompt.
- If the user gives a photo of a person, a third-party image or a style reference, ask the user to confirm they may use it. For a person, ask the user to confirm that the person agreed to appear in an AI-made image. Ask before any quote. Do not use a photo of a child or of a public figure. If the user declines or cannot confirm, explain why and stop.

## Steps

1. Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
2. Collect the brief: the product, the scene or background, the light, the aspect ratio and how many images (1 to 4). Ask only for what is missing. If the user gives no scene, offer a studio packshot on white.
3. Find the reference images, if any:
    - For a local file, follow the server's upload instruction for this client.
    - For a public HTTPS image URL, use `import_asset`.
    - For an image already in Sloosh, find it with `list_assets` or `get_asset`.
    - To judge a reference image, look at it with `view_asset`.
4. Look at the product photo with `view_asset`. List what must stay exact: the label text, the logo, the colours and the shape. Tell the user this list in one line.
5. Call `list_models` with mode `image_gen`. Pick a model whose limits fit the brief, such as reference image count and aspect ratio. Do not choose a model or estimate a price from memory.
6. Write the prompt from the craft rules below. If the prompt is short or vague, or the user asks to improve it, call `enhance_prompt` with the prompt, the mode, the model settings and the number of reference images. It is free. Show the user the rewritten prompt and let them change it. If `enhance_prompt` fails, follow its error. Then use your own prompt.
7. Call `quote_generation` for the brief. Set enhancePrompt to false, so the approved prompt and its keep line reach the model word for word. Use one quote for each distinct prompt or aspect ratio. One prompt with up to 4 images needs one quote.
8. Tell the user the credits and what they will get. If the quote 

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

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: product-video
description: Make one short product video clip with Sloosh from a prompt or a product image, such as a hero clip, a short ad shot or a plain product page loop. It can open on the user's exact still and add only motion, or use product photos as references. Use when the user asks for a product video, a clip, or to animate a product image, make a photo move or bring a still to life, and the Sloosh tools are connected. Not for a creator-style UGC ad (use ugc-storyboard) or a launch film rendered on the user's computer (use launch-film). Not for a named product effect such as an exploded view, a 360 spin, a float or a splash, a person speaking to camera, several shots cut into one film, a change to a clip the user already has or a morph between two stills (use the Sloosh video pack if it is installed). For a 9:16 Reel, TikTok or Short with a hook, use the sloosh-social reels-shorts-clip skill if it is installed. For product page videos for several store products, use the sloosh-shopify pdp-video skill if it is installed.
---

# Product video

Use this skill to plan one Sloosh video clip from a prompt, a start frame or product reference photos. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

Make one clip per request. This skill does not cut several shots into a film, make a person speak a script, make a named product effect, change a clip the user already has or morph between two stills.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_generation` or `generate` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its look and brand line in the prompt.
- If the user gives a photo of a person, a third-party image or a style reference, ask the user to confirm they may use it. For a person, ask the user to confirm that the person agreed to appear in an AI-made video. Ask before any quote. Do not use a photo of a child or of a public figure. If the user declines or cannot confirm, explain why and stop.

## Steps

1. Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
2. Collect the brief: the product, the motion or camera move, the aspect ratio, the length and whether the user wants sound. Ask only for what is missing. Write the brief back in three lines: what the clip shows, the motion and camera move, and the ratio, length and sound.
3. Find the product image, if any:
    - Reuse an asset from `list_assets` or `get_asset`.
    - For a local file, follow the server's upload instruction for this client.
    - For a public HTTPS image URL, use `import_asset`.
    - If there is no image yet, offer to make one with the `product-imagery` skill. That image has its own quote and approval.
4. Look at the image with `view_asset`. Tell the user in one line what will move and what stays exact: the label, logo, colours and shape. Never animate or change the label. If the image shows a person, ask the consent question from Before you start before any quote. If it shows a child or a public figure, do not use it. Tell the user why and stop.
5. Call `list_spaces` with output type video and a search such as product video or animate photo. Read the best match with `get_space`. If its description fits the brief, offer it beside a direct clip. If the user picks the Space, follow the `published-spaces` skill. If not, continue here.
6. Choose the image role. Use role start_frame when the clip must open on the user'

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

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: published-spaces
description: Find, quote and run a published Sloosh Space, a ready-made recipe such as an ad grid, a product video, a UGC-style set or a catalogue pack, and follow the run through its checkpoints to the outputs. Use when the user names a Space, asks for a Space or wants a ready-made Sloosh recipe and the Sloosh tools are connected. Not for a single direct image or clip (use product-imagery or product-video), not for a shot-by-shot UGC storyboard (use ugc-storyboard), not for changes to a result the user has already seen (use creative-iteration), and not when a pack skill owns the Space type, such as a UGC ad from a creator photo (ugc-video-ad), sale banners (sale-banner-set), testimonial, comparison or before and after ads, or seasonal creatives; use that skill from the Sloosh ads pack if it is installed.
---

# Published Spaces

Use this skill to find, quote and run a published Sloosh Space. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

One Space run makes one recipe's outputs. The Space fixes its own models and steps.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_space` or `run_space` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its voice in any brief you write.

## Steps

1. Call `list_spaces` with a search term from the request. Narrow by output type when you know it. Pass scope own when the user asks for their own Spaces. Without it, public Spaces from other workspaces appear too.
2. Call `get_space` on the best matches. Describe one to three options in plain words and let the user choose. Choose by the description, the output type and what the form needs. Compare holds only after the quote.
3. Note the runner from `get_space`. A legacy Space runs the same way, but it has no checkpoints.
4. Call `get_space_input_schema` for the chosen Space. Ask for the inputs it needs, in the order the form lists them. Ask only for what is missing.
5. Before you import or pass a person's photo, a third-party image, reviews, a reference ad or a style reference, ask the user to confirm they may use it. Ask before any quote. Do not use a photo of a child or of a public figure. If the user declines or cannot confirm, explain why and stop.
6. For an image input, follow the server's upload instruction for a local file, use `import_asset` for a public URL, or reuse an asset from `list_assets`. Look at each image with `view_asset` before you pass it.
7. Fill a brief or hook field with the brief pattern below. For a select field, pick one of its options. Do not type free text into a select.
8. Call `quote_space` with those inputs.
9. Tell the user the expected credits and the maximum the run can hold. If the quote has a warning, tell the user what it says.
10. The allowance left from `get_connection` is in millicredits. Divide it by 1000 to get credits. If the hold is more than the allowance left, give the user the settings link from `get_connection` and do not run. Offer fewer inputs, a shorter duration or another Space.
11. Ask the user to approve this quote. Wait for the user.
12. Call `run_space` with the quote and a stable idempotency key, for example `spaces-ad-grid-citrus-can-1x1-v1`. Set confirmed=true only after the user approves this quote.
13. If `show_generation` is available, call `show_generation` once with the run's oper

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

View saved version →

---
name: remix-video
description: Remix a short video clip with the Sloosh Shadow Clone Space, so a new character plays the clip with the same motion, framing and timing. Use when the user wants to remix, recreate or clone a video, a Reel or a TikTok with their own character or model and the Sloosh tools are connected.
---

# Remix a video

Use this skill to remix one short clip with the Shadow Clone Space. Shadow Clone keeps the clip's motion, camera, pacing and length, and puts the user's character in it. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

## Steps

1. Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
2. Get the clip:
    - For a local file, follow the server's upload instruction for this client.
    - For a direct HTTPS link to an .mp4 or .mov file, use `import_asset`.
    - Reuse a video from `list_assets` or `get_asset` when the user names one.
    - A link to a post page, such as an Instagram Reel, a TikTok or an X post, is not supported yet. Support for post links is coming. For now, ask the user to save the clip with the platform's own save or download option, then share the file. A YouTube link is not supported. Ask for the video file.
3. Check the clip before you quote. It must be 4 to 30 seconds long and at most 64 MiB, as an .mp4 or .mov file. Ask the user for the length if you cannot check it yourself. The quote does not check the length, and a clip over 30 seconds fails only after the run has started and held credits. Do not quote a clip until you know it is 4 to 30 seconds long. If the clip is outside the limits, tell the user how to fix it: trim it in the phone's photo app or a video editor, or export it at a lower resolution. In a coding agent that can run commands on the user's computer, offer to trim it to 30 seconds with ffmpeg. The remix comes back the same length as the clip.
4. Get the character image. Reuse an asset from `list_assets` or `get_asset`, follow the server's upload instruction for a local file, or use `import_asset` for a public HTTPS image URL. If there is no image yet, offer to make one with the `product-imagery` skill. That image has its own quote and approval. To check that an image shows the right character, call `view_asset`.
5. Call `list_spaces` with the search term `Shadow Clone`. Do not filter by output type, because that filter hides this Space. Call `get_space` on the match to confirm it. If no Shadow Clone Space is listed, tell the user it is not available in this workspace and stop.
6. Call `get_space_input_schema` for the Space. Fill the fields the schema names:
    - Put the clip in the Reference Video field, as one video.
    - Put the character image first in the Reference Images field. The schema says which roles the later images take, such as an outfit, a product or a background. Keep that order.
    - In Select Workflows, choose Motion Transfer and only that one. Do not choose Object Transfer.
    - Add the user's notes to Additional Instructions only when they have some.
    - Leave the aspect ratio empty to match the clip. Keep the default resolution unless the user asks for another one.
7. Call `quote_space` with those inputs. If the quote has an error, tell the user why in plain words.
8. Tell the user the expected credits and the maximum the run can hold. If the hold is more than the daily allowance left, give the user the settings link from `get_connection` and do not run.
9. Wait for the user to approve.
10. Call `run_space` with the quote and a stable idempotency key, for example `remix-dance-clip-hero-character-v1`. Set confirmed=true only after the user approves this quote.
11. If `show_generation` is available, call `show_generation` once with the run's operation id. Show the Space run on its own. The card updates

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

View saved version →

---
name: sloosh-router
description: Pick the one Sloosh skill that fits a creative request when the user names no skill, and say which Sloosh pack to install when that skill is in a pack the user does not have. It reads the request, maps it to one shipped core or pack skill, checks for a ready-made Space that fits, and hands off with the inputs that skill needs. Use when the user asks Sloosh to make, plan or improve images, ads, videos, motion films, brand assets, social posts or catalogue images and it is not clear which skill applies, when the user asks what Sloosh can do or what to do with a photo, or when one request implies several outputs, such as a launch or a sale. It makes nothing itself and starts no paid work. Not when the user names a skill or asks for one clear output, such as a packshot on white (use product-imagery), an ad set (use ad-variants), one product clip (use product-video) or a named Space (use published-spaces).
---

# Sloosh router

Use this skill to choose the Sloosh skill for a request. A request goes in. One skill comes out, or a short ordered list of skills, with the inputs each one needs. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

This skill costs nothing. It never asks for a quote and never starts paid work. The chosen skill quotes its own work and asks the user for approval.

## Before you start

- If the Sloosh tools are not available (no `get_connection` tool), you can still choose a skill. Tell the user that every Sloosh skill that makes images or videos needs the core Sloosh plugin, installed and connected.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, tell the user that the paid skills will need the settings link it returns.
- If a brand kit exists (a sloosh-brand.md file, the Project's knowledge, memory or brand kit text the user pasted), note it. The chosen skill reads it.

## When to use it

- The request names an outcome, not a skill, such as "stuff for our Diwali sale" or "make our new sneaker look good everywhere".
- The user asks what Sloosh can do, or what Sloosh can do with a photo.
- The request implies several outputs, such as stills, ads and a clip.
- Two skills could fit, and the choice changes what the user gets or pays.

If the user names a skill or asks for one clear output, go straight to that skill. Do not route.

## Steps

1. Read the request. Note three things:
    - The output: a still, a set of stills, a clip, a film, copy, a plan or a brand asset.
    - The purpose: sell, launch, explain, catalogue or explore.
    - The inputs the user has: a product photo, a logo, a reference image, a reference video, a brand kit, a Shopify store or nothing.
2. Check the core skills below first. Then read `references/pack-skills.md` for the pack skills.
3. Pick the one skill whose job matches the output and the inputs the user has. Name a second skill only when the request clearly needs two different outputs. When the user is still exploring, offer a free planning skill first, such as ad-concepts (sloosh-ads) or creative-strategy (sloosh-strategy).
4. Check that the chosen skill is installed. Look at the skills you can load. A pack skill shows with its pack name, such as sloosh-ads:ad-concepts.
5. If the chosen skill is in a pack that is not installed, tell the user which pack has it and how to install it. Then offer the nearest core skill for now, and say in one line what the pack adds.
    - Claude Code: run /plugin install with the pack name and @sloosh, for example /plugin install sloosh-ads@sloosh. If the Shop-OS/sloosh-plugin marketplace is not added yet, run /plugin marketplace ad

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

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: ugc-storyboard
description: Plan a short UGC-style product video as a storyboard, then make its shots as separate Sloosh images or clips in two approved rounds. Use when the user wants to plan a UGC ad or creator-style video shot by shot, or wants a storyboard for a creator-style or handheld product video, and the Sloosh tools are connected. Not for one finished UGC ad from a single run with a creator photo (use the sloosh-ads ugc-video-ad skill if it is installed), for one product clip (use product-video) to run a Space the user names (use published-spaces), or a 15 to 60 s cinematic or commercial product film of several shots (use the sloosh-video cinematic-product-film skill if it is installed).
---

# UGC storyboard

Use this skill to plan a short UGC-style video and make its shots with Sloosh. The tool descriptions and the server's instructions decide how each tool works. If this skill differs from a tool description or a server guide, follow the server.

Tell the user what this makes: separate images and clips, one for each shot. Sloosh does not join the clips, add a voice-over or mix audio in this flow. The user puts the shots together in their own editor.

## Before you start

- If the Sloosh tools are not available (no `get_connection`, `quote_generation` or `generate` tool), tell the user to install and connect the core Sloosh plugin. Then stop.
    - Claude Code: run /plugin install sloosh@sloosh, then run /mcp and sign in.
    - Claude app: open the plugin's Connectors tab and connect Sloosh. Or add a custom connector with the URL https://mcp.sloosh.ai/mcp.
- If a brand kit exists, read it: a sloosh-brand.md file, Project knowledge, memory or pasted brand text. Use its voice and channels in the script.
- If the user gives a creator photo, ask the user to confirm that the person agreed to an AI-made video that shows their face. If the user gives a third-party image, reviews or a reference ad, ask the user to confirm they may use it. Ask before any quote. Do not use a photo of a child or of a public figure. Do not describe a person who looks like a public figure. If the user declines or cannot confirm, explain why and stop.
- If the user has a creator photo and wants one finished ad from a single run, use the sloosh-ads ugc-video-ad skill if it is installed.

## Steps

1. Call `get_connection` once in the conversation if you have not called it yet. If spending is not enabled, give the user the settings link it returns and do no paid work.
2. Find the product photo and any creator photo. For a local file, follow the server's upload instruction for this client. For a public HTTPS URL, use `import_asset`. For an image already in Sloosh, find it with `list_assets`. Look at each photo with `view_asset`.
3. Collect the brief: the main benefit in the buyer's words, the offer, the call to action, the placement and the length in seconds. Ask only for what is missing.
4. Write the script yourself in the chat, only from the brief and the product facts: a hook, three to five shots and a closing line with the call to action. Give each shot a one-line visual, an aspect ratio and its length in seconds. Follow the craft rules below. This step costs nothing.
5. Ask the user to approve or change the script before you quote anything.
6. Look for a published UGC Space first. Call `list_spaces` and search for `UGC`. If one fits the approved script, offer it and follow the `published-spaces` skill. A Space that writes text can hold many credits. The `published-spaces` skill quotes it and compares the maximum hold with the allowance in credits.
7. If no Space fits, plan each shot:
    - A still shot follows the `product-imagery` skill.
    - A moving shot follows the `product-video` skill. If its start frame is an image that does not exist yet, make that image in the first round. A clip cannot be quoted before its start frame exists.
    - Call `list_models` with mode `image_gen` for stills and `video_gen` for clips. Pick models 

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

Referenced files: 1 — file references are metadata, not package contents.