Name: testland/godot-gut-tests
Rating: 74.4 (1 reviews)
Author: testland

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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

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

A well-structured body with executable GDScript examples, concrete install/CI workflows, an anti-patterns guardrail table, and disciplined one-level-deep references. It assumes Claude's competence and resists padding, with only minor framing verbosity and a missing CI feedback loop keeping it from top marks.

Suggestions

Trim the Overview paragraph's Unity/Unreal framing and the 'When to use' bullets that restate the description to lift conciseness toward 5.

Add an explicit CI feedback loop (e.g. 'If JUnit failures>0, surface failing tests, fix, re-run — parse XML, not exit code') to push workflow_clarity to 5.

Consider moving the long compatibility/version detail out of the description and into a short table in the body to reduce description verbosity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient: code blocks are tight and GDScript basics (preload, extends) are assumed without explanation. Minor trim opportunities exist — e.g. the Overview paragraph re-stating Unity/Unreal context and the 'When to use' bullets partially restate the description. Not a 5 because a few framing passages could be cut without losing actionability.	4 / 5
Actionability	Copy-paste-ready executable examples for minimal tests, lifecycle hooks, inner classes, parameterised tests, doubles/stubs/spies, and async await, plus a complete headless CLI invocation with real flags. References carry the exhaustive tables, so the body covers the common cases concretely.	5 / 5
Workflow Clarity	Install is a numbered sequence with an explicit re-launch step, and CI integration is laid out as run-headless → upload-artifact → feed-reporter with the JUnit-XML-as-source-of-truth checkpoint noted in Limitations. Not a 5 because there is no explicit fail→fix→re-run feedback loop for the CI workflow.	4 / 5
Progressive Disclosure	SKILL.md is an overview that delegates the full assertion table to references/assertions.md, CLI flags and .gutconfig schema to references/cli.md, and JUnit XML shape plus the GitHub Actions workflow to references/ci.md — all one level deep, clearly signaled, and verified as real files.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 dense, concrete description that names the framework, its canonical sources, install paths, the full authoring/running feature set, and version compatibility, then closes with an explicit 'Use when' trigger. Third-person voice is maintained throughout. The only risk is verbosity, but every clause carries specific capability or trigger information.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'install (Godot Asset Library or manual addons/gut/ copy + plugin enable)', 'writing tests that extend GutTest with test_ prefix methods', 'doubles / stubs / spies', 'command-line runner (-d -s addons/gut/gut_cmdln.gd ...)', 'JUnit XML export, and CI integration' — covering the full framework surface comprehensively.	5 / 5
Completeness	Explicitly answers 'what' (author and run GUT; enumerated coverage areas) and 'when' via a concrete 'Use when the unit under test is GDScript code in a Godot project' trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms and synonyms users say — 'GUT (Godot Unit Test)', 'GDScript test framework', 'unit under test is GDScript code in a Godot project' — with keyword coverage (godot, gut, gdscript, unit-test).	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche — GDScript unit testing inside Godot via GUT — with engine/version scoping, so it is unlikely to trigger for unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Reviewed

19 days ago

Table of Contents

Discovery Implementation Validation