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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill app-store-deploymentOverall
score
88%
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 a well-crafted skill description that excels across all dimensions. It uses third person voice, lists specific concrete actions, includes natural trigger terms that developers would use, and has an explicit 'Use when' clause. The focus on mobile app store publishing with platform-specific mentions (iOS/Google Play) makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Publishes mobile applications', 'code signing', 'versioning', 'CI/CD automation', 'preparing app releases', 'configuring signing certificates', 'setting up automated deployment pipelines'. | 3 / 3 |
Completeness | Clearly answers both what (publishes mobile apps with code signing, versioning, CI/CD) AND when (explicit 'Use when' clause covering app releases, signing certificates, and deployment pipelines). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'iOS App Store', 'Google Play', 'app releases', 'signing certificates', 'deployment pipelines', 'CI/CD'. These are terms developers naturally use when discussing mobile app publishing. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app store publishing with distinct triggers like 'iOS App Store', 'Google Play', 'signing certificates' that are unlikely to conflict with general CI/CD or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent conciseness and concrete executable examples for both iOS and Android deployment. The main weaknesses are the lack of validation/verification steps in the deployment workflow (e.g., checking if upload succeeded, handling signing errors) and the monolithic structure that could benefit from splitting detailed CI/CD configurations into separate files.
Suggestions
Add explicit validation steps after key operations (e.g., verify archive was created, check upload response for success/failure, validate signing before upload)
Include error recovery guidance for common failures like expired certificates, rejected builds, or signing mismatches
Consider moving the full CI/CD workflow to a separate CI.md file and keeping only a summary/reference in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary commands and configurations without explaining what iOS/Android deployment is or how build systems work. Every section delivers actionable content. | 3 / 3 |
Actionability | Provides fully executable bash commands, complete YAML workflows, and copy-paste ready configurations. The xcodebuild, gradlew, and CI/CD examples are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Steps are listed in logical sequence (build → archive → export → upload), but lacks explicit validation checkpoints. No verification steps after upload, no error recovery guidance if builds fail or uploads are rejected. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The CI/CD section is quite long and could be referenced externally. No links to detailed guides for signing setup or store configuration. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.