build-and-run-macos-app

Slash command that creates or updates the project-local macOS `script/build_and_run.sh` and uses it as the default build/run entrypoint. Invoke explicitly with /build-and-run-macos-app — this skill never self-triggers.

Quality

75%

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 ./.agents/skills/build-and-run-macos-app/SKILL.md

Quality

Content

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

Concise and well-structured with good progressive disclosure, but the workflow is directional rather than executable and lacks validation checkpoints for its destructive stop/build/run operations.

Suggestions

Add an inline minimal script template or concrete xcodebuild/swift commands so the skill is actionable without requiring the external reference.

Insert an explicit validation checkpoint (e.g., verify the build succeeded before launching, and confirm the prior app process was stopped) given the kill/build/run operations.

Show the kill→build→run sequence as concrete commands in the no-flag path rather than only describing it abstractly.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned body with no concept padding; it assumes Claude's knowledge of Xcode/SwiftPM and lets every line earn its place.	5 / 5
Actionability	Workflow steps are directional ('Detect whether the repo uses...', 'Create or update...') rather than executable commands, and the concrete script shape is deferred to an external reference rather than shown inline.	3 / 5
Workflow Clarity	A clear 7-step sequence is present, but operations that stop a running app and run git init are destructive/batch-like with no explicit validation checkpoints, capping clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines with well-organized Arguments/Workflow/Guardrails sections and a single one-level-deep reference to ../build-run-debug/references/build-script.md; no nested references.	5 / 5
	Total	16 / 20 Passed

Description

78%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 tight, third-person description that clearly states what the skill does and how it is invoked, with low conflict risk. Minor gains are possible in action breadth and trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names two concrete actions — 'creates or updates the project-local macOS script/build_and_run.sh' and 'uses it as the default build/run entrypoint' — but stops short of the comprehensive multi-action coverage of a 5.	4 / 5
Completeness	Answers both what (create/update the build_and_run.sh script and use it as the entrypoint) and when ('Invoke explicitly with /build-and-run-macos-app'), but the when could state the motivating situation more concretely.	4 / 5
Trigger Term Quality	Includes the natural slash-command phrase '/build-and-run-macos-app' plus 'build/run entrypoint' and 'macOS', giving good keyword coverage, though a few synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (project-local macOS build/run script) with a distinct explicit trigger and explicitly notes it 'never self-triggers', minimizing conflict risk.	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: robinebers/openusage
Path: .agents/skills/build-and-run-macos-app/SKILL.md
Commit: 2270d5f

Reviewed: 1 day 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.