Godot Export Builds logo

Godot Export Builds

Community
thedivergentai
godot-export-builds

Expert patterns for multi-platform exports including export templates (Windows/Linux/macOS/Android/iOS/Web), command-line exports (headless mode), platform-specific settings (codesign, notarization, Android SDK), feature flags (OS.has_feature), CI/CD pipelines (GitHub Actions), and build optimization (size reduction, debug stripping). Use for release preparation or automated deployment. Trigger keywords: export_preset, export_template, headless_export, platform_specific, feature_flag, CI_CD, build_optimization, codesign, Android_SDK.

Overview

Publisherthedivergentai
RepositoryGD-Agentic-Skills
Skill namegodot-export-builds
Stars
727
Forks
43
Bundled files
16
LicenseLGPL-3.0
Links
Skill sourceRepository
  • 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.

  • 16 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Godot Export Builds 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.
  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/thedivergentai/GD-Agentic-Skills.git /tmp/GD-Agentic-Skills
mkdir -p .claude/skills
cp -r /tmp/GD-Agentic-Skills/skills/godot-export-builds .claude/skills/godot-export-builds
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Godot Export Builds 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 Godot Export Builds 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 Godot Export Builds 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.

Export & Builds

Headless / CI / platform release plumbing — not Editor → Export click-path tutorials.

NEVER Do (Expert Export Rules)

Platform & Validation

  • NEVER export to production without a smoke test — Editor play ≠ Web/Mobile/Console constraints.
  • NEVER skip macOS notarization for direct distribution — Gatekeeper blocks unsigned apps (Steam/App Store distribution can substitute).
  • NEVER use ad-hoc writable res:// paths in builds — Saves/logs go to user://.

Performance & Size

  • NEVER ship Debug templates as release — Use --export-release.
  • NEVER include raw authoring junk — Filter .md / .psd / docs out of presets.
  • NEVER ignore VRAM compression on Web/Mobile — Enable ASTC/ETC2 (keep pixel art uncompressed).

Security

  • NEVER commit keystores or passwords — Env vars + export_android_signing_env.ps1.
  • NEVER leave debug cheats in release — Gate with OS.has_feature("release").
  • NEVER enable Shader Baker on dedicated server exports — Wasted build time; baker is for visual clients.

Platform Decision Tree

TargetMANDATORY scripts / actionsDo NOT Load
Desktop smoke (Win/Linux)export_headless_pipeline.ps1 or headless_build.shManual Export UI tutorials
Web smokeHeadless web preset + size reportDesktop-only compression assumptions
Android releaseexport_android_signing_env.ps1Committed keystores
macOS direct distributeexport_macos_notarize_cmd.ps1Skipping notarize "because Steam exists" when not on Steam
Dedicated serverHeadless server preset, baker offClient shader baker / UI feature packs
CI multi-platformexport_ci_github_actions.yml (Godot 4.7 images)Stale 4.2.x container pins
Steam depot uploadexport_steam_upload.ps1— if not shipping on Steam
PCK / DLC patchesexport_pck_patch_loader.gd— if no DLC
One-click all presetsexport_universal_manager.gd—
Version syncexport_version_sync.gd / version_manager.gdHardcoded version labels in UI only
Feature strippingexport_feature_flag_manager.gd—
Size auditexport_build_size_report.gd—
Custom engine stripexport_custom_build_stripper.py— unless custom builds
Post-export zip/manifestexport_post_process_hook.gd—

Editor Export UI / template download prose: use Official Documentation links in Reference — or export-setup-guide.md for INI/CLI/platform checklists.

Available Scripts

MANDATORY: Read the script that matches the platform decision above before implementing.

CI Contract (4.7)

Workflows must pull Godot 4.7 editor + export templates (not 4.2.x). Prefer the checked-in export_ci_github_actions.yml over pasted legacy YAML. Artifacts upload with actions/upload-artifact@v4.

Expert Export Patterns

1. Platform-Specific Patching (Delta Updates)

Mount external PCKs with ProjectSettings.load_resource_pack(path, true) — same-path resources override base. See export_pck_patch_loader.gd.

2. VRAM Compression Audit

  • Desktop Forward+: S3TC/BPTC
  • Mobile: ETC2 / ASTC
  • Pixel art: compression off

3. SteamPipe Upload

Build locally/CI → export_steam_upload.ps1 with STEAM_USER / STEAM_PASS / STEAMCMD_PATH env vars and an app_build.vdf.

4. Universal Build Manager

Iterate presets from export_presets.cfg via export_universal_manager.gd for one-click multi-platform consistency.

Reference

Progressive disclosure: open Official Documentation links only when researching a specific API; load Related Skills when routing to a peer domain — do not preload the whole lattice.

Official Documentation

  • Exporting (tutorial index) — Entry map for presets, templates, platform guides, feature tags, and PCK workflows before platform deep-dives.
  • Exporting projects — Export presets, template install, include/exclude filters, and release vs debug template choice.
  • Feature tags — OS.has_feature / custom tags that drive runtime stripping of debug tools and platform forks.
  • Command line tutorial — --headless, --export-release, --export-debug, and --export-pack for CI and scripted pipelines.
  • Exporting packs, patches, and mods — PCK/DLC mounting with ProjectSettings.load_resource_pack for delta updates.
  • Exporting for Android — SDK, keystore, and signing env expectations for store and CI Android builds.
  • Exporting for macOS — Codesign, notarization, and universal binary options required for Gatekeeper distribution.
  • Exporting for Web — Threading/SharedArrayBuffer, VRAM compression, and HTML5 shell constraints for web smoke tests.
  • Exporting for dedicated servers — Headless server templates and why client-only bake steps (e.g. shader baker) waste server builds.
  • EditorExportPlugin — Hook API for post-export zip/manifest steps shared across team export presets.
  • Optimizing for size — SCons module stripping and size flags when custom templates must beat stock binary weight.
  • Data paths — res:// vs user:// so exported builds do not write into read-only packed paths.

Related Skills

Prerequisites
  • godot-project-foundations — Project layout, project.godot version/icon settings, and import defaults must be sane before export presets and filters.
  • godot-gdscript-mastery — EditorScript / plugin typing and OS.execute patterns used by version sync, universal export, and post-process hooks.
Complements
  • godot-platform-desktop — Windows/Linux/macOS runtime quirks (icons, windowing, Steam) that export presets must match.
  • godot-platform-mobile — Android/iOS permission, orientation, and input assumptions that belong in mobile export options.
  • godot-platform-web — Web host constraints (CORS, threads, memory) that decide Web export type and smoke-test matrix.
  • godot-platform-console — Console certification packaging flows that extend beyond desktop/mobile export templates.
  • godot-adapt-desktop-to-mobile — Touch/UI/safe-area adaptations that must ship in mobile feature-tagged builds, not desktop-only assets.
  • godot-debugging-profiling — Profile export vs editor differences (shader compile, memory) before blaming preset filters.
  • godot-testing-patterns — Automated smoke tests against headless/CI artifacts so “runs in editor” never ships alone.
  • godot-save-load-systems — Persist under user://; export filters must not strip save schemas players need after install.
  • godot-resource-data-patterns — Resource packing and .gdignore hygiene that directly shrinks export footprint.
Downstream / consumers
Master
  • godot-master — Library router and mirrored module entry; open when discovering which Domain Skill owns a cross-cutting export or platform concern.

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 Godot Export Builds AI skill do?

Expert patterns for multi-platform exports including export templates (Windows/Linux/macOS/Android/iOS/Web), command-line exports (headless mode), platform-specific settings (codesign, notarization, Android SDK), feature flags (OS.has_feature), CI/CD pipelines (GitHub Actions), and build optimization (size reduction, debug stripping). Use for release preparation or automated deployment. Trigger keywords: export_preset, export_template, headless_export, platform_specific, feature_flag, CI_CD, build_optimization, codesign, Android_SDK.

Why use Godot Export Builds on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedivergentai/GD-Agentic-Skills/tree/main/skills/godot-export-builds. 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 Godot Export Builds?

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 Godot Export Builds?

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

Is the Godot Export Builds AI skill free?

Yes. It is published on GitHub by thedivergentai under the LGPL-3.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.

Related AI Skills

View all
obra logo

Using Git Worktrees

obra
CommunityPopular

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

25.8K
288.1K
Instructions
View
obra logo

Using Superpowers

obra
CommunityPopular

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

25.8K
288.1K
5 files
View
obra logo

Verification Before Completion

obra
CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

25.8K
288.1K
Instructions
View
obra logo

Writing Plans

obra
CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

25.8K
288.1K
1 files
View

Set up your own AI workspace now

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