app-store-deployment
Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation. Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 a well-crafted skill description that clearly communicates specific capabilities (publishing to app stores, code signing, versioning, CI/CD), includes natural trigger terms developers would use, and explicitly states both what the skill does and when to use it. It occupies a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: publishing to iOS App Store and Google Play, code signing, versioning, and CI/CD automation. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation') and when ('Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'iOS App Store', 'Google Play', 'code signing', 'signing certificates', 'app releases', 'deployment pipelines', 'CI/CD'. These cover the main terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around mobile app publishing, app stores, and code signing. Unlikely to conflict with general CI/CD or web deployment skills due to the specific mobile/app store focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable deployment commands for both iOS and Android with a useful CI/CD template. Its main weaknesses are the duplication between the manual commands and CI/CD sections, the lack of validation/error-handling steps between deployment stages, and missing references to deeper topics like certificate management and ExportOptions.plist configuration.
Suggestions
Add explicit validation steps between build/archive/upload stages (e.g., verify archive exit code, check IPA exists before upload) to create feedback loops for error recovery.
Extract the CI/CD workflow into a separate referenced file to eliminate duplication with the manual commands section.
Remove the generic 'Best Practices' bullets (Claude already knows these) and replace with specific gotchas or failure modes unique to app store deployment.
Add a reference or brief section on ExportOptions.plist configuration, which is a common pain point and non-obvious requirement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with concrete commands, but the CI/CD section largely duplicates the iOS build/archive/upload commands already shown above. The 'Best Practices' section contains generic advice Claude already knows. Some tightening possible. | 2 / 3 |
Actionability | Provides fully executable commands for both iOS and Android: xcodebuild archive/export, altool upload, keytool keystore generation, gradle build, and a complete GitHub Actions workflow. Commands are copy-paste ready with clear variable placeholders. | 3 / 3 |
Workflow Clarity | Steps are presented in a logical sequence (build → archive → upload) and a pre-deployment checklist is included. However, there are no explicit validation checkpoints between steps (e.g., verify archive succeeded before exporting, verify IPA before uploading) and no error recovery/feedback loops for these potentially destructive deployment operations. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear section headers, but everything is inline in one file. The CI/CD workflow duplicates earlier content and could be referenced separately. No links to external references for topics like ExportOptions.plist configuration or signing certificate setup, which are complex enough to warrant separate files. | 2 / 3 |
Total | 9 / 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.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.