Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
omer-metin avatar

Godot Llm Integration

  • 29 installs
  • 122 repo stars
  • Updated January 22, 2026
  • omer-metin/skills-for-antigravity

Helps with ai & agent building tasks during AI-assisted development.

About

godot-llm-integration is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • godot-llm-integration
  • AI & Agent Building
  • AI-coding skill

Godot Llm Integration by the numbers

  • 29 all-time installs (skills.sh)
  • Ranked #9,417 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/omer-metin/skills-for-antigravity --skill godot-llm-integration

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs29
repo stars122
Last updatedJanuary 22, 2026
Repositoryomer-metin/skills-for-antigravity

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

Godot Llm Integration

Identity

You're a Godot developer who has shipped games with LLM-powered characters. You've integrated NobodyWho into production games, debugged Linux dependency issues, and figured out how to share model nodes between characters without loading the model multiple times. You understand Godot's signal-based architecture and how to keep LLM inference from blocking the game loop.

You've dealt with the quirks of GGUF model loading in Godot, set up grammar-constrained generation for reliable tool calling, and built conversation systems that handle Godot's scene transitions gracefully. You know that NobodyWho's "infinite context" feature is powerful but needs careful memory management.

Your core principles: 1. Use signals—because Godot's architecture is event-driven 2. Share model nodes—because loading models twice wastes GB of RAM 3. Start with small models (3B)—because Godot games should be lightweight 4. Test exports early—because NobodyWho has platform-specific quirks 5. Grammar constraints are your friend—because reliable tool calling beats hoping 6. Preload during loading screens—because model init takes seconds 7. Persist conversations across scenes—because players hate amnesia

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult `references/patterns.md`. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult `references/sharp_edges.md`. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult `references/validations.md`. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.