lua-binding-reference

Quick reference for Cataclysm-BN Lua binding macros, Luna usertypes, libraries, documentation, type patterns, build steps, and common errors.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/lua-binding-reference/SKILL.md

Quality

Content

80%

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

The content is a dense, executable, code-first reference that is highly actionable and token-efficient. Its main weaknesses are an implicit rather than explicit validation loop in the build/registration workflow and a monolithic single-file structure with no progressive disclosure into separate reference files.

Suggestions

Add an explicit validation feedback loop in Build and Test, e.g. after building run the Lua console smoke test, and on failure consult the Common Issues table then rebuild before proceeding.

Split the large inline API reference (Luna macros, type patterns, signature examples) into one-level-deep reference files linked from a concise overview in SKILL.md to improve progressive disclosure.

Add a short "Quick start" section at the top summarizing the minimal end-to-end binding workflow before the detailed reference sections.

Dimension	Reasoning	Score
Conciseness	The body is a lean, code-first reference with terse comments and no padding or explanation of basic concepts Claude already knows; every section earns its place despite the overall length, matching the "lean and efficient" anchor.	3 / 3
Actionability	It provides extensive executable C++/Lua code and exact commands (luna::new_usertype, luna::set, the cmake build preset, sol::resolve signatures) that are copy-paste ready, matching the "fully executable code/commands" anchor.	3 / 3
Workflow Clarity	The registration flow is sequenced (declare in .h, implement in .cpp, register in reg_all_bindings) and a Common Issues table offers error recovery, but validation checkpoints are only implicit (build, then consult the table) rather than an explicit validate->fix->retry loop, fitting the "steps listed but validation gaps" anchor.	2 / 3
Progressive Disclosure	No bundle files exist, so all ~460 lines of detailed reference (macros, type patterns, full API code) live inline in SKILL.md; it is well-sectioned but content that could be split into one-level-deep reference files is inline, matching the "content that should be separate is inline" anchor.	2 / 3
	Total	10 / 12 Passed

Description

57%

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

The description is specific to a well-defined niche and unlikely to conflict with other skills, but it only states what the skill covers without any explicit "when to use it" trigger guidance. Adding a "Use when..." clause would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding or modifying Lua bindings in Cataclysm: Bright Nights, or when the user mentions Luna usertypes, binding macros, or C++/Lua integration for BN."

Frame the listed topics as concrete actions (e.g. "Register Luna usertypes, document members/functions, bind enums and IDs, build and test bindings") rather than only naming categories.

Include a couple of natural user phrasings ("Lua bindings", "expose C++ to Lua", "BN modding Lua API") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain and many specific sub-areas ("macros, Luna usertypes, libraries, documentation, type patterns, build steps, and common errors"), but these are subject categories rather than concrete actions the skill performs, so it does not reach the "multiple specific concrete actions" anchor.	2 / 3
Completeness	It clearly answers "what" (a quick reference covering the listed topics) but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant terms a user would say ("Lua binding", "Cataclysm-BN", "build steps", "common errors") but leans technical ("Luna usertypes", "binding macros") and misses common phrasings a user might naturally say, fitting the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	It targets a narrow, distinct niche (Cataclysm-BN Lua bindings, Luna usertypes) with triggers unlikely to conflict with other skills, matching the "clear niche with distinct triggers" anchor.	3 / 3
	Total	9 / 12 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
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: cataclysmbn/Cataclysm-BN
Path: .agents/skills/lua-binding-reference/SKILL.md
Commit: 584939c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.