Stack logo

Stack

OrganizationPopular
bionic-gpt
stack

Create or modify StackApp infrastructure-as-code manifests and Stack-managed application infrastructure. Use for Stack components, services, profiles, database wiring, storage, authentication, ingress, secrets, or deployment configuration.

Overview

Publisherbionic-gpt
Repositorybionic-gpt
Skill namestack
Stars
2.4K
Forks
247
Bundled files
1
LicenseApache-2.0
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.

  • 1 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 Stack 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/bionic-gpt/bionic-gpt/tree/main/.agents/skills/stack
  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/bionic-gpt/bionic-gpt.git /tmp/bionic-gpt
mkdir -p .claude/skills
cp -r /tmp/bionic-gpt/.agents/skills/stack .claude/skills/stack
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Stack 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 Stack 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 Stack 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.

Stack

Use this skill for infrastructure declared with the Stack StackApp custom resource. Stack is language-neutral: configure the infrastructure here, then use the relevant application skill for framework- or language-specific code.

Workflow

  1. Inspect the existing *.stack.yaml manifests and repository deployment conventions before editing.
  2. Identify whether the change belongs in the base spec or an environment-specific profile.
  3. Prefer a Stack component or service field over adding handwritten Kubernetes resources for infrastructure Stack already manages.
  4. Preserve existing component, service, namespace, secret, and environment variable names unless the requested change requires a migration.
  5. Validate the narrowest relevant configuration before proposing a deploy.

Profiles are overlays. Keep shared configuration in the base spec and put only environment differences under spec.profiles. Do not duplicate the full base configuration in each profile.

References

  • For PostgreSQL provisioning, roles, connection secrets, service wiring, or development port exposure, read references/database.md.

Add further capability references, such as storage, authentication, ingress, and secrets, when their implementation guidance is substantial enough to load only for those tasks.

Application Boundaries

Stack owns deployed infrastructure and delivery of configuration to services. Application skills own schemas, migrations, queries, HTTP handlers, pages, and business logic. A feature may require both this skill and an application skill.

Do not put application schema design or language-specific client code in a Stack manifest merely because the application consumes a Stack-managed service.

Deployment and Safety

Treat stack init, stack deploy, kubectl apply, secret changes, and cluster configuration changes as state-changing operations. Inspect the active context, manifest, profile, namespace, and intended environment before running them. Only deploy or mutate a cluster when the user explicitly requests it.

Do not expose secret values in logs or commit generated credentials. Refer to secrets by name and use Stack's supported service wiring where available.

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 Stack AI skill do?

Create or modify StackApp infrastructure-as-code manifests and Stack-managed application infrastructure. Use for Stack components, services, profiles, database wiring, storage, authentication, ingress, secrets, or deployment configuration.

Why use Stack on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bionic-gpt/bionic-gpt/tree/main/.agents/skills/stack. 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 Stack?

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 Stack?

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

Is the Stack 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

Set up your own AI workspace now

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