CtrlK
BlogDocsLog inGet started
Tessl Logo

add-settings-page

Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout. Use when creating a settings tab, or when asked to check/clean up settings pages so they match the design system (consistent title, header, search, spacing).

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent procedural content: lean, fully executable, and each mode ends in explicit verification with recovery guidance. The only structural gap is that the body depends on an external rules file outside the skill bundle as its normative contract.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no concept explanations, no filler; it opens with ownership facts ('chrome ... is owned by the layout.tsx shell'), exact paths, and copy-paste grep commands. Every token carries procedure, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Fully executable throughout: exact git grep commands with scoped path globs, concrete transformations ('text-[12px] → text-caption, never a different size'), exact file paths, and runnable verify commands ('cd apps/sim && bun run type-check', 'bunx biome check --write'). Nothing is pseudocode or hand-waved.

5 / 5

Workflow Clarity

Each mode is a clearly sequenced numbered workflow ending in explicit validation (type-check, biome, page tests, and a diff read of every converted block), with error-recovery checkpoints such as grepping before removing imports and verifying gated rows have no leftover clickable affordance. The batch-sweep operations all include verification, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file procedure with a clear mode split, and the detailed convention is kept one level deep in .claude/rules/sim-settings-pages.md, referenced with named sections ('See the "Save / Discard + unsaved-changes guard" section', 'Read "The resource row" ... first'). It falls short of 5 because the authoritative rules file is not part of the skill's own bundle (no references/ directory), yet the body defers to it repeatedly as the contract.

4 / 5

Total

19

/

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, third-person voice, and natural trigger phrases. Its main weakness is coverage: it advertises two of the skill's three modes, omitting the list-row migration capability defined in the body.

Suggestions

Add a third action verb covering Mode C, e.g. '...or migrate settings list rows to the shared SettingsResourceRow primitive', so the description covers all three modes.

Include a natural synonym users might say for the audit mode, such as 'design-system compliance check', alongside 'check/clean up'.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Add a new Sim settings page", "audit existing settings pages for design-system compliance with the shared SettingsPanel layout") with concrete criteria (title, header, search, spacing), matching the '1-2 concrete actions, not comprehensive' anchor. It scores below 4 because an entire capability of the skill — migrating list rows to SettingsResourceRow (Mode C) — is omitted, which is more than a minor coverage gap.

3 / 5

Completeness

Both halves are explicit: the "what" (add a new settings page, audit existing pages for design-system compliance) and a concrete "Use when..." clause ("creating a settings tab, or when asked to check/clean up settings pages so they match the design system"). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: "settings page", "settings tab", "check/clean up settings pages", "match the design system". It falls just short of anchor 5 because a few natural variations are missing (e.g. 'migrate', 'rows', or listing-compliance phrasing).

4 / 5

Distinctiveness Conflict Risk

"Sim settings page", "settings tab", and "SettingsPanel" carve out a clear niche with distinct triggers; the description is unlikely to fire for unrelated design-system or generic settings work. Not 4, since the scope is unambiguously this app's settings pages.

5 / 5

Total

17

/

20

Passed

Validation

100%

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
simstudioai/sim
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.