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).

Quality

89%

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

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.

An excellent procedural skill body: concise, fully actionable, and tightly sequenced with verification checkpoints for risky batch operations. The sole gap is progressive disclosure, where the detailed convention lives in an external non-bundled rules file rather than bundled references alongside the skill.

Suggestions

Bundle a trimmed copy of the relevant 'Save / Discard' and 'resource row' conventions into ./references/ so the skill is self-contained when the external .claude/rules file is unavailable.

Add a short 'References' section enumerating the external rule file paths up front so the one-level-deep navigation is explicit rather than inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and procedural: it never explains concepts Claude already knows and defers the full convention to an external rules file, with terse numbered steps and exact commands where every token earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready guidance such as precise git grep invocations, 'cd apps/sim && bun run type-check', 'bunx biome check --write <file>', and exact token swaps like 'text-[12px] -> text-caption' covering the common cases.	5 / 5
Workflow Clarity	Each of the three modes is a clearly numbered sequence with explicit validation checkpoints (Mode A step 5, Mode B step 8, Mode C step 8), including feedback loops and structural-only-change guardrails for these batch/destructive sweeps.	5 / 5
Progressive Disclosure	Well-organized into per-mode sections with clearly signaled one-level references to a shared rules doc ('read it first; this skill is the procedure'); it stops short of anchor 5 because the referenced convention file is an external dependency rather than a bundled reference inside this skill's own bundle.	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 well-crafted description that clearly states both capabilities and trigger conditions in third-person voice, with strong completeness and distinctiveness. Its only modest dimension is specificity, which lists two concrete actions but does not comprehensively enumerate all of the skill's operations.

Suggestions

Expand the 'what' clause to surface the third mode (row migration to SettingsResourceRow) so the description reflects the full capability set rather than only add and audit.

Add one or two more concrete action verbs (e.g. 'migrate list rows') to lift specificity toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain (Sim settings pages) and two concrete actions ('Add a new Sim settings page' and 'audit existing settings pages') tied to the SettingsPanel layout, but does not enumerate the broader set of concrete operations the way a 5-anchor example would.	3 / 5
Completeness	Explicitly answers both what ('Add a new Sim settings page, or audit existing settings pages for design-system compliance') and when ('Use when creating a settings tab, or when asked to check/clean up settings pages') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases such as 'creating a settings tab' and 'check/clean up settings pages' with good coverage; only minor synonyms or extensions are missing, which fits the 4 anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The niche is narrow and specific (Sim settings pages via the shared SettingsPanel layout) with distinct triggers ('settings tab', 'match the design system'), giving minimal overlap risk with unrelated skills.	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: simstudioai/sim
Path: .claude/skills/add-settings-page/SKILL.md
Commit: 804a452

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