CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-payments-apps

The Payments Apps API enables payment providers to integrate their payment solutions with Shopify's checkout.

59

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/shopify/skills/shopify-payments-apps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

The content is highly actionable with a strong, well-sequenced search-validate-retry workflow and clean one-level-deep references to real bundle files. The only weakness is moderate redundancy between the 'Required Tool Calls' section and the later 'MANDATORY' search/validate sections, plus repeated privacy notices, which slightly inflates token usage.

DimensionReasoningScore

Conciseness

The body is largely lean with concrete commands and no conceptual filler, but the 'MANDATORY: Search Before Writing Code' and 'MANDATORY: Validate Before Returning Code' sections substantially repeat the step list and flag instructions already given in 'Required Tool Calls', and the duplicate privacy notices pad the token budget, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

2 / 3

Actionability

It gives fully executable commands (scripts/search_docs.mjs "<query>", scripts/validate.mjs with --code/--model/--artifact-id/--revision flags) and a concrete example query ("paymentSessionPending mutation"), copy-paste ready, matching the 'Fully executable code/commands' anchor.

3 / 3

Workflow Clarity

A clear numbered 5-step sequence (search -> write -> validate -> fix -> return) with an explicit validate->fix->re-validate feedback loop, max-3-retry cap, and a hard checkpoint ('Return code only after validation passes') matches 'Clear sequence with explicit validation steps; feedback loops for error recovery'.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that points one level deep to real, verified bundle files (scripts/search_docs.mjs, scripts/validate.mjs, assets/payments-apps_2026-04.json.gz) with clearly signaled sections, matching 'Clear overview with well-signaled one-level-deep references'.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 clearly identifies a specific Shopify niche and one capability, but it omits the 'Use when...' trigger guidance that the rubric requires for full credit. This caps completeness and distinctiveness at 2 despite a concrete domain focus.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when writing GraphQL queries or mutations for Shopify's Payments Apps API (payment sessions, refunds, captures).'

List concrete operations the skill covers (paymentSessionConfirm, refundSessionResolve, captureSessionReject, etc.) to lift specificity to 3.

Include common user phrasings like 'payments integration', 'payment session mutation', or 'Shopify checkout GraphQL' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"integrate their payment solutions with Shopify's checkout" names the domain and a concrete action, but does not enumerate multiple specific operations (e.g. payment sessions, refunds, captures), matching the 'Names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does but provides no "Use when..." or equivalent explicit trigger guidance, which the guidelines cap at 2; the 'when' is entirely absent.

2 / 3

Trigger Term Quality

Terms like "Payments Apps API", "payment providers", and "checkout" are relevant, but common natural variations a developer would say ("payments integration", "payment session", "GraphQL mutation") are missing, fitting the 'Some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The Payments Apps API niche is fairly specific and unlikely to trigger unrelated skills, but the absence of explicit trigger phrases means it could overlap with broader Shopify skills, fitting 'Somewhat specific but could still overlap'.

2 / 3

Total

8

/

12

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.