CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-apps

Modern Shopify app template with React Router

28

Quality

21%

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/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

14%Scale 1-5

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

This skill is essentially a skeleton or outline with no actual content. It lists pattern names, anti-pattern names, and a Sharp Edges table filled with placeholder text ('Issue') instead of real issues. There is zero actionable guidance—no code examples, no commands, no workflows, and no references to supporting files.

Suggestions

Add concrete, executable code examples for each pattern (React Router setup, App Bridge embedding, webhook HMAC verification) with copy-paste ready snippets.

Replace placeholder 'Issue' text in the Sharp Edges table with actual issues (e.g., 'Webhook timeout', 'Rate limiting', 'GDPR compliance') and provide concise, actionable solutions rather than bare section headers.

Add a clear multi-step workflow for at least the primary use case (e.g., setting up a new Shopify app) with validation checkpoints.

Either add supporting bundle files for detailed references (API patterns, configuration examples) and link to them, or inline the essential content with proper structure.

DimensionReasoningScore

Conciseness

The content is relatively brief and doesn't over-explain basic concepts, but the Sharp Edges table is poorly formatted with repeated 'Issue' placeholders instead of actual content, and the solutions are just section headers rather than concise answers. The 'When to Use' section is a tautological filler sentence.

3 / 5

Actionability

The skill provides no concrete code, commands, or executable guidance whatsoever. Section headers like 'React Router App Setup' and 'Webhook Handling' name patterns but contain zero implementation details, no code examples, no specific commands, and no actual instructions Claude could follow.

1 / 5

Workflow Clarity

There are no steps, no sequences, no validation checkpoints, and no workflow of any kind. The content is entirely a list of topic headings and a malformed table with placeholder text ('Issue') instead of actual issues and solutions.

1 / 5

Progressive Disclosure

There are no bundle files, no references to external files, and the content itself is just skeletal headings with no substance. The structure suggests sections that should contain detailed content or link to supporting files, but neither exists.

1 / 5

Total

6

/

20

Passed

Description

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

This description is essentially a label rather than a functional description. It names a technology stack but fails to describe any concrete actions the skill performs and completely lacks trigger guidance for when Claude should select it. It would be very difficult for Claude to reliably choose this skill from a list of alternatives.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Scaffolds a modern Shopify app using React Router, configures authentication, sets up API routes, and generates boilerplate code.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user wants to create a new Shopify app, scaffold a Shopify project, or set up a Shopify app template with React Router.'

Include synonyms and related terms users might say, such as 'boilerplate', 'starter project', 'scaffold', 'Shopify CLI', or 'Remix/React Router'.

DimensionReasoningScore

Specificity

Names the domain (Shopify app) and mentions the technology stack (React Router), but describes no concrete actions. 'Template' is vague—it doesn't say what the skill does (e.g., scaffolds, generates, configures).

2 / 5

Completeness

There is no clear 'what does this do' beyond a vague noun phrase, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing.

1 / 5

Trigger Term Quality

Includes relevant keywords like 'Shopify', 'app', 'React Router', and 'template' that users might naturally say. However, it misses synonyms and variations like 'scaffold', 'boilerplate', 'starter', 'Remix', or 'Shopify CLI'.

3 / 5

Distinctiveness Conflict Risk

The combination of 'Shopify app' and 'React Router' narrows the domain somewhat, but without specifying actions or triggers, it could overlap with other Shopify or React-related skills.

3 / 5

Total

9

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.