tinyworld-runtime-state

Use when adding or changing persisted user state — settings defaults, audio, camera/orbit, panel positions, feature flags, and the in-app "Save Defaults" pipeline that snapshots localStorage into tinyworld-defaults.json. Also covers the inline-script regex gotcha that has burned us twice.

Quality

81%

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

Quality

Content

75%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 dense, project-specific instruction skill with strong executable snippets, a clear defaults pipeline, and a real validation checklist. The main weaknesses are minor verbosity in narrative passages and a long single-file structure that could benefit from splitting some lore into referenced files.

Suggestions

Tighten narrative padding in the cloud-save bullets and feature-flag section (e.g. drop 'that has burned us twice' and 'has previously exposed legacy multi-gate selector boards') to recover token budget without losing the rule.

Add a short sequenced checklist with checkpoints for the account/cloud sync workflow (currently a bulleted rule list) so imports/saves-during-bootstrap have an explicit validate-and-retry loop.

Consider splitting the Audio system and Feature flags sections into referenced files (e.g. references/audio.md, references/feature-flags.md) and keeping SKILL.md as an overview, since the body is ~280 lines of inline lore.

Dimension	Reasoning	Score
Conciseness	Mostly lean and information-dense, assuming Claude's competence without explaining known concepts, but carries minor padding (e.g. "that has burned us twice", "has previously exposed legacy multi-gate selector boards") and some long narrative passages in the cloud-save and feature-flag sections that could be trimmed.	4 / 5
Actionability	Provides concrete copy-paste artifacts (exclusion regexes, the localStorage percentage-position code block, the camera JSON shape, and validation commands like `node tools/check.js`), but a fair portion of guidance is prose rules (e.g. "must be server-authoritative", "Keep PartyKit presence out of saved world JSON") without accompanying code, leaving minor gaps.	4 / 5
Workflow Clarity	The Defaults pipeline is a clear 5-step sequence and the Validation section is an explicit checkpointed checklist (clean vs. existing localStorage), but the cloud-save sync workflow is a bulleted rule list rather than a sequenced process with checkpoints, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Defaults pipeline, Panel positions, Audio system, Camera, Feature flags, etc.) with no nested references and no bundle files present, though the ~280-line monolith could plausibly split the audio/feature-flag/cloud lore into referenced files.	4 / 5
	Total	16 / 20 Passed

Description

87%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, specific description with an explicit Use-when clause covering both what and when for a well-scoped project-internal niche. It would only improve by using distinct verbs per capability and adding a few natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("settings defaults, audio, camera/orbit, panel positions, feature flags, and the in-app Save Defaults pipeline that snapshots localStorage into tinyworld-defaults.json"), but the actions are mostly one verb ("adding or changing") applied to a list of nouns rather than distinct per-item verbs, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what (adding/changing persisted user state plus the Save Defaults pipeline and the inline-script regex gotcha) and when ("Use when adding or changing persisted user state — settings defaults, audio, camera/orbit, panel positions, feature flags...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage of domain terms a tinyworld dev would naturally say ("Save Defaults", "panel positions", "feature flags", "camera/orbit", "localStorage", "tinyworld-defaults.json"), though it leans technical and is missing natural synonyms/variations that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a very specific niche (tinyworld localStorage persisted state, the Save Defaults pipeline, and the inline-script regex gotcha) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jasonkneen/tiny-world-builder
Path: .codex/skills/tinyworld-runtime-state/SKILL.md
Commit: 6a9a551

Reviewed: 3 days 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.