CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/godot-gut-tests

Author and run GUT (Godot Unit Test) - the community-canonical GDScript test framework at github.com/bitwes/Gut and gut.readthedocs.io. Covers install (Godot Asset Library or manual `addons/gut/` copy + plugin enable), GUT panel inside the editor, writing tests that extend GutTest with `test_` prefix methods, the assertion family (assert_eq / assert_almost_eq / assert_true / assert_signal_emitted), lifecycle hooks (before_each / after_each / before_all / after_all), inner classes for grouping, parameterized tests via `params=[...]`, doubles / stubs / spies, async / coroutine tests, the command-line runner (`-d -s addons/gut/gut_cmdln.gd -gdir=res://test -gjunit_xml_file=... -gexit`), JUnit XML export, and CI integration. Godot 4.x uses GUT 9.x (current main branch supports 4.6.x; godot_4_7 branch for 4.7.x); Godot 3.x uses GUT 7.x. Use when the unit under test is GDScript code in a Godot project.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable examples, clear workflows, and properly signaled one-level-deep references. The only weakness is minor verbosity around inline version-compatibility detail.

Suggestions

Move the inline version-compatibility specifics (4.6.x/4.7.x/7.4.3 branch detail) into the references/cli.md or a dedicated compatibility note so the main flow stays lean and the version info is easier to update.

Trim the repeated framework-provenance phrasing in the Overview and Limitations sections to a single concise statement, since the canonical link already establishes it.

DimensionReasoningScore

Conciseness

Mostly lean and skill-specific with no 'what is Godot' filler, but inline time-sensitive version detail (4.6.x/4.7.x/7.4.3) and some restated framework provenance could be tightened or moved to a version-compat note rather than the main flow.

2 / 3

Actionability

Provides fully executable GDScript snippets, an exact copy-paste CLI invocation with real paths (addons/gut/gut_cmdln.gd, res://src/health.gd), and a concrete anti-pattern table with specific fixes.

3 / 3

Workflow Clarity

Clear install → layout → authoring → running → parsing → CI sequence with explicit guardrails and validation cues (parse JUnit failures>0 as source of truth, mandatory --headless and -gexit).

3 / 3

Progressive Disclosure

The body is an overview that signals three one-level-deep references — references/assertions.md, references/cli.md, references/ci.md — all verified to exist as real bundle files, with no deep nesting.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific, and complete description that names concrete capabilities, includes natural trigger terms, and explicitly states when to use it. It is highly distinguishable and unlikely to conflict with sibling skills.

DimensionReasoningScore

Specificity

Lists many concrete actions — install via Asset Library or manual addons/gut copy, the GUT panel, authoring tests extending GutTest with test_ prefix, the assertion family, lifecycle hooks, doubles/stubs/spies, the exact CLI runner flags, JUnit XML export, and CI integration.

3 / 3

Completeness

Explicitly answers both what (author and run GUT, with a concrete covered-feature list) and when ('Use when the unit under test is GDScript code in a Godot project'), satisfying the explicit trigger requirement.

3 / 3

Trigger Term Quality

Strong natural terms a user would say — 'Godot Unit Test', 'GUT', 'GDScript', 'unit-test' — plus an explicit trigger phrase 'Use when the unit under test is GDScript code in a Godot project' that maps to real phrasing.

3 / 3

Distinctiveness Conflict Risk

A clear niche — GDScript unit testing inside Godot — with distinct triggers and an explicit C# exclusion, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents

DiscoveryImplementationValidation