version: "1.0.1" name: asset-strategy description: "Route any 'I need a [thing]' asset request to the right skill: 2D, 3D, audio, video, VFX or animation." license: MIT compatibility: [Cursor, Claude Code, Windsurf, Codex] category: asset-pipeline user-invocable: false allowed-tools: Read Grep Skill summer_assets_search summer_assets_get summer_import_asset_by_id summer_call

Asset Strategy — Meta-Router for Asset Creation

Classify the user's request, ask at most one clarifying question, then dispatch to the right specialist via the Skill tool. Don't generate anything yourself — every media-type/asset-class combination has a dedicated specialist that owns the prompt patterns, polycount targets, gates, and fallbacks. Your job is the routing decision, not the work.

Step 1 — Classify by media type

If the request spans rows ("a witch with idle and a fire spell"), classify the first asset and dispatch — the specialist hands off when it's done.

Step 2 — Disambiguate (one question max)

Ask the exact phrase before dispatching. Skipping the question is the most common routing mistake.

Step 3 — Dispatch

Invoke the specialist via the Skill tool. Don't paraphrase — let it run. Pass the user's original phrasing through.

Routing tables

2D assets

3D assets

Polycount targets (hero 8k–15k, grunt 3k–6k, mobile 1k–3k, cinematic 20k–40k) live in each specialist.

Audio

Animation

Video

Visual effects

VFX is code, not generative — recipes are shader + GDScript + node setup, not image generation.

How the specialists call Summer

The specialists name Summer's asset work by operation. A call written area.action({...}) is one operation: use the tool summer_area_action when your client lists it, else summer_call({ op: "area.action", input: {...} }). summer_search finds any operation and its exact input.

• Find and read: assets.search({ query, scope }) (scope: library (default), mine for their own, all), then assets.get({ assetId }) for the file, downloadUrl and viewerUrl. Reuse before generating.
• Generate: assets.generate_image, assets.generate_3d, assets.generate_audio, assets.generate_video, assets.generate_motion, assets.generate_sfx_choices (then assets.choices for the person's picks). They spend the person's credits; dryRun: true returns the estimate (credits, balance, enough) and makes nothing.
• Wait: 3D, video and animation answer at once with a job; jobs.wait({ jobId, timeoutSeconds: 50 }) until finished, and the finished job's result holds the asset ids.
• Save on this machine: with the local Summer MCP or the CLI, out (a folder or a file path) on a generate call, jobs.wait or assets.get saves the file there, and the answer adds localPath.
• Edit their assets: assets.remove_background, assets.slice_sheet, assets.update (title, description, tags, private or team), assets.make_public (lists one for everyone in Summer's asset store), assets.delete (deletes for good; asks the person unless they let their agent delete, and then nothing is deleted until they confirm).
• Permissions: The person decides once what their agent may do: publishing (including assets.make_public), spending and building run at once by default, and deleting for good asks. An operation whose group they have not granted answers needs_approval with a link: give the link to the person, then jobs.wait on the apr: job.
• Upload an image from disk: assets.upload_begin, then assets.upload_complete.
• One-shot makers: makers.<tool> (for example makers.npc_voice, makers.trailer_forge); summer_search lists them.

When NOT to use this skill

• The user already named the specific skill — go straight there.
• The user is debugging or running the game — route to debug or play.
• The asset is an existing Summer asset ID — call assets.get({ assetId }), then summer_import_asset_by_id.
• The asset is being imported from a non-Summer URL (.glb / .wav from Sketchfab, Quaternius, AmbientCG) — call summer_import_from_url directly.
• The user wants to plan the whole game's asset list — brainstorm-game first, then this router on each item.

Anti-patterns

• Generating yourself instead of dispatching. This file holds zero prompt patterns by design. If you're writing an assets.generate_image call from here, stop and invoke the specialist.
• Skipping the disambiguation question. Sends users to the wrong specialist and burns a paid generation. The verbatim phrasing in Step 2 is required.
• Routing concept-art to character-portrait (or the reverse). Different goals: concept-art produces 4 divergent variants for art direction; character-portrait produces 1 polished bust for dialogue UI.
• Inventing skill names. Only dispatch to skills listed above. If nothing fits, ask the user to clarify.
• Routing rigged-humanoid requests to `prop-model`. Anything that needs animation always goes to character-model.

Without Summer Engine

In a session without Summer Engine tools (the assets profile; the summer-assets skill has the whole loop), the routing tables still pick the skill. Leave out every step that imports (summer_import_asset_by_id, summer_import_from_url): deliver the file with out instead (the summer-assets skill says how).

Fallback (no MCP)

The router still works without MCP — classification is text-only. It hands off to the specialist, which surfaces its own no-MCP fallback (typically: run the same generation in the Summer dashboard, then summer_import_from_url once MCP is back).

<!-- shell-commands: generated from the operation catalog by npm run generate:registry; do not edit by hand -->

From a shell

No Summer MCP tools in this session? Run each one as a command; when summer --version is missing or below 4.0, use npx -y summer-engine@latest in place of summer. Fields are flags in kebab-case (--scene-path res://main.tscn) or one --input '<json>', and summer ops describe <op> prints the exact input. The summer-cli skill has the rest.

<!-- /shell-commands -->