CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/app-store-deployment/skills/app-store-deployment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, mostly actionable reference for app store deployment with good sectioning. Its main weaknesses are the lack of inline validation/feedback loops in an irreversible deploy workflow and the absence of any progressive disclosure via reference files.

Suggestions

Add explicit validation checkpoints into the deploy sequence (e.g., verify the archive/exit code before exporting, confirm the IPA exists before uploading) with a fix-and-retry loop, since publishing to a store is irreversible.

Move the lengthy GitHub Actions CI/CD workflow and gradle.properties example into reference files under references/ and link to them from the body to improve progressive disclosure.

Show the ExportOptions.plist content and the Android upload action's auth/service-account configuration so the examples are fully copy-paste executable.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable code and command blocks with only minimal prose, though the opening sentence redundantly restates the description and a few code comments could be trimmed.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands (xcodebuild, xcrun altool, keytool, gradlew, a full GitHub Actions workflow), with minor gaps such as the omitted ExportOptions.plist content, the Android upload action lacking auth configuration, and use of the deprecated altool.

4 / 5

Workflow Clarity

A deploy sequence is present (Build → Export → Upload) plus a pre-deployment checklist, but there are no inline validation checkpoints or feedback loops for an irreversible store-publishing operation, which caps this dimension at 3.

3 / 5

Progressive Disclosure

Content is organized under clear section headers and is navigable, but the ~130-line body is entirely inline with a lengthy CI/CD YAML and gradle.properties example that could reasonably be split into reference files.

4 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that clearly conveys both capability and trigger conditions with concrete, natural language. It is specific and distinct, with only minor gaps in trigger synonyms and coverage edge cases.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("code signing, versioning, and CI/CD automation" plus publishing to iOS App Store and Google Play), but leaves minor gaps such as store metadata, screenshots, and the review/submission process.

4 / 5

Completeness

Explicitly states what it does ("Publishes mobile applications to iOS App Store and Google Play with code signing, versioning, and CI/CD automation") and when to use it ("Use when preparing app releases, configuring signing certificates, or setting up automated deployment pipelines") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("preparing app releases", "configuring signing certificates", "automated deployment pipelines"), but misses common synonyms like "deploy/publish my app" or tool names like "fastlane".

4 / 5

Distinctiveness Conflict Risk

Has a clear niche in mobile app store publishing with distinct triggers, but carries minor overlap risk with generic CI/CD, release, or deployment skills.

4 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.