tinyworld-cctv-truman

Use when changing the in-world CCTV / "Truman Show" surveillance cameras in Tiny World Builder — render-to-texture security feeds, the black-and-white CRT/VHS monitor shader, camera placement (lobby side-cams, pumpkincam, treecams), subject tracking, or the lobby screen cutting to live feeds.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%

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

A tightly written, highly actionable body that assumes competence and gives concrete identifiers and validation steps. Its only weakness is progressive disclosure: everything lives inline with no external reference split.

Suggestions

Move the detailed CRT_FRAG shader mechanics and placement enumeration into a references/ file, keeping SKILL.md as an overview with one-level-deep links.

Add a short copy-paste code snippet for the minimal camera mount + tick loop so the core pattern is executable without reading the source.

Surface the ?cctv=demo QA entry point earlier (e.g. a one-line 'Quick check' near the top) so validation is discoverable before the detailed sections.

Dimension	Reasoning	Score
Conciseness	Lean and dense — every line carries specific file paths, constants, and mechanisms with no explanation of concepts Claude already knows; tokens earn their place.	3 / 3
Actionability	Provides exact files (engine/world/62-cctv-truman.js), function names (setSubjectsProvider, aim, glitch), constants (FEED_W, TRACK_LERP), and executable QA commands (?cctv=demo, npm run check).	3 / 3
Workflow Clarity	Clear sequencing for the mount/teardown lifecycle, tick wiring order, and lobby-cutting state machine, with explicit QA validation asserts (activeFeed returns feed, activity > 0).	3 / 3
Progressive Disclosure	Well-organized into clear sections but all content is inline in a single >50-line file with no bundle references; detail like the CRT shader mechanics could be split out.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 highly specific, well-triggered description that names concrete capabilities and an explicit 'Use when' clause tied to a distinct niche. Third-person imperative voice is correct and it avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'render-to-texture security feeds, the black-and-white CRT/VHS monitor shader, camera placement (lobby side-cams, pumpkincam, treecams), subject tracking' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (changing the in-world CCTV cameras) and when via a clear 'Use when changing...' trigger clause with multiple scenarios.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ('CCTV', 'Truman Show', 'surveillance cameras', 'security feeds', 'CRT/VHS monitor shader') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche ('Tiny World Builder' CCTV cameras) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: jasonkneen/tiny-world-builder
Path: .codex/skills/tinyworld-cctv-truman/SKILL.md
Commit: 039a20a

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.