Library / SDK
thedivergentai/GD-Agentic-Skills avatar
thedivergentai/GD-Agentic-Skills

GD-Agentic-Skills tracks its own version log in the README while the repository publishes no releases

The official "Long-Term Memory" for Godot 4.7+ AI Agents. A high-density library of 99 expert skills and 27 genre blueprints, providing audited, strictly typed GDScript patterns, automated persona orchestration (Analyst, Auditor, Builder), and production-grade game engineering.

969 stars61 forksGDScriptLGPL-3.0

At a glance

What is it?
A GDScript skill library for Godot 4.7 aimed at coding agents, with persona routing, a migration hub and a vision skill that scores what an agent can see. Its LoRA adapters are distributed through release assets on a repository that has none, and the front page leads with a star count.
Who is it for?
The routing design here is the part worth copying: version work is pushed into one migration hub, every Domain Skill keeps its notes in a separate references file, and current API bodies stay current, which is a saner arrangement than letting 90 skills each carry their own changelog. Two things deserve checking before you rely on it.
Can I use it commercially?
Yes, with conditions. LGPL-3.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
Is it still maintained?
Yes. The repository last received commits 30 days ago.
What is it written in?
Mainly GDScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • thedivergentai/GD-Agentic-Skills969 ★ · +269
Star history
Repository2026-09-132026-11-15
thedivergentai/GD-Agentic-Skills700969

269 Stars in the last 63 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

There is no GitHub release, so the README is the version log

The repository has no GitHub releases at all, and the last push is dated 2026-09-09. Version history is therefore maintained in the front page itself, under a heading that opens with v0.1.0 and then collapses v0.0.11, v0.0.10, v0.0.9, v0.0.8 and v0.0.7 into a details block further down. A separate CHANGELOG.md sits at the root as well, so there are two places where a version can be recorded and no tag that binds either one to a commit. The numbering is also uneven in a way a reader has to notice: v0.1.0 is the current entry, while the highest archived entry is v0.0.11, which means the project crossed to a new minor version without a corresponding release object anywhere. Nothing in the visible text explains how the two files are kept in step.

The LoRA adapters are documented as release assets on a repository with no releases

The Creation Station entry introduces five style families, pixel, painted, flat, cel and ink, each backed by a trained LoRA adapter, and shows the invocation as generate.py with a lora pixel argument. Those adapters are not in the tree. The entry says the models/ folder ships them as GitHub release assets and that they are gitignored in the repository, with models/README.md carrying the manifest, checksums and download instructions. The models/ directory does appear at the root, so what is versioned is the manifest and not the weights. That leaves the delivery step resting on release assets, and this repository has none, so the five style families described as the visual backbone of the art pipeline have no download attached to them in the visible text.

Two generations of persona names run through the update log

The project description names three personas, Analyst, Auditor and Builder. The v0.0.8 entry, the Director's Cut update, names a different squad: Anara, Aurelius and Builder, updated there for 4.7 scoring, never-lists and GODOT_PATH CLI overrides. The newer v0.0.10 entry returns to Analyst, Auditor and Builder, this time as the set of skills that point engine-version work at the migration hub. So a rename happened between those two entries, and both spellings remain readable in the same document. The practical consequence is narrow but real: a persona referenced by name in an agent instruction file has to match whichever era the surrounding text came from, and the older names still appear next to the newer ones without any note that they were retired.

Ninety-two skills in the log, ninety-nine skills and 27 blueprints in the description

The counts disagree by version. The v0.0.8 entry records the rename of Micro-Skills to Domain Skills and calls them 92 modular topic skills, each with a 4.7 baseline and targeted migration deltas. The project description now claims a library of 99 expert skills and 27 genre blueprints. Seven more skills and an entire blueprint category appeared after the entry that counted them, and the README does not attribute the new work to a version. What stayed stable is the shape: each skill is a directory under skills/ with a SKILL.md body, and the front page links a skills_index.json at the repository root. A generator for that index, update_skills_index.py, also sits at the root, which puts a Python entry point in a project whose primary language is GDScript.

godot-agent-vision puts a WebP budget and a scoring rubric between the agent and the screen

The vision skill is the mechanism that answers the creator's complaint that agents guess at menus and HUDs from file paths. It captures GUI elements, assets and editor viewports as budgeted WebP images, then scores what it captured against a granular production rubric described as typography-weighted, anti-slop and identity. Budgeted WebP is the detail that matters for cost, since a screen grab per iteration becomes an image per iteration in the agent's context. The host side is a cross-platform command line program for Windows, macOS and Linux, paired with a temporary editor bridge that lives under .gdskills/ in the user's project. The entry is explicit that this bridge is not an in-game Autoload, and the .gdskills/ directory is created on the user's side rather than shipped in this tree.

Version questions route to one hub instead of becoming a changelog dump

The Migration Station update adds godot-version-migration, which covers the full history from early Godot through 4.7 and splits that span into legacy eras, the official 3 to 4 move and hop-by-hop 4.x steps. The routing rule matters more than the coverage: Analyst, Auditor, Builder, the foundations skills, GDScript and TileMap all send engine-version questions to that hub, and godot-master forwards upgrades there instead of serving a changelog. Alongside that, every Domain Skill ships its own references/migration-notes.md while the SKILL.md body stays on current APIs. The result is a split between the file an agent reads to write code now and the file it reads to move a project forward, which keeps version history from spreading across dozens of skill bodies.

Every Domain Skill ends with a documentation lattice and a related-skills block

The Reference Lattice update added a fixed ending to each Domain Skill: a curated set of official documentation links under docs.godotengine.org/en/stable/, followed by a Related Skills block naming four relationships, Prerequisites, Complements, Downstream and Master. The same update put research-link comment blocks on skill scripts and phase documents, marked GDSkills research links (agents), described as non-executing and file-specific so they cost nothing at run time. One external contribution is credited: godot-monte-carlo-balancer, a source-driven Monte Carlo balance lab written in Rust with rayon, including headless Godot calibration. That is the only non-GDScript code the visible text credits, and it arrives from outside the project rather than from its own roster.

The front page opens with a popularity claim, and the root carries four agent instruction files

The first thing the README says after the badges is a milestone: 500 stars in August 2026, which the message places in roughly the top 0.4 percent of all public GitHub repositories. The same claim, with the same numbers, appears again in the v0.0.11 entry, so it is stated twice and verified nowhere in the visible text. The root layout is the more interesting part for anyone deciding how the project wants to be used. Alongside AGENT.md, CONTRIBUTING.md and CHANGELOG.md there are SOUL.md, IDENTITY.md and PARTNERS.md, three files that read as persona and relationship configuration rather than contributor documentation, next to assets/, scripts/, skills/ and a .github/ directory. The README also opens with the line A skill forgotten is a power lost, credited to a Code Architect.

Editorial conclusion

The routing design here is the part worth copying: version work is pushed into one migration hub, every Domain Skill keeps its notes in a separate references file, and current API bodies stay current, which is a saner arrangement than letting 90 skills each carry their own changelog. Two things deserve checking before you rely on it. The models/ folder is documented as a delivery point for LoRA adapters pushed as GitHub release assets, and the repository has no GitHub releases, so the style families cannot be fetched the way the tree describes. And the update log names two different persona squads, Anara and Aurelius in the older entries against Analyst and Auditor in the newer ones and in the project description. Treat the README as the release channel, since the project has no other one, and check a persona name before scripting against it.

Frequently asked questions

What does the GD-Agentic-Skills library contain?

Its project description calls it 99 expert skills and 27 genre blueprints for Godot 4.7 and later, with automated persona orchestration for Analyst, Auditor and Builder. The primary language is GDScript.

How are the five LoRA style adapters distributed?

The models/ folder ships them as GitHub release assets rather than in the tree, with a manifest, checksums and download instructions in models/README.md. The five families are pixel, painted, flat, cel and ink.

What does godot-agent-vision do for an agent?

It captures GUI elements, assets and editor viewports to budgeted WebP images, then scores what it captured against a production rubric that weights typography and checks identity and anti-slop.

Where does the vision skill put its editor bridge?

Under .gdskills/ in your project, driven by a host command line program for Windows, macOS and Linux, and the update entry states explicitly that it is not an in-game Autoload.

Which Godot version do these skills target?

Godot 4.7 and later. Each Domain Skill carries a 4.7 baseline along with targeted migration deltas, and a separate migration skill covers upgrades from early Godot through 4.7.

How are the three personas named across the project?

The project description and the migration entry name Analyst, Auditor and Builder, while an older update entry names Anara, Aurelius and Builder. Both spellings remain in the README.

Official sources

  1. Issues
  2. License: LGPL-3.0
  3. README
  4. thedivergentai/GD-Agentic-Skills on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thedivergentai-gd-agentic-skills.svg)](https://hysenlabs.com/projects/thedivergentai-gd-agentic-skills)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thedivergentai-gd-agentic-skills.svg)](https://hysenlabs.com/projects/thedivergentai-gd-agentic-skills)

Was this useful?