saleor-storefront
Build Reliable Saleor Storefronts
Saleor storefronts can fail when pricing, variants, permissions, checkout, and channel availability are misunderstood. This skill provides practical GraphQL patterns and troubleshooting guidance for reliable implementations.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "saleor-storefront" from https://skillstore.io/skills/saleor-saleor-storefront.md and its manifest at https://skillstore.io/api/skills/saleor-saleor-storefront/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「saleor-storefront」を使用しています。 Why is a product visible but not purchasable in a Saleor channel?
期待される結果:
- Check publication, channel listing, variant price, warehouse assignment, and stock.
- In legacy mode, also check shipping-zone coverage and warehouse assignment to that zone.
- In direct mode, verify shipping methods separately because visibility does not guarantee checkout success.
「saleor-storefront」を使用しています。 What should a variant picker do when a selected combination does not exist?
期待される結果:
- Keep options visible and let the customer choose a different value.
- Clear conflicting selections and resolve the selection against a specific variant.
- Disable add to cart until every required selection attribute is resolved.
「saleor-storefront」を使用しています。 How should a storefront handle a failed payment attempt?
期待される結果:
- Read the live checkout totals and transaction events.
- Check for authorization failures, stale transactions, and changed shipping totals.
- Use a fresh checkout when the existing checkout is invalid or accumulated failed transactions.
セキュリティ監査
安全All 56 static detections are false positives caused by Markdown syntax, GraphQL identifiers, documentation examples, or optional investigation commands. No executable malware behavior, credential exposure, network exfiltration, filesystem traversal, or prompt injection was found in the reviewed skill files.
リスク要因
⚙️ 外部コマンド (16)
🌐 ネットワークアクセス (4)
📁 ファイルシステムへのアクセス (3)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/saleor-saleor-storefront/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/saleor-saleor-storefront?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/saleor-saleor-storefront?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/saleor-saleor-storefront/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/saleor-saleor-storefront.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
saleor. (2026). saleor-storefront security audit report (audit version 1) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/saleor-saleor-storefront/audits/1BibTeX形式の引用
@techreport{saleor-saleor-saleor-storefront-2026,
author = {saleor},
title = {saleor-storefront security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/saleor-saleor-storefront/audits/1},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "saleor-storefront security audit report (audit version 1)"
version: "1.0.0"
type: report
authors:
- name: "saleor"
date-released: "2026-09-11"
url: "https://skillstore.io/skills/saleor-saleor-storefront/audits/1"
identifiers:
- type: other
value: "skillstore:saleor-saleor-storefront:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Plan a product page
Map Saleor product data, variant attributes, pricing, media, and availability into a clear product page workflow.
Debug checkout failures
Trace checkout state, shipping methods, payment transactions, and stale identifiers to isolate completion errors.
Audit channel availability
Compare channel, warehouse, stock, pricing, and shipping-zone conditions when products cannot be purchased.
これらのプロンプトを試す
Explain how Saleor products, variants, channels, prices, and checkouts relate. Use a short example for a beginner.
Design a channel-scoped Saleor GraphQL product query for pricing, selection attributes, media, availability, and cursor pagination. State nullable fields.
Given this Saleor checkout error and current checkout state, identify likely causes, required checks, and the safest recovery sequence: [paste details].
Analyze this Saleor channel availability problem across legacy and direct modes. Separate purchasability from shippability and produce a verification checklist: [paste configuration].
ベストプラクティス
- Pass the channel argument on product and availability queries.
- Use live authenticated checkout data for payment amounts and completion decisions.
- Treat nullable fields deliberately and distinguish purchasability from shippability.
回避
- Do not add a product to checkout without resolving a specific variant ID.
- Do not use staff tokens or cache user-specific checkout responses.
- Do not assume product availability guarantees shipping or successful checkout.
よくある質問
What does this skill cover?
Does it support every frontend framework?
Why is the channel argument important?
What is the difference between variant attribute types?
Can available products still fail at checkout?
Does this skill access my Saleor store?
開発者情報
作成者
saleorライセンス
MIT
作者バージョン
v1.0.0
Skillstore リビジョン
r1
参照
19bb472056c2085a0d323a15c7fe4c4ff1a2af48
メンテナンスの新しさ
2026/9/11
利用状況
0 ダウンロード · 0 閲覧