Name: saleor
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

saleor

Saleor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Saleor data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/saleor/SKILL.md

Quality

Content

67%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 a well-structured, actionable guide to driving Saleor through the Membrane CLI, with strong state-based connection handling; its main weakness is a marketing-flavored intro and some command redundancy.

Suggestions

Cut the marketing sentences about who Saleor is 'designed for' — keep at most one neutral sentence of context, since Claude already understands e-commerce platforms.

Remove the duplicated `membrane action list` invocation in 'Popular actions' or fold it into the 'Searching for actions' section to avoid restating the same command.

Label the workflow steps consistently (e.g. '## 2. Search for actions', '## 3. Run actions') so the inline 'Step 2' references resolve to visible headers.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the marketing intro ('designed for businesses that need a highly customizable and scalable e-commerce solution') and the duplicated action-search command in 'Popular actions' add unnecessary tokens.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure, --wait polling, action list/run, and the proxy request, plus a flags table — copy-paste ready with standard placeholders.	4 / 5
Workflow Clarity	The connection flow branches on explicit states (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with polling feedback loops, though step numbering is inconsistent ('Step 2' is referenced but not labeled).	4 / 5
Progressive Disclosure	No bundle files are present and the skill is self-contained with clear section headers and no nested references; the structure is well-organized, with only minor inline bulk (the flags table) that could arguably live elsewhere.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when...' trigger and names the specific platform, but its capability list is generic and lacks the concrete e-commerce terms that would make triggers fully natural.

Suggestions

Replace generic actions with concrete Saleor verbs, e.g. 'Manage orders, products, customers, collections, and vouchers; automate checkout and fulfillment workflows.'

Expand the trigger clause with natural terms users say: 'Use when the user wants to query or update Saleor orders, products, customers, or inventory.'

Tie the 'automate workflows' claim to a concrete example so it reads as a real capability rather than marketing.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Saleor domain but the actions are generic and abstract rather than concrete (no orders, products, customers, or checkout specifics).	2 / 5
Completeness	It states both a 'what' ('Saleor integration. Manage data, records, and automate workflows.') and an explicit 'Use when the user wants to interact with Saleor data.' trigger, though the when could be more specific.	4 / 5
Trigger Term Quality	'Saleor' is a strong natural trigger term and 'interact with Saleor data' is reasonable, but common e-commerce synonyms users would say (orders, products, customers, carts) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Saleor platform gives it a clear niche with minimal conflict risk, though 'manage data, records, workflows' could overlap slightly with sibling Membrane integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/saleor/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.