swiftpm-macos
$
npx mdskill add openai/plugins/swiftpm-macosBuild SwiftPM macOS packages without Xcode projects.
- Executes Swift build commands for package-first repositories.
- Reads Package.swift to identify executables and test targets.
- Selects the appropriate product based on available binaries.
- Reports success or specific failure reasons like linker errors.
SKILL.md
.github/skills/swiftpm-macosView on GitHub ↗
--- name: swiftpm-macos description: Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project. --- # 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
More from openai/plugins
- accessibility-and-inclusive-visualizationMake data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.
- agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.
- agent-browser-verifyAutomated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
- agents-sdkBuild AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
- ai-elementsAI Elements component library guidance — pre-built React components for AI interfaces built on shadcn/ui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.
- ai-gatewayVercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
- ai-generation-persistenceAI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation
- ai-sdkVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
- aiq-deploy|
- aiq-research|