CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-store-review

Use when reviewing iOS or iPadOS apps for App Store submission, TestFlight readiness, rejection recovery, Resolution Center replies, Guideline 4.3 similarity, or product craft. Includes iOS 27 compatibility, SDK and deployment gates, scene lifecycle, iPhone Duo, Apple Intelligence, Foundation Models, Siri/App Intents, privacy, subscriptions, accessibility, new App Store assets, and Apple design and Human Interface Guidelines audits of native interaction, motion, gestures, materials, haptics, and iPad adaptation. Applies to Xcode, Expo, React Native, and Flutter projects, supplied rejections or metadata, and requests such as "review my app" or "will Apple approve this".

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced multi-mode skill: executable scanner/render commands, literal output gates, explicit validation loops and contingencies, and a clean one-level reference structure. It loses points for repetition across sections and for inlining policy catalogues that duplicate the reference layer's role.

Suggestions

State the Mode C contract-placement rule once (e.g., in the Mode C section or report-contract.md) and reference it from the Output gates and Mode A sections instead of repeating it three times.

Move the output-gates catalogue and severity definitions into references/report-contract.md, keeping only the mode-entry gate lines inline in SKILL.md.

DimensionReasoningScore

Conciseness

Dense, procedural, and free of concept padding Claude already knows, but the Mode C contract-placement instruction is repeated in three places (Output gates, Mode A, Mode C) and the 13-rule list plus inline gate/severity catalogues could be tightened. Between anchors 3 and 4, closer to 4.

4 / 5

Actionability

Copy-paste ready commands with flags and placeholders (scanner invocation, --compare-root, --archive, --metadata, render script), exact output templates ('Mode A: Pre-submission audit', the six-line Mode C contract, the Markdown/JSON/HTML/Verification block), and exact severity labels — covers the common cases.

5 / 5

Workflow Clarity

Clear mode-routed sequence (Discover → Establish scope → Review → mode workflows → current-policy check) with explicit validation checkpoints: read-only first pass with approval before edits, literal output-gate verification before saving, false-positive re-inspection, and explicit offline/timeout contingencies that still finish the report.

5 / 5

Progressive Disclosure

Well-signaled, verified, one-level-deep references with a mode-to-file Load table, but the body inlines the 13 non-negotiable rules, the full output-gates catalogue, severity definitions, and repeated contract templates that could largely live in the mode references — minor organization gaps per anchor 4.

4 / 5

Total

18

/

20

Passed

Description

95%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: explicit 'Use when' triggers, user-voice request phrases, and a clearly bounded App Store review niche. Its only weakness is that the second sentence enumerates included topics as a keyword list, which pads length without adding capability clarity.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions (rejection recovery, Resolution Center replies, Guideline 4.3 similarity audits, SDK/deployment gates, HIG design audits), but the middle sentence ('scene lifecycle, iPhone Duo, Apple Intelligence, Foundation Models, Siri/App Intents...') is a keyword enumeration that pads length without adding action clarity — between anchors 4 and 5.

4 / 5

Completeness

Opens with an explicit 'Use when reviewing iOS or iPadOS apps for App Store submission...' clause and closes with concrete request phrases, so both what (review/audit/recover/reply) and when are explicitly and concretely answered.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including user-voice quotes ('review my app', 'will Apple approve this'), tool names (Xcode, TestFlight, Expo, React Native, Flutter), and specific policy triggers (Resolution Center, Guideline 4.3).

5 / 5

Distinctiveness Conflict Risk

Clear niche (App Store review compliance) with distinct triggers (App Store submission, TestFlight readiness, Resolution Center, Guideline 4.3) that would not naturally fire a general code-review or design skill.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ElxMaj/app-store-review-skill

Path

SKILL.md

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.