CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-app-store-review

Run a pre-submission compliance check against your Shopify app's codebase. Reviews App Store requirements and surfaces likely issues before you submit for official review.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

82%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 well-structured, actionable, and token-efficient, with concrete fetch/evaluate/report instructions and a clear output template. The main gap is the absence of an explicit validation/feedback loop in the workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient and task-specific, assuming Claude's knowledge (no preamble on what Shopify or compliance is), with only minor redundancy such as restating the 'when in doubt, use ⚠️' guidance in multiple places.

4 / 5

Actionability

Provides fully concrete, executable guidance—an exact URL to fetch, precise three-status definitions with criteria, applicability-gating rules, and a detailed output template—leaving little ambiguity about what to do.

5 / 5

Workflow Clarity

A clear sequence is laid out (fetch requirements → evaluate each → gate by applicability → track skipped groups → compile report) with decision checkpoints, but it lacks an explicit validate/fix/retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections and appropriately externalizes the bulk content (the requirements list) to a single well-signaled live URL rather than inlining it; no bundle files exist to navigate.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific, well-targeted, and states both what the skill does and roughly when to use it. Its main weaknesses are the second-person voice and a trigger condition that is embedded rather than a clean 'Use when...' clause.

Suggestions

Rewrite in third person to satisfy the voice guideline (e.g., 'Runs a pre-submission compliance check against a Shopify app's codebase...'), which would recover the specificity point.

Add an explicit 'Use when...' trigger clause (e.g., 'Use when preparing to submit a Shopify app for App Store review') to lift completeness toward 5.

Include a few more natural trigger synonyms (e.g., 'app approval,' 'submission requirements') to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the Shopify App Store domain with three concrete actions ('Run a pre-submission compliance check,' 'Reviews App Store requirements,' 'surfaces likely issues'), matching the 'several specific actions' anchor at 4; reduced one level because the voice is second-person imperative ('Run... against your... codebase,' 'before you submit'), which the guidelines penalize.

3 / 5

Completeness

Clearly states what it does (compliance check, reviews requirements, surfaces issues) and supplies a when ('before you submit for official review'), but the trigger is embedded in a clause rather than a clean 'Use when...' trigger phrase.

4 / 5

Trigger Term Quality

Natural terms a developer would say are present ('Shopify app,' 'App Store,' 'submit,' 'official review,' 'compliance check'), giving good keyword coverage, but common synonyms and variations (e.g., 'approval,' 'submission requirements') are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a highly specific niche (Shopify App Store pre-submission compliance) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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
openai/plugins
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.