agentsclimarketplace

Asset strategy

Skill SummerEngine/summer-engine-agent/skills/asset-pipeline/asset-strategy

Use when planning asset creation, picking an asset pipeline, or routing an "I need a [thing]" request to the right specialist skill. Disambiguates between 2D / 3D / audio / video / VFX / animation pipelines and dispatches via the Skill tool. Trigger on "assets", "asset pipeline", "make a model", "I need a sound", "create concept art", "generate something", broad creative requests.From its SKILL.md

Install
npx -y skills add SummerEngine/summer-engine-agent --skill asset-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

7.8 KB, as published. Nobody here has run it

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

Signal in user requestContinue at
image, art, concept, portrait, icon, sprite, texture, skybox, HUD2D table
model, mesh, 3D, prop, character, rigged, vehicle, tree, level kit3D table
sound, SFX, music, ambient, voice, VOAudio table
cutscene, trailer, loop video, animated backgroundVideo table
animation, idle, walk, attack, retarget, blend tree, IK, lipsyncAnimation table
fire, muzzle flash, smoke, lightning, shake, hit-stop, particlesVFX table

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.

AmbiguityDisambiguation question (verbatim)Routes
Concept art vs character portrait"Quick check — exploring the look (3-4 variants for art direction) or generating a final character portrait for dialogue UI?"summer:2d-assets/concept-art (exploring) / summer:2d-assets/character-portrait (final)
Prop vs character model"Static object (sword, chair, lantern) or rigged character that needs animation?"summer:3d-assets/prop-model / summer:3d-assets/character-model
Tile vs sprite sheet"One seamless tile that repeats, or a frame grid for an animated sprite?"summer:2d-assets/tileable-texture / summer:2d-assets/sprite-sheet
SFX vs music"One-shot effect or a longer track (loop, theme, ambient bed)?"summer:audio/sound-effect / summer:audio/music-track (or audio/ambient-bed)
Generate vs retarget motion"Generate a new clip on this character, or apply an existing library to a new character?"summer:animation/generate-motion / summer:animation/retarget
VFX recipe vs game-feel"Particle/shader effect in the world or screen-feel (camera shake, hit-stop)?"summer:visual-effects/recipes/<name> / summer:visual-effects/game-feel

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

RequestSkill
Concept / mood board / variantssummer:2d-assets/concept-art
Polished portrait / NPC bustsummer:2d-assets/character-portrait
Pixel sprite / retro iconsummer:2d-assets/pixel-art
HUD / button / inventory framesummer:2d-assets/ui-graphics
Wall / floor / seamless groundsummer:2d-assets/tileable-texture
Run cycle / spritesheet gridsummer:2d-assets/sprite-sheet
360 sky / panoramic backgroundsummer:2d-assets/skybox-panorama

3D assets

RequestSkill
Sword / chair / barrel / static objectsummer:3d-assets/prop-model
Player / NPC / enemy / boss / rigged humanoidsummer:3d-assets/character-model (canonical Meshy auto-rig)
Modular dungeon / building blockssummer:3d-assets/environment-kit
Car / spaceship / hard-surface vehiclesummer:3d-assets/vehicle-model
Tree / rock / mushroom / foliagesummer:3d-assets/organic-model

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

Audio

RequestSkill
Sword clash / footstep / UI clicksummer:audio/sound-effect
Theme / level music / boss tracksummer:audio/music-track
Forest ambience / cave dronesummer:audio/ambient-bed
NPC line / VO / spoken dialoguesummer:audio/voice-line
Music that reacts to combatsummer:audio/adaptive-music
What should this game sound likesummer:audio/audio-direction

Animation

RequestSkill
Idle / walk / run / attack — new clipsummer:animation/generate-motion
Apply library to a different charactersummer:animation/retarget
Blend tree / state machinesummer:animation/animation-tree
Look-at / IK / foot placementsummer:animation/procedural-animation
Lipsync / facial blendshapessummer:animation/facial-and-lipsync

Video

RequestSkill
Intro cutscene / story sequencesummer:video/cinematic-cutscene
Steam trailer / marketing clipsummer:video/trailer-shot
Animated menu background / loopsummer:video/animated-loop

Visual effects

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

RequestSkill
Fire / torch / campfiresummer:visual-effects/recipes/fire
Muzzle flash / gunshotsummer:visual-effects/recipes/muzzle-flash
Water ripple / splashsummer:visual-effects/recipes/water-ripple
Lightning / electric arcsummer:visual-effects/recipes/lightning
Dissolve / disintegratesummer:visual-effects/recipes/dissolve
Smoke / dust puffsummer:visual-effects/recipes/smoke
Hit spark / impact flashsummer:visual-effects/recipes/hit-spark
Magic glow / aurasummer:visual-effects/recipes/magic-glow
Camera shake / hit-stopsummer:visual-effects/game-feel

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 summer:debug or summer:play.
  • The asset is an existing Summer asset ID — call summer_get_asset, 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 — summer: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 a summer_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 summer:3d-assets/character-model.

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 equivalent generation via the Summer dashboard / Meshy / nano-banana web, then summer_import_from_url once MCP is back).

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.