serve-sim-placeholder-assets

Audit and update serve-sim's Device Hub-style simulator placeholder assets from local Xcode/CoreTypes resources. Use after installing a new Xcode or macOS seed, or when iPhone, iPad, Watch, or Vision placeholder previews look wrong.

Quality

84%

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

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

An exemplary lean body for a simple internal skill: efficient tokens, an executable command, an explicit review-before-proceed gate, and well-organized one-level-deep references. The only gaps are the absence of a re-validation loop after code updates and no concrete guidance for the actual update step.

Suggestions

Add a closing validation step, e.g., "After updating aliases, re-run the audit script and confirm no profiles report 'missing'" — this closes the feedback loop for the batch audit operation.

Make step 4 slightly more concrete about the update target (e.g., which alias/mapping file or test directory the audit output feeds into), even in one line, so the update step is executable without guesswork.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean with zero padding: it assumes competence, links one reference, gives one runnable command, and adds only non-obvious scope constraints ("Keep the public skills/serve-sim skill focused on end-user CLI usage"). Every token earns its place.	5 / 5
Actionability	The audit command ("node .codex/skills/serve-sim-placeholder-assets/scripts/audit-placeholder-assets.mjs --out tmp/device-placeholder-assets") is copy-paste ready and the reference link resolves to a real file. Not 5 because step 4's "Update app code/tests" provides no concrete guidance on what to change or where, deferring everything to the reference.	4 / 5
Workflow Clarity	A clear 4-step sequence with an explicit checkpoint ("Update app code/tests only after reviewing the audit output for exact, fallback, or missing mappings"). Not 5 because there is no feedback loop (e.g., re-run the audit after adding an alias to confirm the mapping is no longer missing) and no guidance on handling failures.	4 / 5
Progressive Disclosure	The body is a concise overview that clearly signals one-level-deep references: references/device-placeholder-assets.md exists and is self-contained (no further nesting), and scripts/audit-placeholder-assets.mjs matches the referenced path. Structure is appropriate for a simple skill under 50 lines.	5 / 5
	Total	18 / 20 Passed

Description

82%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 with explicit what-and-when structure and a well-scoped niche. The only weakness is that the action list stops at "audit and update" without enumerating the specific operations the skill performs.

Suggestions

Expand the action list beyond "audit and update" to the concrete operations the skill performs (e.g., verify CoreTypes icon mappings, regenerate cropped preview PNGs, update serve-sim aliases for missing models).

Add one or two natural trigger variations such as "device preview images" or "simulator placeholder icons" to broaden how users can phrase the request.

Dimension	Reasoning	Score
Specificity	"Audit and update serve-sim's Device Hub-style simulator placeholder assets from local Xcode/CoreTypes resources" names the domain and two concrete actions (audit, update), matching the anchor for 1-2 concrete actions without comprehensive coverage. Not 4 because it does not enumerate several specific actions or what updating involves.	3 / 5
Completeness	Explicitly answers what ("Audit and update serve-sim's Device Hub-style simulator placeholder assets from local Xcode/CoreTypes resources") and when ("Use after installing a new Xcode or macOS seed, or when ... placeholder previews look wrong") with concrete trigger phrases. Not 4 because the 'when' clause is explicit and specific rather than merely present.	5 / 5
Trigger Term Quality	Natural trigger phrases like "iPhone, iPad, Watch, or Vision placeholder previews look wrong" and "installing a new Xcode or macOS seed" are phrases a user would actually say. Not 5 because common variations (e.g., "device preview images", "simulator icons") are not covered.	4 / 5
Distinctiveness Conflict Risk	"serve-sim's Device Hub-style simulator placeholder assets" defines a clear niche with distinct triggers (Xcode/macOS seed installs, device placeholder previews); conflict risk with other skills is minimal.	5 / 5
	Total	17 / 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: EvanBacon/serve-sim
Path: .codex/skills/serve-sim-placeholder-assets/SKILL.md
Commit: 1930e6c

Reviewed: 5 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.