CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-tinyverse-collectibles

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

Quality

66%

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

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

This is a strong guardrails-style skill: nearly every line is repo-specific, actionable, and free of padding, with explicit do-not-delete protections for archived code. Its weaknesses are structural — the release flow is spread across sections without validation checkpoints, and everything lives inline in one file with no reference split.

Suggestions

Add validation checkpoints to the release flow — e.g. verify the collectible snapshot exists in tinyworld:collectibles.v1 after a pack open before rendering it in the 'Your islands' grid, and define the retry/abort behavior when tinyverse-access returns an error.

Move the pack-audio clip mapping, hub layout spec, and fish-derivation rule into one-level-deep reference files (e.g. references/audio.md, references/hub.md) so SKILL.md stays a lean overview.

Consolidate the duplicated Raw Yield card-copy rules into one section and move the 'Release preview (tonight)' block into a dated 'current release' or 'old patterns' section so the time-sensitive details stop competing with durable guidance.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no explanations of concepts Claude already knows, but the Raw Yield card-copy rules are effectively stated twice (the card-label rules and the later 'Do not put archetype... on card-facing records' passage), and the time-sensitive "Release preview (tonight)" block is not isolated in a deprecated section — anchor 4's 'minor instances that could be trimmed', leaner than anchor 3 but short of anchor 5.

4 / 5

Actionability

Concrete guidance throughout — file paths, function names (bootCollectibleHandoffFromQuery, importToBuildCopy), the API endpoint, localStorage keys, and the runnable window.__tinyworldCollectible.enter({ id, world, profile }) snippet — with only minor gaps such as no example of handling the tinyverse-access response beyond the COMING SOON branch; it matches anchor 4 and never falls to anchor 3's pseudocode level, though a few flows (hub wiring, catalog SKU shape) are described rather than shown.

4 / 5

Workflow Clarity

The release flow (login + allowlist gate → hub → pack open → snapshot save → flip/visit) is sequenced via the 'Release preview' arrows, but it is scattered across three sections and there are no validation checkpoints — e.g. no step confirming the snapshot landed in tinyworld:collectibles.v1 before showing it in 'Your islands', and no re-check loop for the auth gate. Anchor 3 ('steps listed but validation gaps') fits: the sequence is present and readable, so it stays above anchor 2, but checkpoints are missing or implicit, capping it below 4.

3 / 5

Progressive Disclosure

The body is ~105 lines in a single file with no bundle files at all; well-headed sections exist, but content that would naturally split out — pack audio clip mappings, hub layout/rail spec, the fish derivation rule — is inlined in SKILL.md rather than moved to one-level-deep reference files. Anchor 3 ('some structure... content that should be separate is inline') is the closest match: far better organized than anchor 2's header-less wall, but lacking the signposted external references anchor 4 requires.

3 / 5

Total

14

/

20

Passed

Description

53%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 terse and unambiguous about its niche, but it reads as a project-lane label rather than a capability statement: it names features instead of actions and gives no guidance on when the skill should be invoked. Adding a 'Use when...' trigger clause and stating the skill's actual actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working on pack reveal, collectible island snapshots, or play-mode visits in the Tinyverse lane.'

Convert feature nouns into third-person actions (e.g. 'Implements pack reveal flow, immutable island snapshots, and play-mode collectible visits') to strengthen specificity.

Drop or shorten the archived-carousel clause — it is a body-level detail that dilutes the description's job of signaling when to load the skill.

DimensionReasoningScore

Specificity

"Tinyverse collectibles lane — pack reveal, frozen islands, play-mode visits" names the domain and 2-3 concrete features, but these are feature nouns rather than the actions the skill performs, matching anchor 3 rather than 4's 'several specific actions'.

3 / 5

Completeness

There is a terse 'what' (the lane and its features) but no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; the 'when' is entirely absent rather than weakly implied, keeping it from scoring 4.

3 / 5

Trigger Term Quality

Terms like "collectibles", "pack reveal", and "Tinyverse" are what a contributor would say, but coverage stops there — no synonyms or variations, and "frozen islands"/"lane" are internal jargon, fitting anchor 3's 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

"Tinyverse collectibles lane" carves a clear niche with minimal overlap risk, but the trailing "Universe carousel is archived but code stays in repo" clause blurs the boundary toward an adjacent surface, so it sits at anchor 4 rather than 5.

4 / 5

Total

13

/

20

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.

Validation — 15 / 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

Path

.codex/skills/tinyworld-tinyverse-collectibles/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.