CtrlK
BlogDocsLog inGet started
Tessl Logo

island-best-practice

Conventions, architecture, and design patterns for the boring.notch macOS Dynamic Island app. Use this skill whenever working on any feature, bugfix, or refactor in boring.notch — including adding new views, managers, settings, animations, or modifying the notch layout. Also consult this when the user asks about how the project works, how to add a new module, or when you need to understand the codebase structure before making changes.

68

Quality

83%

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

The canonical home for this skill is island-best-practice in SnowingFox/macos-island

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, project-specific architecture guide with executable code, sequenced workflows, and a clean reference table pointing to real bundle files. Its only weakness is a lack of explicit validation/feedback loops in the workflows.

Suggestions

Add an explicit validation/feedback step to the Checklist for New Features (e.g., 'Build in Xcode and fix any project.pbxproj errors before committing') to strengthen workflow_clarity.

Tighten the Architecture prose by replacing the illustrative `func startMonitoring() { ... }` stub with a note that method bodies are project-specific, improving actionability.

Trim a few explanatory sentences in the State Management and Manager sections that restate what the code already conveys, to lift conciseness toward 5.

DimensionReasoningScore

Conciseness

Largely lean and focused on project-specific facts Claude would not know (BoringViewModel layers, manager singleton pattern, NotchViews routing); a few explanatory sentences could be trimmed but none restate general knowledge.

4 / 5

Actionability

Provides concrete, copy-paste-ready Swift for the manager pattern, settings keys, and conditional modifiers, plus numbered steps for adding views/settings; minor gaps like the illustrative `func startMonitoring() { ... }` body.

4 / 5

Workflow Clarity

Multi-step processes ('Adding a New Setting', 'Adding a new top-level view', 10-item 'Checklist for New Features') are clearly sequenced with a testing checkpoint (test open/closed + liquid glass), but lack explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

A clear References table maps each of six one-level-deep reference files (all verified present) to a 'When to read' condition, with module detail appropriately offloaded and the overview kept navigable.

5 / 5

Total

17

/

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.

The description clearly states what the skill covers and gives explicit, natural trigger conditions tied to a specific app niche. It is comprehensive on completeness and distinctiveness with only minor specificity/trigger-term gaps.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'adding new views, managers, settings, animations, or modifying the notch layout' — with minor gaps in coverage rather than fully enumerating every capability.

4 / 5

Completeness

Explicitly answers both what ('Conventions, architecture, and design patterns for the boring.notch macOS Dynamic Island app') and when ('Use this skill whenever working on any feature, bugfix, or refactor... Also consult this when the user asks about how the project works').

5 / 5

Trigger Term Quality

Includes natural user-facing phrases like 'feature, bugfix, or refactor', 'how the project works', 'how to add a new module', and 'codebase structure'; a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — the boring.notch macOS Dynamic Island app — with distinct triggers, making accidental activation for unrelated skills unlikely.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
SnowingFox/macos-island
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.