CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-tinyverse-collectibles

Tinyverse collectibles lane — pack reveal, frozen islands, play-mode visits. Universe carousel is archived but code stays in repo.

63

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 ./.codex/skills/tinyworld-tinyverse-collectibles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is dense, actionable, and well-sequenced with explicit auth/recompute checkpoints, scoring top marks on conciseness, actionability, and workflow clarity. Its only weakness is progressive disclosure: everything is inline in one file with no reference split.

Suggestions

Move the detailed Raw Yield card-facing stat rules and economy spec into a references/ file (e.g. ECONOMY.md) and link to it one level deep, keeping SKILL.md as an overview.

Add a short 'Quick reference' table of the key file paths and localStorage keys near the top so the most-used facts are discoverable without scanning the whole document.

DimensionReasoningScore

Conciseness

Dense, project-specific guidance with no concept explanations or padding; it assumes Claude's competence and every line states a concrete repo fact, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides an executable call (window.__tinyworldCollectible.enter({ id, world, profile })), exact file paths, function names, localStorage keys, and env vars — copy-paste-ready concrete guidance.

3 / 3

Workflow Clarity

The visit boot sequence is clearly ordered (read query + sessionStorage -> enter() after applyState -> recompute profile -> openNewWorldReveal) with explicit checkpoints (auth gate, allowlist, recompute-before-reveal) and a 'Do not' constraint list.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but at ~110 lines it is a single monolithic SKILL.md with no references/ bundle and no one-level-deep pointers; detailed card-facing/economy spec that could live in a reference file is inline.

2 / 3

Total

11

/

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 names a clear, distinctive niche and a few concrete lanes but is jargon-heavy and lacks any explicit 'Use when' trigger guidance, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when ...' trigger clause naming the user-facing situations that should activate this skill.

Replace some internal codenames ('frozen islands') with the natural terms a developer would actually say when requesting this work.

Expand the action list from a terse phrase into two or three concrete capabilities to lift specificity toward 3.

DimensionReasoningScore

Specificity

Names the domain and a few concrete lanes ('pack reveal, frozen islands, play-mode visits') but the actions are terse project jargon rather than a comprehensive list of specific actions.

2 / 3

Completeness

States what the lane covers but has no 'Use when...' clause or equivalent trigger guidance, so per the rubric 'when' is only implied and completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes identifiable domain keywords ('Tinyverse collectibles', 'pack reveal') but they are internal jargon with no common variations; not the broad natural terms users would naturally say.

2 / 3

Distinctiveness Conflict Risk

The 'Tinyverse collectibles lane' niche is highly specific and unlikely to trigger for any other skill, matching the clear-niche anchor.

3 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

15

/

16

Passed

Repository
jasonkneen/tiny-world-builder
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.