CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-apps

Modern Shopify app template with React Router

Quality

48%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shopify-apps/SKILL.md

The canonical home for this skill is shopify-apps in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

37%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 essentially an empty skeleton: headings and topic labels with no executable guidance, a corrupted Sharp Edges table full of placeholder 'Issue' rows, unexplained anti-patterns, and a filler 'When to Use' sentence. It reads as an auto-generated stub rather than a usable skill. It needs real pattern examples (scaffold commands, App Bridge setup code, HMAC verification snippet) and a repaired or removed table.

Suggestions

Replace topic-label patterns with concrete, executable guidance: the scaffolding command (e.g., Shopify CLI template selection), an App Bridge script-tag/embed snippet, and an HMAC webhook verification code example with immediate-response-then-process structure.

Fix the Sharp Edges table: the Issue column contains repeated 'Issue' placeholders and the Solution column leaks '## ' markdown into cells; either write real issue descriptions and clean solutions or remove the section.

Give each ❌ anti-pattern a one-line explanation of why it's wrong and what to do instead, and replace the 'When to Use' filler with actual applicability conditions (e.g., new Shopify app development, embedded admin apps, webhook endpoints).

DimensionReasoningScore

Conciseness

The body is short with no over-explanation of concepts Claude already knows — no padding around the pattern headings. Not a 5 because of wasted tokens: the 'When to Use' section is contentless filler ('This skill is applicable to execute the workflow or actions described in the overview.') and the Sharp Edges table repeats placeholder 'Issue' cells with stray '## ' markdown leaking into the solution column.

4 / 5

Actionability

The Patterns section offers only high-level hints ('Secure webhook processing with HMAC verification', 'Render app embedded in Shopify Admin') with no code, commands, or steps anywhere; the Anti-Patterns are bare ❌ headings with no explanation, and the Sharp Edges table is broken placeholders. Fits 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'. Not a 1 because the pattern lines do name concrete technologies (App Bridge, HMAC, React Router) that hint at real direction.

2 / 5

Workflow Clarity

No multi-step process is presented anywhere — no setup sequence, no validation steps, no checkpoints; the content is a list of topic labels. Matches 'Steps missing or incoherent; no sequence; no validation for risky operations', which applies even more strongly given the skill covers risky areas like webhook HMAC verification.

1 / 5

Progressive Disclosure

The skill has recognizable section structure (Patterns, Anti-Patterns, Sharp Edges, When to Use) and no external files are needed at this size, but organization is poor: the Sharp Edges table is corrupted with placeholder 'Issue' rows, Anti-Pattern sections are empty shells, and the When to Use section is meaningless. Fits 'Some structure but could be better organized'. Not lower because headers do partition content sensibly; not 4 because broken and empty sections undermine navigation.

3 / 5

Total

10

/

20

Passed

Description

36%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 a bare noun phrase naming the domain but no capabilities and no usage guidance. It fails both the 'what does this do' and 'when to use it' tests and would serve poorly as a skill trigger. It needs concrete third-person actions (e.g., 'Scaffolds Shopify apps with React Router, embeds them via App Bridge, and secures webhooks...') plus an explicit 'Use when...' clause.

Suggestions

Add concrete third-person action statements, e.g., 'Scaffolds modern Shopify apps using React Router, App Bridge embedding, and HMAC-verified webhooks. Use when building or updating a Shopify app, embedded admin app, or Shopify webhooks.'

Include natural trigger terms and synonyms users would actually say: 'Shopify app', 'embedded app', 'App Bridge', 'webhooks', 'GraphQL', 'Shopify CLI', 'shopify.app.toml'.

State when to use the skill explicitly ('Use when...') so it is distinguishable from other Shopify-related skills.

DimensionReasoningScore

Specificity

"Modern Shopify app template with React Router" names the domain (Shopify apps, React Router) but contains no actions or capabilities at all — it is a noun phrase, matching the anchor 'Names the domain but actions are minimal or generic'. Not a 1 because the domain is concrete and specific tech (Shopify, React Router), not abstract fluff; not a 3 because no concrete actions are listed.

2 / 5

Completeness

The 'what' is vague — it identifies a template but never states what the skill does — and the 'when' is entirely absent, matching 'Has a vague "what" and no "when"'. Not a 3 because anchor 3 requires a clear 'what' (e.g., 'Extract text and tables from PDF files'), and this description provides no verb or capability statement; a missing 'Use when...' clause also caps this dimension at 3.

2 / 5

Trigger Term Quality

Includes some relevant natural keywords ("Shopify", "app", "React Router", "template") a user might say, but misses the many common variations and synonyms for this domain (webhooks, embedded app, App Bridge, GraphQL, Polaris, checkout, .toml). Fits 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"Shopify" is a moderately distinct niche, but the description is so thin it would overlap with any other Shopify-related skill (e.g., a Shopify CLI, theme, or GraphQL skill). Fits 'Somewhat specific but could still overlap with similar skills'. Not a 4 because no distinct triggers or capabilities are stated that would separate it from closely related Shopify skills.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shopify-apps/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.