macos-spm-app-packaging
Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project. Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill macos-spm-app-packaging89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific niche (SwiftPM-based macOS development without Xcode), lists concrete capabilities, and provides explicit trigger conditions. The description uses proper third-person voice and includes natural keywords that developers would use when seeking this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold, build, and package SwiftPM-based macOS apps', 'from-scratch macOS app layout', 'SwiftPM targets/resources', 'custom .app bundle assembly script', 'signing/notarization/appcast steps'. These are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project') and when ('Use when you need a from-scratch macOS app layout, SwiftPM targets/resources, a custom .app bundle assembly script, or signing/notarization/appcast steps outside Xcode'). Has explicit 'Use when' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'SwiftPM', 'macOS apps', 'Xcode project', '.app bundle', 'signing', 'notarization', 'appcast'. These cover the domain well and include both technical terms developers would use and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: SwiftPM-based macOS apps specifically WITHOUT Xcode projects. The 'outside Xcode' qualifier and specific mentions of SwiftPM, .app bundle assembly, and notarization create a distinct scope that wouldn't conflict with general iOS/macOS development or Xcode-based workflows. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized and concise, effectively pointing to templates and reference files without over-explaining. However, it would benefit from inline code snippets showing key script usage patterns and explicit validation steps (e.g., 'verify the .app launches before signing'). The workflow is clear but missing feedback loops for error recovery in multi-step operations.
Suggestions
Add validation checkpoints to the workflow, e.g., 'Verify .app launches correctly before running sign-and-notarize.sh' and 'Check notarization status before publishing'
Include a minimal inline code example showing typical script invocation with expected output or success indicators
Add error recovery guidance for common failure points (signing failures, notarization rejections)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude understands SwiftPM, macOS app bundling, and shell scripting. No unnecessary explanations of basic concepts; every section provides actionable information. | 3 / 3 |
Actionability | Provides clear command references (swift build, Scripts/package_app.sh) and workflow steps, but lacks executable code examples. The instructions reference external templates without showing their key contents or usage patterns inline. | 2 / 3 |
Workflow Clarity | The two-step workflow is clearly sequenced, but lacks validation checkpoints. No explicit verification steps after packaging, signing, or notarization to confirm success before proceeding. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear template listing, and well-signaled references to packaging.md and release.md for details. Content is appropriately split between the skill file and referenced materials. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.