菜单
Upload local image files into SpriteCook through MCP without API keys or base64 logs. Use when the user provides a local file path that should become a SpriteCook asset for generation references, style guides, tilesets, animation, background removal, presets, or asset organization.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Animation guide for SpriteCook. Use with spritecook-workflow-essentials when importing source images, writing stronger motion prompts, and animating existing assets.
Still-image generation guide for SpriteCook. Use with spritecook-workflow-essentials when generating pixel art or detailed/HD assets, choosing models, and keeping style consistency with reference assets.
Tileset generation guide for SpriteCook. Use with spritecook-workflow-essentials when generating autotile tilesets through SpriteCook MCP tools, choosing tile sizes, using reference/edit/style asset IDs, and saving generated tileset asset IDs.
Shared workflow rules for SpriteCook. Use together with SpriteCook generation, animation, import, background-removal, and asset-organization workflows for credits, downloads, asset manifests, safe auth handling, and recommended defaults.
Use SpriteCook saved presets through MCP. Use when the user explicitly asks to use a preset, refers to one of their saved SpriteCook presets, asks for the same style/settings as a saved preset, or asks to save a private preset for future consistent asset generation.
Godot workflow for SpriteCook assets. Use when the user wants to turn SpriteCook spritesheet PNGs, animation assets, or character animation runs into Godot SpriteFrames resources and AnimatedSprite2D/AnimatedSprite3D animation nodes. Covers both manual spritesheet-to-Godot setup and the optional SpriteCook MCP Godot export endpoint.
| name | spritecook-upload-assets |
| description | Upload local image files into SpriteCook through MCP without API keys or base64 logs. Use when the user provides a local file path that should become a SpriteCook asset for generation references, style guides, tilesets, animation, background removal, presets, or asset organization. |
Use this skill when a local image file should become a reusable SpriteCook asset_id.
Pair it with spritecook-workflow-essentials for credential safety, manifests, and downstream asset reuse.
file_name, MIME content_type, optional size_bytes, and whether pixel should be true.create_asset_upload(file_name=..., content_type=..., pixel=..., size_bytes=...).upload_url with HTTP PUT and the returned headers.finalize_asset_upload(upload_token=...).asset_id in the next SpriteCook tool.The upload URL and token are short-lived secrets. Do not print them in user-facing prose, save them to project files, or include them in manifests.
On Windows, upload without printing bytes:
Invoke-WebRequest -Method Put -Uri $uploadUrl -InFile $path -ContentType $contentType | Out-Null
Use variables for $uploadUrl, $path, and $contentType; do not echo them if they include the upload token.
Use import_asset(image=...) only when the image is already a small data URL or base64 value that can be passed directly without logging it.
Do not use shell commands that print base64 to the terminal. If encoding is necessary, store the value in memory or a private variable and pass it directly to the MCP tool.
reference_asset_id when the uploaded asset is one specific source or context image.edit_asset_id only when the uploaded asset is the one image being directly modified.style_asset_ids on generate_game_art when uploaded assets are ambient style guides; pass up to 10 IDs.style_asset_id on generate_tileset for one tileset style guide image.asset_id on animate_game_art when the uploaded asset is the source to animate.Save the returned asset_id and a local file hash in the project manifest when the workspace is writable.