CtrlK
BlogDocsLog inGet started
Tessl Logo

app-store-publish

Publishes AppLocker (and similar Apple apps) via repo scripts plus App Store Connect MCP: verify entitlements, sync icons, bump versions, archive/export/upload, then ASC metadata and versions through MCP tools. Use when the user wants App Store Connect publishing, resubmission after rejection, TestFlight, or updating “What’s New” / localizations.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, actionable SKILL.md body that sequences a multi-step publishing workflow with validation and defers detail to external references. The main gaps are the hedged MCP tool names and references pointing to files not bundled here.

Suggestions

Pin the exact MCP tool names (or link to a tool inventory that does) instead of hedging 'examples — exact tool names match the installed package'.

Add an explicit validate->fix->retry loop for the archive/export/upload step (e.g., what to do when 'make publish-appstore' or altool upload fails).

Ensure referenced files (reference.md, RELEASE.md, tools/app-store-connect-mcp/README.md) are actually bundled alongside the skill, or inline the small amount of detail they hold.

DimensionReasoningScore

Conciseness

Largely lean and command-driven with little padding of concepts Claude already knows; minor trimmable detail such as the note about the upstream repo being archived and the ${workspaceFolder} expansion caveat.

4 / 5

Actionability

Provides concrete, executable commands ('make verify-entitlements', 'swift test', './scripts/sync-app-icons-from-1024.sh', 'xcodegen generate --spec project.yml', 'make publish-appstore') plus named MCP tools; the MCP tool list is hedged ('examples — exact tool names match the installed package'), leaving a minor gap.

4 / 5

Workflow Clarity

Clear ordered sequence (prerequisites -> MCP setup -> repo-local checks 'Run in order' -> build/upload -> MCP tasks -> resubmission checklist) with validation checkpoints (verify-entitlements fails-on-error, swift test); not capped at 3 because validation is present, though explicit validate->fix->retry feedback loops are only weakly shown.

4 / 5

Progressive Disclosure

Body is a well-organized overview with a dedicated 'Additional detail' section signaling one-level-deep references (reference.md, RELEASE.md, tools/app-store-connect-mcp/README.md); however those referenced files are not present in the bundle, so navigation would hit dead ends.

4 / 5

Total

16

/

20

Passed

Description

92%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 strong description that uses third-person voice, states concrete capabilities, and pairs them with an explicit 'Use when' clause covering the main triggering scenarios. Slight headroom only in trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'verify entitlements, sync icons, bump versions, archive/export/upload, then ASC metadata and versions through MCP tools' — giving comprehensive coverage of the publishing workflow.

5 / 5

Completeness

Explicitly answers both what ('Publishes AppLocker ... via repo scripts plus App Store Connect MCP') and when ('Use when the user wants App Store Connect publishing, resubmission after rejection, TestFlight ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'App Store Connect publishing, resubmission after rejection, TestFlight, updating What's New / localizations' are well covered, though a few common synonyms ('submit to App Store', 'app review', 'beta testing') are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — App Store Connect publishing for AppLocker and similar Apple apps — with distinct triggers (TestFlight, resubmission, ASC) and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
Mirxa27/AppLocker
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.