CtrlK
BlogDocsLog inGet started
Tessl Logo

build-game-inventory

Build or repair game inventory, loot, equipment, tooltips, drag-and-drop, persistence, and progression systems. Use for item schemas, pickup flows, stack rules, equipment slots, atomic swaps, save migration, and no-loss regression testing.

77

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured skill body that stays lean and directive with explicit transactional validation steps and a strong regression-test checklist. The only soft spot is actionability: guidance is concrete at the design level but a sample item schema or concrete validation example would make it fully executable.

Suggestions

Add a minimal example of the typed, serializable item contract (a few lines of schema showing stable ID, stack limit, and migration version) to make the "item source of truth" concrete.

Include one concrete validation check or invariant assertion (e.g., how to verify total owned item identity is conserved after a transfer) so the no-loss regression testing guidance is directly executable.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — "Use one typed, serializable item source of truth and make every transfer atomic" — with no concept explanations Claude already knows and every token earning its place. Not 4 because there is nothing left to trim.

5 / 5

Actionability

The numbered transaction procedure ("1. Validate source ownership and destination legality... 3. Commit once or reject") and the concrete test-boundary checklist are actionable, but there is no example item schema or concrete validation harness to anchor the "typed, serializable" contract. Not 5 because guidance is design-level rather than copy-paste ready; not 3 because no key details are missing for its abstraction level.

4 / 5

Workflow Clarity

Clear sequence with explicit validation checkpoints ("Persist only after the committed state is valid", "Never remove an item before confirming a legal destination") plus a loss-boundary test checklist. Not 4 because checkpoints and the checklist are explicit, forming a validate-before-commit feedback loop.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized into four clean sections, with no external references needed and none buried — the rubric's simple-skill case where well-organized sections alone suffice. Not 4 because there are no organization gaps.

5 / 5

Total

19

/

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 strong description: third-person, concrete, and specific, with an explicit "Use for..." trigger clause naming concrete sub-tasks. It closely matches the rubric's good examples and has no vague padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities across the domain — "atomic swaps, save migration, and no-loss regression testing", "stack rules, equipment slots" — with comprehensive coverage and no vague filler. Not 4 because the capability list has no notable gaps.

5 / 5

Completeness

Explicitly answers both: what ("Build or repair game inventory, loot, equipment, tooltips, drag-and-drop, persistence, and progression systems") and when ("Use for item schemas, pickup flows, stack rules..."). Not 4 because the trigger clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Natural phrases users would actually say appear throughout ("game inventory", "loot", "drag-and-drop", "pickup", "tooltips"), with synonyms spanning the domain. Not 4 because common variations are present, and file extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche (game inventory/loot/equipment systems) with distinct, domain-specific triggers; minimal overlap risk with other skills. Not 4 because it is not broad and its triggers are narrowly scoped to this domain.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.