CtrlK
BlogDocsLog inGet started
Tessl Logo

ios-settings-patterns

Apple-platform settings design for signalbox - which control shape fits which problem, what status text should say, and the anti-patterns this project keeps rediscovering. Use when adding or changing anything in the macOS Settings window, the iOS Settings tab, or any pane that pairs a control with live state.

68

Quality

81%

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

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 tight, opinionated, project-specific design skill that assumes competence, gives concrete decision rules with named precedents, and closes with a shipping checklist that acts as its validation loop. It is self-contained with no bundle files, so progressive disclosure is organized but cannot reach the exemplary split-file form.

Suggestions

Consider extracting the per-app precedent evidence (Spotlight/Photos/iCloud/Alfred) into a reference file so the core SKILL.md stays even leaner while preserving the detail.

Add an explicit validation feedback loop near the worked example (e.g., 'after moving progress to the surface, re-check: does Settings still show any state it cannot change?') to push workflow_clarity toward 5.

Verify the cited integration/remote-hub/scratch/*.md paths exist, or move that evidence into a bundled reference, so the 'Where the evidence lives' pointers resolve from the skill itself.

DimensionReasoningScore

Conciseness

Lean and assumes competence (no explanations of what a checkbox or iOS is); every section is load-bearing and the Apple/Mullvad/Spotlight evidence is genuinely non-obvious project knowledge. Minor re-explanation in the worked example keeps it just below the lean 5 anchor.

4 / 5

Actionability

Concrete, executable design rules with named precedents ('Six toolbar tabs maximum. General first.', 'Grouped Form sections with a footer per section', 'a checkbox plus an expensive action such as Rebuild'); absence of code is appropriate for this instruction skill and guidance is specific, sitting just below the fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The 'Before you ship a settings change' checklist provides explicit validation checkpoints (label alone carry it? counts in user's units? pane lets you change everything it shows? updated settings.html?), giving a clear sequence with most checkpoints present, just short of the full error-recovery feedback-loop 5.

4 / 5

Progressive Disclosure

Self-contained body with well-organized sections and one-level-deep, clearly signaled pointers ('Where the evidence lives' -> synthesis.md and research-*.md); no bundle files exist to split, so structure is good with minor gaps rather than the exemplary multi-file split of the 5 anchor.

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, project-scoped description that clearly states both what the skill covers and when to invoke it, with concrete triggers and low conflict risk. The only mild gap is that the 'what' lists design concerns rather than a comprehensive enumeration of discrete actions.

DimensionReasoningScore

Specificity

Names the domain ('Apple-platform settings design for signalbox') and several concrete concerns ('which control shape fits which problem, what status text should say, and the anti-patterns'), but these are areas of design guidance rather than a comprehensive list of discrete performed actions, so it sits above the 3 anchor but below the fully comprehensive 5.

4 / 5

Completeness

It explicitly answers both 'what' (settings design: control shape, status text, anti-patterns) and 'when' with a concrete 'Use when ...' trigger clause, matching the anchor that requires both with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when adding or changing anything in the macOS Settings window, the iOS Settings tab, or any pane that pairs a control with live state' clause supplies natural phrases a user would say, with good coverage but missing a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Project-specific niche ('signalbox', 'macOS Settings window', 'iOS Settings tab') with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dwmkerr/signalbox
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.