CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-godot

Agent-native CLI for Godot project management, scenes, exports, and script execution.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./godot/agent-harness/cli_anything/godot/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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.

An efficient, fully executable CLI reference with excellent conciseness and actionability. Its main weakness is workflow guidance: no validation checkpoints around scene-mutating and batch export operations, and no stated composition of steps (e.g. validate then run, check engine status first).

Suggestions

Wire validation into the workflows: after scene add-node suggest 'scene read' to verify the node landed, and before/after export build suggest checking 'export presets' output or the produced artifacts.

Add a brief recommended sequence for the highest-risk flows, e.g. 'script validate scripts/player.gd' before 'script run', and 'engine status' before any project command to confirm the binary is available.

Consider moving the full command catalog into a references/ file (one level deep, clearly signaled) and keeping SKILL.md to install, requirements, and the most common commands.

DimensionReasoningScore

Conciseness

The body is a lean command reference — e.g. "cli-anything-godot -p <project> scene create scenes/Level1.tscn --root-type Node3D" — with no concept explanations, no padding, and no over-explanation of things Claude already knows. Every section earns its tokens; the one-line intro is the only mild redundancy with the frontmatter.

5 / 5

Actionability

Every command is copy-paste ready with concrete flags, placeholders, and realistic values ("--preset 'Windows Desktop' --output build/game.exe"), covering the common case for each command group. The note that script run files "must extend SceneTree" supplies exactly the key detail needed to avoid a failure.

5 / 5

Workflow Clarity

Each command is individually unambiguous, but mutating and batch operations ("export build", "scene add-node", "project reimport") have no validation or verification steps, and "script validate" is never wired into a run workflow. The missing-validation cap for destructive/batch operations holds this at 3 rather than 4.

3 / 5

Progressive Disclosure

Sections are well-organized by command group with clear headers and no buried or nested references, and no bundle files exist to misroute. It is not 5 because the skill exceeds 50 lines with the entire command catalog inlined in SKILL.md — the under-50-line exception doesn't apply — though the catalog is compact enough that inlining is defensible.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific, well-scoped description with strong niche distinctiveness and decent trigger terms, held back by the complete absence of 'when to use this' guidance. Adding an explicit trigger clause and GDScript/file-extension terms would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when working with Godot projects (.tscn scenes, .gd scripts) or when the user mentions Godot, game exports, or running GDScript from the command line.'

Include natural synonyms users would say — "GDScript", ".tscn", "game engine", "Godot 4" — alongside "Godot" and "scenes".

Convert noun phrases into explicit actions where cheap, e.g. 'create projects and scenes, run and validate GDScript, build exports' instead of 'project management, scenes, exports, and script execution'.

DimensionReasoningScore

Specificity

"Godot project management, scenes, exports, and script execution" lists four concrete capability areas in a clearly named domain, matching the several-specific-actions anchor with minor gaps (node/resource operations and validation are unmentioned). It falls short of 5 because capabilities are noun phrases rather than explicit actions like 'creates scenes' or 'runs exports', but exceeds anchor 3's 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clear (a CLI for Godot project, scene, export, and script work), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3. It is not 2 because the 'what' half is specific and complete.

3 / 5

Trigger Term Quality

"Godot", "scenes", "exports", and "script execution" are terms a user would naturally say, giving good keyword coverage comparable to 'PDF files, forms, document extraction'. Not 5 because common synonyms and extensions users would mention — "GDScript", ".tscn", "game engine" — are missing.

4 / 5

Distinctiveness Conflict Risk

"Godot" pins a clear niche with distinct triggers, and the enumerated capabilities (scenes, exports, script execution) are engine-specific, so conflict with other skills is minimal. No broader or generic phrasing would cause it to fire for the wrong skill.

5 / 5

Total

16

/

20

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

HKUDS/CLI-Anything

Path

godot/agent-harness/cli_anything/godot/skills/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.