lua-binding-reference

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

Quality

73%

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

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

The content is highly actionable with comprehensive executable examples and good conciseness, but it functions as a monolithic single-file reference with no progressive disclosure into bundle files and no explicit validation checkpoints in its build/test workflow.

Suggestions

Split the large API/type-pattern reference into separate files under references/ (e.g. type-patterns.md, macros.md) and link them from SKILL.md as one-level-deep pointers.

Add an explicit validation step in the Build and Test section, e.g. run the format target and a Lua console smoke test, then a fix-and-retry loop on failure.

Trim redundant example variants and the trailing 'Note' line to tighten conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, using code blocks with minimal prose and assuming Claude's competence; only minor padding (e.g. the trailing 'Note' line and a few redundant example variants) could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, executable examples across macros, usertype creation, member/function registration, operators, libraries, type patterns, and build commands, covering the common cases.	5 / 5
Workflow Clarity	Sequencing is implied via 'Registration Functions' and 'File Organization', and a 'Common Issues' table exists, but there is no explicit validate->fix->retry checkpoint around the build/test flow; steps are listed without validation gates.	3 / 5
Progressive Disclosure	No bundle files exist; the entire ~460-line API reference is inlined in one SKILL.md with header-based sections but no split into separate reference files, leaving bulk content inline that could be partitioned.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and distinctive, clearly scoping a narrow technical reference, but it omits any explicit 'when to use' trigger guidance, capping completeness. Adding a 'Use when...' clause would raise the trigger and completeness scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or modifying Lua bindings for Cataclysm: Bright Nights.'

Include natural user phrases such as 'Lua bindings', 'expose C++ types to Lua', or 'Luna usertype' to broaden trigger-term coverage.

Keep the enumerated component list but pair it with the use-when phrasing so both what and when are explicit.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete components ('macros, Luna usertypes, libraries, documentation, type patterns, build steps, and common errors'), providing comprehensive coverage of the skill's scope rather than vague abstraction.	5 / 5
Completeness	The 'what' is clearly stated via the enumerated reference list, but there is no 'when' / 'Use when...' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'Lua binding', 'Luna usertypes', 'macros', and 'build steps' match what a user would say, but it lacks an explicit 'Use when...' trigger phrase and a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific ('Cataclysm-BN Lua binding') with distinct triggers and minimal risk of overlapping unrelated skills.	5 / 5
	Total	17 / 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
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: b782646

Reviewed: 23 hours 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.