CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftpm-macos

Build, run, and test pure SwiftPM-based macOS packages and executables. Use when the repo is package-first, when there is no Xcode project, or when Swift package workflows are the fastest path to diagnosis.

71

Quality

86%

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

86%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 tight, well-structured instruction-only skill with concrete commands and a clear workflow that assumes Claude's competence. The main improvement opportunity is making the test-filtering and failure-diagnosis steps concrete with actual command examples.

DimensionReasoningScore

Conciseness

The 46-line body is lean and directive throughout — no concept explanations Claude already knows, no padding; every line ("Use `swift build` by default", "Do not assume an app bundle exists") earns its place. Matches anchor 5.

5 / 5

Actionability

Mostly executable guidance with concrete commands (`swift build`, `swift run <product>`, `swift test`, read `Package.swift`), but "Apply filters when a specific test target or case is known" never shows the concrete `--filter` flag, and the failure-category list is abstract labels rather than commands. Anchor 4 (mostly executable, minor gaps), not 5.

4 / 5

Workflow Clarity

A clear 5-step sequence (inspect → build → run → test → summarize) with a failure-summary step, but there is no explicit validate→fix→retry checkpoint (e.g., "if the build fails, fix and rebuild before running"). Anchor 4 (clear sequence, minor validation gaps), not 3 since the failure-summary step provides implicit error handling.

4 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no bundle files; the body is well-organized into Quick Start, Workflow, Guardrails, and Output Expectations sections with no content that needs to be split out. Per the simple-skill guideline this merits 5.

5 / 5

Total

18

/

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 strong description: concrete third-person capabilities paired with an explicit, multi-condition 'Use when' clause that cleanly separates it from Xcode-based workflows. The only real gap is the absence of the natural file trigger 'Package.swift'.

DimensionReasoningScore

Specificity

"Build, run, and test pure SwiftPM-based macOS packages and executables" lists several concrete, third-person actions scoped to a specific domain. It falls short of anchor 5 only because it omits the failure-diagnosis capability that the skill body actually covers.

4 / 5

Completeness

Clearly answers both: what ("Build, run, and test pure SwiftPM-based macOS packages and executables") and when ("Use when the repo is package-first, when there is no Xcode project, or when Swift package workflows are the fastest path to diagnosis"). Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "SwiftPM", "macOS packages", "executables", "package-first", "no Xcode project", "Swift package" — but it misses the most natural file-level trigger users would say, like "Package.swift" or ".swift". Not anchor 5 (synonyms/extensions incomplete) nor 3 (coverage goes well beyond 'some relevant keywords').

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers; the explicit contrast with Xcode projects ("when there is no Xcode project") makes conflict with Xcode-based skills unlikely. Minimal overlap risk.

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.

Validation — 16 / 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.