Saleor Skills
Five Saleor skills for an agent: apps, storefronts, store configuration as code and backend internals
- 112 ★ on the repository
- Last commit
Minimal access
Why this level
- The skills contain instructions and references and run nothing themselves
- The guidance concerns payment apps, so review the generated code before deploying
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/saleor-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills contain instructions and references and run nothing themselves
- The guidance concerns payment apps, so review the generated code before deploying
This is third-party code. Review the repository files before installing.
What it does
The skills folder in the Saleor documentation repository holds five skills maintained alongside the docs. The saleor-app skill covers the app protocol: manifest, registration, webhooks, authentication, payment apps, settings storage and Dashboard embedding. The saleor-storefront skill explains the GraphQL API data model, permissions, the checkout lifecycle, channels and product variants. The storefront-builder skill sets data contracts and storefront behavior step by step, with steps run by number. The saleor-configurator skill teaches describing store configuration in config.yml and rolling it out with the deploy, introspect and diff commands. The saleor-core skill explains backend behavior from the source: discount precedence, how an order discount is spread across lines, stock availability modes, webhook triggers and migration pitfalls. The skills come with rules and references ranked by importance: in saleor-app protocol, permissions and payments are marked critical. Installation runs npx skills add . --skill name from a repository clone. The docs build also publishes a /.well-known/agent-skills/index.json list with links to downloadable skills.
Who it is for. Developers on the Saleor platform who write apps, storefronts or store configuration with an agent.
Good fit when
- You write a Saleor app and need manifests, webhooks and permissions without protocol mistakes
- You build a storefront on Next.js, Remix or Nuxt and want shared rules for channels, variants and checkout
- You run the store as code with config.yml and the deploy, introspect and diff commands
- You investigate why a discount or voucher did not apply, or debug PRODUCT_VARIANT_*_IN_CHANNEL webhooks
Not a fit when
- The store does not run on Saleor: the rules rest on its GraphQL API and backend
- You need general product documentation: the skills cover five topics, and the rest of the docs.saleor.io site is not included
- You want a ready plugin with one-click install: the README describes installing from a clone via npx skills add
Example request
Create a Saleor payment app on Next.js: the manifest, transaction webhooks and settings in metadata, following the saleor-app skill rules.Limitations
The skills were imported from the saleor/agent-skills repository at commit fb1a572 and are maintained here from then on. Each skill needs its own installation with the --skill flag. Some rules are tied to Saleor 3.23 and newer, such as stock availability modes. GitHub metadata shows no license for the documentation repository, the skills declare an MIT license in their own files, and the original license sits in skills/LICENSE.
How to disable. Delete the skill's folder from your agent's skills directory, for example .claude/skills/saleor-app. The documentation repository does not have to be installed whole, so nothing else is left behind.
FAQ
How do I install the Saleor skills in Claude Code?
Clone saleor-docs and run npx skills add . --skill saleor-app inside it. Replace the skill name with saleor-storefront, storefront-builder, saleor-configurator or saleor-core.
Which skills are in the set?
Five: saleor-app, saleor-storefront, storefront-builder, saleor-configurator and saleor-core. A table with the purpose of each sits in skills/README.md.
How does saleor-core differ from saleor-storefront?
saleor-core describes backend logic: discounts, stock, webhooks and migrations. saleor-storefront gives rules for working with the public GraphQL API in storefronts.
Do I need to download the saleor/agent-skills repository separately?
No. The documentation says the complete original skill directories were imported here, and the former repository does not need downloading.
What does saleor-configurator do?
The skill explains how to keep store configuration in config.yml and apply it with deploy, introspect and diff, and how to pick slug or name as the identifier for each entity.
Discussion
No questions or reviews yet.
Related
SkillsWorkOS Skills: AuthKit, SSO and RBAC for agents
WorkOS Skills
Official WorkOS skills: a router and 40 references on AuthKit, SSO, Directory Sync, RBAC, Vault and moves from Auth0 and Clerk
Official Clerk skills that teach an agent to add authentication to Next.js, React, Vue, Expo, Swift and Android apps
Hundreds of per-provider skills teach an agent to receive webhooks, verify signatures and handle events, with code examples.
Scalar API Reference skill for agents
Scalar API Reference skill
A skill that adds a Scalar reference to an app from its OpenAPI description: integrations, authentication, themes, migration from Swagger UI
builder-skills: agent skills for Convex apps
builder-skills
17 skills that teach an agent to build Convex apps by the docs and run a project through a PRD, task.md and a changelog
Oracle's official set of installable skills for Oracle Database, OCI, GraalVM, Fusion and APEX
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Saleor Skills (this card) | yes | 112 | |
| Medusa Agent Skills | yes | 236 | plugins for the Medusa platform, while these are skills for Saleor |
| Shopify Admin Skills | no | 204 | skills for the Shopify Admin API; Saleor has its own data model and GraphQL API |
README in short
The main README covers the Saleor documentation: it is built with Blume and deployed on Vercel, pages sit in docs, and an update-schema script refreshes the API schema. Skills get one line there with a link to skills/README.md, which lists the five skills and the install method.
README badge
Original SKILL.md
--- name: saleor-app description: > Universal Saleor app development patterns. Covers the app protocol (manifest, registration, webhooks, authentication), payment processing, SDK abstractions, settings persistence, and Dashboard integration. Framework-agnostic with Next.js examples. license: MIT metadata: author: saleor version: "1.0.0" --- # Saleor App Guide for building apps that extend Saleor via webhooks and the GraphQL API. Framework-agnostic protocol documentation with Next.js examples using `@saleor/app-sdk`. ## When to Apply - Defining an app manifest or registering webhooks - Handling async/sync webhook events from Saleor - Building payment apps with the Transaction API and provider webhooks - Authenticating requests (registration handshake, JWT, signature verification) - Storing app settings in Saleor metadata - Building Dashboard UI inside the iframe - Making GraphQL calls with app tokens - Debugging webhook failures, auth errors, or permission issues - Deciding who can view the app and what they should see (user vs app scope) ## Rule Categories by Priority | Priority | Category | Impact | Prefix | | -------- | --------------- | -------- | --------------- | | 1 | Protocol | CRITICAL | `protocol-` | | 2 | Permissions | CRITICAL | `permissions-` | | 3 | Payment Apps | CRITICAL | `payment-` | | 4 | Webhooks | HIGH | `webhook-` | | 5 | Data & Settings | HIGH | `data-` | | 6 | Dashboard UI | MEDIUM | `dashboard-` | | 7 | Development | MEDIUM | `dev-` | ## Quick Reference ### 1. Protocol (CRITICAL)