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.

70

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

SwiftPM for macOS

Quick Start

Use this skill when Package.swift is the primary entrypoint or when SwiftPM is the fastest path to a reproducible result.

Workflow

  1. Inspect the package.

    • Read Package.swift.
    • Identify executable, library, and test products.
  2. Build with SwiftPM.

    • Use swift build by default.
    • Use release mode only when the user explicitly needs it.
  3. Run the right product.

    • Use swift run <product> when an executable exists.
    • If multiple executables exist, explain the default choice.
  4. Test narrowly.

    • Use swift test.
    • Apply filters when a specific test target or case is known.
  5. Summarize failures.

    • Module/import resolution
    • Package graph or dependency issue
    • Linker failure
    • Runtime failure
    • Test regression

Guardrails

  • Prefer SwiftPM over Xcode when both exist and the package path is clearly simpler.
  • Do not assume an app bundle exists in a pure package workflow.
  • Explain when the package is library-only and therefore not directly runnable.

Output Expectations

Provide:

  • the package products you found
  • the command you ran
  • whether build, run, or test succeeded
  • the top blocker if not
Repository
robinebers/openusage
Last updated
First committed

Canonical home

openai/plugins
In sync

since Jul 24, 2026

Also appears in

robinebers/openusage
In sync

since Jul 27, 2026

Renamed to: macos-swiftpm

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.