CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-lua-binding-api

Add Cataclysm-BN Lua API bindings for global game functions, utility libraries, constants, callbacks, and domain-specific Lua namespaces.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-lua-binding-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-sequenced guide with excellent executable C++ examples, but it is overlong for a SKILL.md overview because five complete domain implementations are inlined rather than split into reference files. Consolidating duplicate examples and moving domain-specific code to a references/ directory would improve both conciseness and progressive disclosure.

Suggestions

Move the five full domain implementations (Game, Map, RNG, UI, Constants APIs) into references/ files (e.g. references/domains.md) and keep one exemplar library inline in SKILL.md.

Deduplicate repeated examples ("get_map", "spawn_monster") and remove the trivial one-line "Builder Pattern" section to tighten token usage.

Promote "Testing Your API" into an explicit final workflow step (e.g. "4. Build and verify: compile, then exercise the new functions in the Lua console") so validation is a checkpoint, not a separate section.

DimensionReasoningScore

Conciseness

The body contains no generic filler, but examples are duplicated ("get_map" appears in both the Map API section and Best Practices, "spawn_monster" in two Best Practices sections) and the one-line "Builder Pattern" section adds little, so it could be noticeably tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready C++ code with real luna/sol2 calls, exact file paths (src/catalua_bindings.h, catalua_bindings.cpp), complete registration steps, and a Lua-console testing snippet covering the common cases (functions, constants, tables, callbacks, error handling).

5 / 5

Workflow Clarity

The Step-by-Step Process clearly sequences library creation, registration in the main binding, and testing; however, validation ("Testing Your API") is a standalone section rather than an explicit checkpoint such as verifying the build compiles after registration.

4 / 5

Progressive Disclosure

Sections are well organized, but no reference bundle exists and roughly 200 lines of full domain-specific example implementations (Game, Map, RNG, UI, Constants APIs) are inlined in SKILL.md when they clearly belong in separate reference files; the References section only points at existing repo source files.

3 / 5

Total

15

/

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, distinctive description that clearly communicates its niche, but it omits any explicit "when to use" trigger guidance. Adding a "Use when..." clause would raise completeness and reinforce trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding or exposing game functions, constants, or callbacks to the Cataclysm-BN Lua API, or when creating a new Lua namespace in src/catalua_bindings_*.cpp".

Include natural trigger variations such as "expose to Lua", "Lua scripting API", or "sol2/luna bindings" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description enumerates concrete binding targets ("global game functions, utility libraries, constants, callbacks, and domain-specific Lua namespaces") but relies on a single action verb ("Add"), leaving minor gaps in coverage rather than listing multiple distinct actions.

4 / 5

Completeness

It clearly answers what the skill does ("Add Cataclysm-BN Lua API bindings for...") but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"Lua", "API bindings", and "Cataclysm-BN" are natural terms a user would say when requesting this work, but common variations like "expose to Lua", "sol2", or "Lua scripting" are missing.

4 / 5

Distinctiveness Conflict Risk

"Cataclysm-BN Lua API bindings" names a clear, highly specific niche with distinct triggers; it is unlikely to fire for unrelated skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 14 missing, 7 suspicious

Warning

Total

14

/

16

Passed

Repository

cataclysmbn/Cataclysm-BN

Path

.agents/skills/add-lua-binding-api/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.