CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-swiftpm

Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.

69

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 swiftpm-macos in openai/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 compact, well-structured instruction skill with executable commands and clear output expectations. Its main weakness is the absence of validation checkpoints in the build-run-test workflow, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint after `swift build` (e.g., only proceed to `swift run`/`swift test` when the build succeeds) to create a build->verify->run feedback loop.

Include one or two concrete example invocations (e.g., `swift run MyExecutable --flag`) to make the run/test step copy-paste ready.

Add a narrow test-filter example (e.g., `swift test --filter MyTestCase`) so the "Apply filters" guidance is directly executable.

DimensionReasoningScore

Conciseness

The body is lean across ~50 lines with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete commands like "swift build", "swift run <product>", and "swift test" with filter guidance are executable, but there are no worked example invocations, leaving a minor gap versus the copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced, but build/run/test are batch operations with no explicit validation checkpoints (e.g., confirm build success before testing), which caps this at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the well-organized Quick Start / Workflow / Guardrails / Output Expectations sections satisfy the simple-skill exception for a top score.

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.

A concise, specific description that cleanly answers both what the skill does and when to use it, with low conflict risk. Minor keyword coverage gaps keep specificity and trigger_term_quality just short of perfect.

DimensionReasoningScore

Specificity

"Build, run, and test SwiftPM macOS packages and executables" names the domain plus three concrete actions; not quite comprehensive (no mention of profiling, packaging for distribution), so below the 5 anchor.

4 / 5

Completeness

It states the what ("Build, run, and test SwiftPM macOS packages and executables") and an explicit when ("Use when the repo is package-first or has no Xcode project") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural terms "SwiftPM", "macOS packages", "package-first", "Xcode project" map to user phrasing, but common synonyms like Package.swift or .swift are absent, so just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The SwiftPM/macOS niche and the "package-first or no Xcode project" trigger carve a clear, distinct niche with minimal overlap against Xcode-oriented 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
robinebers/openusage
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.