Local Deployment

OrganizationPopular

bionic-gpt

local-deployment

Deploy one or more locally built Bionic services into the user's k3d cluster. Trigger only when the user explicitly asks for a local, k3d, or Kubernetes deployment.

Overview

Publisher	bionic-gpt
Repository	`bionic-gpt`
Skill name	`local-deployment`
Stars	2.4K
Forks	247
Bundled files	3
License	Apache-2.0
Links	Skill source Repository Homepage

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.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by bionic-gpt on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/bionic-gpt/bionic-gpt/tree/main/.agents/skills/local-deployment
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.

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/bionic-gpt/bionic-gpt.git /tmp/bionic-gpt
mkdir -p .claude/skills
cp -r /tmp/bionic-gpt/.agents/skills/local-deployment .claude/skills/local-deployment

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Local Deployment 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 Local Deployment 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 Local Deployment 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.

Local Deployment

Use this skill for an explicit request to deploy Bionic services locally or to the k3d development cluster.

Run the bundled script from the repository root:

bash
bash .agents/skills/local-deployment/deploy-to-k3d-locally.sh [service ...]

Service names match spec.services in the StackApp. Pass several names to deploy them together, for example web cli-gateway; omitting names deploys web. The script builds each local Cargo binary, imports its image into k3d-bionic, patches that service, and waits for its rollout. Web assets and the CLI gateway's Typst runtime are packaged automatically.

Web deployments enable Bionic debug logging through LOG_LEVEL and targeted Rig request and stream tracing through RIG_LOG.

Prerequisites:

Docker, k3d and kubectl are installed and available as explicit commands.
The k3d-bionic cluster exists.
kubectl is using the k3d-k3d-bionic context.
The bionic-gpt namespace and StackApp are available.

Before deployment, ensure the default kubeconfig has a reachable API server address for the current host. If the context is missing or the API server is unreachable, run the repository's local kubeconfig setup script:

bash
bash .agents/skills/k3d-environment/get-config.sh

This writes/merges the k3d-bionic kubeconfig, replaces loopback/wildcard addresses with the host gateway, and disables TLS verification for local development. It may install iproute2 using sudo apt-get; review its effects before running it on a new machine. Then run the deployment script above.

Inspect web traces after deployment with:

bash
kubectl logs deployment/bionic-gpt --namespace bionic-gpt --tail=200

Look for agent_runtime debug events, outgoing requests under rig::completions, and incoming SSE frames under rig::streaming. These settings are applied by the local deployment script only and are not added to production StackApp manifests.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Local Deployment AI skill do?

Deploy one or more locally built Bionic services into the user's k3d cluster. Trigger only when the user explicitly asks for a local, k3d, or Kubernetes deployment.

Why use Local Deployment on TypingMind?

Because you install it once and use it with any model. Local Deployment 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 Local Deployment in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bionic-gpt/bionic-gpt/tree/main/.agents/skills/local-deployment. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Local Deployment?

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 Local Deployment?

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

Is the Local Deployment AI skill free?

Yes. It is published on GitHub by bionic-gpt under the Apache-2.0 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

Qdrant

NousResearch

OrganizationPopular

Vector search engine for production RAG systems.

Tensorrt Llm

High-throughput LLM inference on NVIDIA GPUs.

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal…

Claude Opus 4 5 Migration

anthropics

OrganizationPopular

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Local Deployment

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now