macos-build-run-debug

Build, run, and debug macOS apps with shell-first Xcode and Swift workflows. Use when launching apps or diagnosing build, startup, or runtime failures.

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with validation checkpoints and a clean one-level reference structure. The only weakness is mild repetition of the script-flag list and GUI-staging details across multiple sections.

Suggestions

State the script flags (--debug, --logs, --telemetry, --verify) once in the Workflow step 3 and reference them from Quick Start and Preferred Commands instead of restating the full list in each section.

Consolidate the SwiftPM GUI .app-bundle staging steps so the Info.plist keys and /usr/bin/open -n launch appear in only one place (the canonical references/build-run-script.md) rather than partially duplicated in step 3.

Dimension	Reasoning	Score
Conciseness	The body is dense with concrete commands and avoids explaining concepts Claude already knows, but the script-flag list (build, --debug, --logs, --telemetry, --verify) and the GUI-app staging details are restated across the Quick Start, Workflow step 3, step 4, and Preferred Commands sections, which is mild padding; not a 3 because that repetition pushes past lean, not a 1 because there is no concept-explanation fluff.	2 / 3
Actionability	Provides fully concrete, executable guidance: exact commands (git rev-parse --is-inside-work-tree, xcodebuild -list, /usr/bin/open -n, pgrep -x), exact Info.plist keys, and a canonical script reference; not a 2 because key details are complete rather than missing or pseudocode.	3 / 3
Workflow Clarity	Seven clearly sequenced steps with explicit validation (the --verify flag and pgrep -x <AppName> process check) and error-recovery feedback (step 5 classify the blocker, step 6 debug-mode loops); not a 2 because checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	SKILL.md is an overview that defers the full script contract one level deep to the real, existing references/build-run-script.md, clearly signaled in both an inline reference and a References section; not a 2 because the split is appropriate and navigation is easy, with no deep nesting.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 is concise, third-person, and clearly states both capabilities and explicit usage triggers for a well-scoped macOS niche. It hits all four dimensions at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Build, run, and debug') and names the domain plus tooling ('macOS apps with shell-first Xcode and Swift workflows'), matching the multiple-specific-actions anchor; not a 2 because the action set and tools are comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers both what ('Build, run, and debug macOS apps...') and when ('Use when launching apps or diagnosing build, startup, or runtime failures.') with an explicit trigger clause; not a 2 because the when is stated, not merely implied.	3 / 3
Trigger Term Quality	Uses natural terms users would say ('launching apps', 'diagnosing build, startup, or runtime failures') with good coverage across build/run/debug/launch/diagnose; not a 2 because it spans multiple common phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The 'macOS apps with shell-first Xcode and Swift workflows' niche is clearly scoped and unlikely to trigger for non-macOS skills; not a 2 because the macOS/Xcode/Swift framing distinguishes it from generic build/run skills.	3 / 3
	Total	12 / 12 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: robinebers/openusage
Path: .agents/skills/macos-build-run-debug/SKILL.md
Commit: 9d2bf09

Reviewed: about 13 hours 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.