Spritecook Use Presets logo

Spritecook Use Presets

Organization
SpriteCook
spritecook-use-presets

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.

Overview

PublisherSpriteCook
Repositoryskills
Skill namespritecook-use-presets
Stars
51
Forks
4
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by SpriteCook on GitHub. Read the source before you install it.

Installation

Install the Spritecook Use Presets AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/SpriteCook/skills/tree/main/skills/spritecook-use-presets
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/SpriteCook/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/spritecook-use-presets .claude/skills/spritecook-use-presets
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Spritecook Use Presets in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Spritecook Use Presets on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Spritecook Use Presets is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

SpriteCook Use Presets

Use this skill with spritecook-workflow-essentials and the relevant generation skill.

Presets are saved SpriteCook settings and prompt recipes. Their purpose is to help the user get consistent, similar output later, especially when they need a collection of related assets with the same style, model, prompt structure, dimensions, color guidance, and reference images. Users can fine-tune and save presets in the SpriteCook app, then ask an agent to use those presets through MCP.

When To Use Presets

  • Use presets when the user explicitly says use my preset, names a saved preset, or asks for assets matching a saved SpriteCook setup.
  • Use presets when the user implies continuity with a named saved style or workflow, such as use my character preset for this.
  • Do not browse presets by default for ordinary generation requests. If the user does not mention or imply a preset, use the normal SpriteCook generation workflow.
  • Use save_private_preset only when the user asks to save a preset or preserve these settings for future use.

Fetch And Apply

  1. Call list_presets(query=...) with the user's preset name or intent.
  2. Pick the best match by title first, then mode, status, description, and settings.
  3. If multiple plausible presets remain, ask a concise clarification before generating.
  4. Call get_preset_settings(preset_id=...) for the selected preset.
  5. Map returned settings into the relevant MCP tool:
    • prompt -> base prompt or prompt guidance.
    • themeText -> theme.
    • styleText -> style.
    • width, height, pixel, bgMode, aspectRatio, smartCropEnabled, smartCropMode, detailedModel, resolution, quality, and colors -> matching generation arguments when the target tool supports them.
    • settings.reference.styleAssetIds -> style_asset_ids for generate_game_art, up to 10 asset IDs.
    • settings.reference.contextAssetId -> reference_asset_id for generate_game_art.
    • settings.reference.editAssetId -> edit_asset_id for generate_game_art only when the user is modifying that specific image.
    • tilesetPerspective, tilesetPieceSet, and tilesetElevation -> generate_tileset settings.
  6. Preserve the user's requested subject or change. The preset should guide style/settings; it should not override the user's new intent unless the user asks for an exact repeat.

Reference Images

  • Private draft presets can return owned asset IDs:
    • settings.reference.styleAssetIds
    • settings.reference.contextAssetId
    • settings.reference.editAssetId
  • Published presets can return frozen preset media URLs:
    • settings.reference.styleUploadUrls
    • settings.reference.contextUploadUrl
    • settings.reference.editUploadUrl
  • Use style_asset_ids directly for settings.reference.styleAssetIds when calling generate_game_art; pass at most 10 IDs.
  • Use reference_asset_id for settings.reference.contextAssetId when the preset provides one specific visual/context reference.
  • Use edit_asset_id only for settings.reference.editAssetId, when the user is modifying that specific image.
  • Treat style asset IDs as ambient style guide images: they establish style, palette, proportions, and rendering for new related assets. The prompt does not need to restate that they are style references unless the user asks to emphasize a specific detail.
  • If a preset returns multiple style asset IDs but the target tool only accepts one, prefer the first style asset unless the user asks to choose differently.
  • If a preset returns upload URLs that the target MCP generation tool cannot consume, still use the text/model/size/color settings and mention that the media reference could not be applied through that tool.

Saving Presets

  • Use save_private_preset(...) only after the user asks to save a preset.
  • Save presets as private drafts only. Do not publish, share, or submit anything for moderation.
  • Include the settings that matter for repeatability: prompt pattern, theme, style, model, size, pixel mode, background mode, smart crop, quality, colors, and supported reference/edit/style images.
  • Use style_references, reference_image, edit_image, and preview asset IDs when the user wants the saved preset to include those images.
  • If saving fails because of the private preset limit or unavailable reference assets, explain the user-facing problem briefly and do not retry with missing references unless the user asks.

Practical Pattern

When the user says Use my character preset for a blue wizard idle sprite:

  1. list_presets(query="character")
  2. Select the likely character preset.
  3. get_preset_settings(preset_id="...")
  4. Generate with the preset's style/settings plus the new subject: blue wizard idle sprite.

Frequently asked questions

What does the Spritecook Use Presets AI skill do?

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.

Why use Spritecook Use Presets on TypingMind?

Because you install it once and use it with any model. Spritecook Use Presets is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Spritecook Use Presets in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/SpriteCook/skills/tree/main/skills/spritecook-use-presets. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Spritecook Use Presets?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Spritecook Use Presets?

As many as you like. As long as a model supports skills, you can use Spritecook Use Presets with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Spritecook Use Presets AI skill free?

Yes. It is published on GitHub by SpriteCook under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇