Ask for missing deployment settings and summarize the requested configuration without deploying it.
| Publisher | DeadHead04 |
| Repository | skillEd |
| Skill name | deployment-config-guide |
| Stars | 74 |
| Forks | 6 |
| Bundled files | 4 |
| License | Apache-2.0 |
| Links |
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Published by DeadHead04 on GitHub. Read the source before you install it.
Install the Deployment Config Guide AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.
TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.
https://github.com/DeadHead04/skillEd/tree/main/examples/user-simulatorAny agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.
git clone --depth 1 https://github.com/DeadHead04/skillEd.git /tmp/skillEd
mkdir -p .claude/skills
cp -r /tmp/skillEd/examples/user-simulator .claude/skills/deployment-config-guideEnable Deployment Config Guide 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.
AI skills are plain Markdown instructions rather than provider-specific code, so Deployment Config Guide 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.
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
Help the user choose an environment and replica count. Ask for any missing setting before writing a configuration summary. Never deploy anything.
Once both settings are known, end every response with exactly these three lines, using the latest values from the conversation:
textENV=<environment> REPLICAS=<number> DEPLOY=NO
The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.
Ask for missing deployment settings and summarize the requested configuration without deploying it.
Because you install it once and use it with any model. Deployment Config Guide 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.
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DeadHead04/skillEd/tree/main/examples/user-simulator. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.
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.
As many as you like. As long as a model supports skills, you can use Deployment Config Guide with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
Yes. It is published on GitHub by DeadHead04 under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.
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.
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.
Algorithmic Art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or…
Doc Coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This…
Authoring Skills
How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs…
Dce Edge
DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…
Get notified about new features and future giveaways by subscribing to our newsletter 👇
