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

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/build-macos-apps/skills/build-run-debug/SKILL.md

Quality

Content

71%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 well-structured, actionable macOS build/run/debug skill with a clear workflow and exemplary progressive disclosure to a single canonical reference. The main weakness is repetition of the script-flag and GUI-bundle details across multiple sections.

Suggestions

Consolidate the script-flag and GUI-bundle-staging details that are repeated across Quick Start, Workflow step 3, step 7, and Guardrails into a single canonical statement, referencing the bootstrap file for the rest.

Promote verification from an optional --verify flag into an explicit checkpoint in the default build/run flow (e.g., confirm the process exists after launch) to strengthen the feedback loop.

Trim the Guardrails bullets that restate guidance already given in the Workflow steps to reduce redundancy and token cost.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's intelligence (no basic concept explanations) but noticeably duplicates the script's flag set and GUI bundle staging details across Quick Start, Workflow step 3, step 7, and Guardrails, so it could be tightened; not a 2 because it is not padded with concept explanations.	3 / 5
Actionability	Concrete commands (git rev-parse, xcodebuild -list, swift build --show-bin-path, pgrep -x), exact script flags, and explicit Info.plist keys give mostly executable guidance; not a 5 because the full copy-paste script lives in the reference rather than inline in the body.	4 / 5
Workflow Clarity	An 8-step sequence with explicit verification (--verify via pgrep) and a failure-classification feedback loop (step 6 classify -> step 7 debug) is clear; not a 5 because verification is an opt-in flag rather than an enforced checkpoint gating the default kill-build-run path.	4 / 5
Progressive Disclosure	A clear overview body with well-signaled one-level-deep navigation to references/run-button-bootstrap.md (cited both inline at steps 3-4 and in a References section), with the canonical implementation split out and no nested references; the referenced file exists and matches the cited path.	5 / 5
	Total	16 / 20 Passed

Description

83%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, well-scoped description that clearly answers both what it does and when to use it with concrete trigger phrases. Minor room to add a few synonyms or file extensions and tighten the broad "debug" verb.

Dimension	Reasoning	Score
Specificity	"Build, run, and debug macOS apps" names three concrete actions scoped to a clear domain, matching the several-specific-actions anchor; not a 5 because "debug" is a single catch-all verb rather than multiple enumerated debug actions.	4 / 5
Completeness	It explicitly states what ("Build, run, and debug macOS apps with shell-first Xcode and Swift workflows") and when ("Use when launching apps or diagnosing build, startup, or runtime failures") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural terms like "launching apps", "build... failures", "startup", and "runtime failures" plus "Xcode"/"Swift" give good keyword coverage; not a 5 because it lacks synonyms/file extensions (e.g., .xcodeproj, .xcworkspace, "crash", "won't launch").	4 / 5
Distinctiveness Conflict Risk	The macOS-app + Xcode/Swift shell-first niche is mostly distinct with specific triggers, but "diagnosing... failures" is broad enough to risk minor overlap with a generic debug or iOS build skill, so it sits below the minimal-conflict 5.	4 / 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: openai/plugins
Path: plugins/build-macos-apps/skills/build-run-debug/SKILL.md
Commit: 1e28582

Reviewed: 6 days 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.