name string | description string | category string | version string | license string | compatibility string | skill_md string | rule_md string | references list | scripts list | eval_tasks int64 |
|---|---|---|---|---|---|---|---|---|---|---|
woocommerce-plugin-development | Build and change WooCommerce plugins with hooks, CRUD data stores, HPOS-safe order access, nonces, capabilities, and gettext. Use when writing or reviewing a plugin that reads or writes WooCommerce products, orders, customers, or checkout. | Platforms and storefronts | 0.3.2 | MIT | null | ---
name: woocommerce-plugin-development
description: "Build and change WooCommerce plugins with hooks, CRUD data stores, HPOS-safe order access, nonces, capabilities, and gettext. Use when writing or reviewing a plugin that reads or writes WooCommerce products, orders, customers, or checkout."
license: MIT
metadata:
... | # WooCommerce plugin development
- Read and write orders and products with WooCommerce CRUD (`wc_get_order`, `wc_get_product`, setters, one `save()`). Do not use `get_post`, `get_post_meta`, `update_post_meta`, or `get_posts` for orders.
- Declare HPOS compatibility from the main plugin file on `before_woocommerce_ini... | [
{
"path": "references/hooks.md",
"content": "# WooCommerce hooks\n\nConfirm argument order in the WooCommerce version you are running when a signature is load-bearing. Prefer a hook that receives a `WC_Order` or `WC_Product`. If a hook passes only an id, load the object with `wc_get_order()` or `wc_get_prod... | [] | 2 |
woocommerce-rest-api | Call the WooCommerce REST API at wc/v3, including authentication, pagination, batch writes, and webhook registration, and keep it separate from the Store API. Use when an external system integrates with a WooCommerce store over HTTP. | Platforms and storefronts | 0.3.2 | MIT | null | ---
name: woocommerce-rest-api
description: "Call the WooCommerce REST API at wc/v3, including authentication, pagination, batch writes, and webhook registration, and keep it separate from the Store API. Use when an external system integrates with a WooCommerce store over HTTP."
license: MIT
metadata:
author: Naser S... | # WooCommerce REST API
- Call `/wp-json/wc/v3/` from the server. Do not send consumer secrets to the browser or to the Store API (`/wp-json/wc/store/v1/`).
- Authenticate over HTTPS with HTTP Basic auth: consumer key as the username, consumer secret as the password. Use query-string credentials only when the host stri... | [
{
"path": "references/endpoints.md",
"content": "# WooCommerce REST API endpoints\n\nBase path: `/wp-json/wc/v3/`. All routes below are relative to that base. Authenticate every call as described in `SKILL.md`.\n\n## Resources\n\n| Path | Typical use |\n| --- | --- |\n| `products` | Create and update the pa... | [] | 2 |
wordpress-plugin-security | Review and implement WordPress plugin security: capabilities, nonces, sanitization, escaping, prepared SQL, and REST permission callbacks. Use when adding admin screens, AJAX, uploads, hooks, or REST routes in a WordPress or WooCommerce plugin. | Platforms and storefronts | 0.3.2 | MIT | null | ---
name: wordpress-plugin-security
description: "Review and implement WordPress plugin security: capabilities, nonces, sanitization, escaping, prepared SQL, and REST permission callbacks. Use when adding admin screens, AJAX, uploads, hooks, or REST routes in a WordPress or WooCommerce plugin."
license: MIT
metadata:
... | # WordPress plugin security
- Check a capability with `current_user_can()`, not a role name. Use `edit_shop_orders`, `edit_products`, or `manage_woocommerce` for shop operations.
- Verify a nonce on cookie-authenticated state changes. A nonce does not authenticate the user and does not belong on a server-to-server web... | [
{
"path": "references/review-checklist.md",
"content": "# Plugin security review\n\nCheck each new entry point. Skip a line only when it does not apply, and say why.\n\n## Entry\n\n- The file starts with `defined( 'ABSPATH' ) || exit;` or is loaded only from a file that does.\n- Admin-post, admin-ajax, REST... | [] | 2 |
payment-gateway-integration | Integrate a payment provider with idempotent charges, signature-checked webhooks, and an explicit map from provider states to order states. Use when adding or changing checkout payment, capture, refund, or payment notification handling. | Payments and orders | 0.3.2 | MIT | null | ---
name: payment-gateway-integration
description: "Integrate a payment provider with idempotent charges, signature-checked webhooks, and an explicit map from provider states to order states. Use when adding or changing checkout payment, capture, refund, or payment notification handling."
license: MIT
metadata:
autho... | # Payment gateway integration
- Keep card numbers and CVV on the payment provider. Do not post or store them on the merchant server.
- Create the shop order in an unpaid status before redirecting the shopper.
- Send a stable idempotency key for each payment attempt, and reuse it when retrying that same attempt.
- Mark... | [
{
"path": "references/woocommerce-gateway.md",
"content": "# WooCommerce payment gateway\n\nExtend `WC_Payment_Gateway` and register it on `woocommerce_payment_gateways`.\n\n```php\nclass Example_Gateway extends WC_Payment_Gateway {\n public function __construct() {\n $this->id = '... | [] | 2 |
product-catalog-modeling | Model a sellable catalog of simple products, variants, attributes, SKUs, and stock, and check the model before importing it. Use when designing product data, variation matrices, inventory rules, or catalog imports. | Catalog and search | 0.3.2 | MIT | The catalog checker requires Node.js 20 or newer. No network access. | ---
name: product-catalog-modeling
description: "Model a sellable catalog of simple products, variants, attributes, SKUs, and stock, and check the model before importing it. Use when designing product data, variation matrices, inventory rules, or catalog imports."
license: MIT
compatibility: "The catalog checker requir... | # Product catalog modeling
- Treat each variant as the purchasable unit. A variable parent does not have its own SKU or price.
- Keep SKUs unique across simple products and variants.
- Define variation attributes as a closed option list. Each variant sets every variation attribute, and no two variants share a combinat... | [
{
"path": "references/variation-model.md",
"content": "# Mapping the catalog model to WooCommerce\n\nWooCommerce product types match this model: `simple`, `variable`, `external`, and `grouped`.\n\n## Global attributes\n\nCreate a global attribute once, then attach terms. The taxonomy name is `pa_` plus the ... | [
{
"path": "scripts/validate-catalog.mjs",
"content": "#!/usr/bin/env node\nimport { readFile } from \"node:fs/promises\";\n\nconst TYPES = new Set([\"simple\", \"variable\", \"external\", \"grouped\"]);\nconst BACKORDERS = new Set([\"no\", \"notify\", \"yes\"]);\nconst STOCK_STATUS = new Set([\"instock\", \... | 2 |
marketplace-search-and-ranking | Index purchasable catalog units and rank them with text relevance, facets, stock, and language-aware matching for Persian and other languages. Use when building marketplace search, filters, relevance, or multilingual product discovery. | Catalog and search | 0.3.2 | MIT | The search-text normalizer requires Node.js 20 or newer. No network access. | ---
name: marketplace-search-and-ranking
description: "Index purchasable catalog units and rank them with text relevance, facets, stock, and language-aware matching for Persian and other languages. Use when building marketplace search, filters, relevance, or multilingual product discovery."
license: MIT
compatibility: ... | # Marketplace search and ranking
- Index each purchasable unit. A variant with its own price or stock is its own document, with parent title and brand copied on.
- Normalize query text and indexed text the same way: Persian Yeh and Kaf, ASCII digits, ZWNJ removed for matching, bidi marks stripped.
- Do not stem Persia... | [
{
"path": "references/document-and-ranking.md",
"content": "# Search documents and a starting rank\n\nThis is an implementation note for the marketplace search skill. The weights are a default to review with real queries, not a measured optimum.\n\n## Field weights\n\n| Field | Weight | Analyzer |\n| --- | ... | [
{
"path": "scripts/normalize-search-text.mjs",
"content": "#!/usr/bin/env node\nimport { readFile } from \"node:fs/promises\";\n\nconst BIDI_MARKS = /[\\u200E\\u200F\\u202A-\\u202E\\u2066-\\u2069]/g;\nconst ARABIC_YEH = /\\u064A/g;\nconst ARABIC_KAF = /\\u0643/g;\nconst PERSIAN_DIGITS = /[\\u06F0-\\u06F9]/g... | 2 |
checkout-ux-and-conversion | Design checkout so the full cost is visible before payment, guest purchase works, and field or payment errors can be corrected without losing the cart. Use when changing the checkout flow, address form, payment choice, or order confirmation page. | Conversion and growth | 0.3.2 | MIT | null | ---
name: checkout-ux-and-conversion
description: "Design checkout so the full cost is visible before payment, guest purchase works, and field or payment errors can be corrected without losing the cart. Use when changing the checkout flow, address form, payment choice, or order confirmation page."
license: MIT
metadata... | # Checkout UX and conversion
- Show shipping, tax, discounts, and the charged total before the pay control. Update that total when the address or shipping method changes.
- Allow guest checkout unless the shop has a written reason not to. Do not force account creation before payment.
- Validate on the server. Show fie... | [
{
"path": "references/checkout-review.md",
"content": "# Checkout review\n\nWalk a real order in the browser. Record pass or fail. Do not treat a screenshot of the empty form as a review.\n\n## Before payment\n\n- Guest checkout is available, or the shop has a written reason it is not.\n- Line items, discou... | [] | 2 |
rtl-and-persian-localization | Localize a storefront for Persian (fa_IR) and right-to-left layout: logical CSS, digits, Yeh and Kaf, ZWNJ, currency display, and Gregorian storage. Use when building or reviewing Persian, Farsi, or RTL commerce UI. | Conversion and growth | 0.3.2 | MIT | The Persian normalizer requires Node.js 20 or newer. No network access. | ---
name: rtl-and-persian-localization
description: "Localize a storefront for Persian (fa_IR) and right-to-left layout: logical CSS, digits, Yeh and Kaf, ZWNJ, currency display, and Gregorian storage. Use when building or reviewing Persian, Farsi, or RTL commerce UI."
license: MIT
compatibility: "The Persian normalize... | # RTL and Persian localization
- Set Persian pages to `lang="fa"` and `dir="rtl"`. In WordPress, rely on the `fa_IR` locale and `is_rtl()`.
- Use CSS logical properties (`margin-inline-start`, `text-align: start`). Do not fix layout by rewriting `left` and `right` in a copied stylesheet.
- Mirror back and forward icon... | [
{
"path": "references/persian-text.md",
"content": "# Persian text handling\n\nUse this note when you change strings, search tokens, or formatted amounts. The functions in `scripts/normalize-persian.mjs` implement the folds below.\n\n## Letters\n\n| Input | Code point | Fold to |\n| --- | --- | --- |\n| Ara... | [
{
"path": "scripts/normalize-persian.mjs",
"content": "#!/usr/bin/env node\nimport { readFile } from \"node:fs/promises\";\n\nconst ARABIC_YEH = /\\u064A/g;\nconst ARABIC_KAF = /\\u0643/g;\nconst PERSIAN_DIGITS = /[\\u06F0-\\u06F9]/g;\nconst ARABIC_INDIC_DIGITS = /[\\u0660-\\u0669]/g;\nconst ZWNJ = /\\u200C... | 2 |
order-and-webhook-reliability | Accept order and payment webhooks with a raw-body signature check, durable deduplication, and reconciliation against the source of truth. Use when handling order events, payment notifications, or outbound webhook delivery. | Payments and orders | 0.3.2 | MIT | The signature checker requires Node.js 20 or newer. No network access. | ---
name: order-and-webhook-reliability
description: "Accept order and payment webhooks with a raw-body signature check, durable deduplication, and reconciliation against the source of truth. Use when handling order events, payment notifications, or outbound webhook delivery."
license: MIT
compatibility: "The signature... | # Order and webhook reliability
- Verify webhook signatures against the raw body with a constant-time compare, before trusting the JSON.
- Persist the event in a unique inbox, then return 2xx. A delivery attempt id is not an idempotency key.
- Dedupe WooCommerce webhooks on resource id, topic, and `date_modified_gmt`.... | [
{
"path": "references/woocommerce-webhooks.md",
"content": "# WooCommerce webhook delivery\n\nSource of this note: WooCommerce webhook documentation and `WC_Webhook::deliver()`. Confirm header names against the shop's WooCommerce version when you debug a live miss.\n\n## Request\n\n- Method: `POST`\n- Conte... | [
{
"path": "scripts/verify-hmac-signature.mjs",
"content": "#!/usr/bin/env node\nimport { createHmac, timingSafeEqual } from \"node:crypto\";\nimport { readFile } from \"node:fs/promises\";\n\n/**\n * WooCommerce signs the raw JSON body with HMAC-SHA256 and Base64.\n * The secret is passed through wp_special... | 3 |
ecommerce-seo-structured-data | Add product JSON-LD that matches the visible offer, including price, currency, availability, and images, without a second conflicting Product node. Use when editing product-page SEO, schema.org markup, or merchant listing data. | Conversion and growth | 0.3.2 | MIT | The JSON-LD checker requires Node.js 20 or newer. No network access. | ---
name: ecommerce-seo-structured-data
description: "Add product JSON-LD that matches the visible offer, including price, currency, availability, and images, without a second conflicting Product node. Use when editing product-page SEO, schema.org markup, or merchant listing data."
license: MIT
compatibility: "The JSON... | # Ecommerce SEO structured data
- Emit one Product node that matches the visible product. Do not add a second Product JSON-LD block on a WooCommerce page that already prints one.
- Prefer the `woocommerce_structured_data_product` filter on WooCommerce. On a custom storefront, render JSON-LD in the server HTML.
- Use a... | [
{
"path": "references/product-jsonld.md",
"content": "# Product JSON-LD\n\n## One node on a WooCommerce product page\n\nWooCommerce builds product structured data in `WC_Structured_Data` and prints it with the single product template. Filter the array before it is encoded:\n\n```php\nadd_filter(\n 'wooco... | [
{
"path": "scripts/check-product-jsonld.mjs",
"content": "#!/usr/bin/env node\nimport { readFile } from \"node:fs/promises\";\n\nconst AVAILABILITY = new Set([\n \"BackOrder\",\n \"Discontinued\",\n \"InStock\",\n \"InStoreOnly\",\n \"LimitedAvailability\",\n \"OnlineOnly\",\n \"OutOfStock\",\n \"Pr... | 2 |
multi-vendor-payouts | Split a marketplace order by vendor, record commission as ledger entries, and pay vendors only settled amounts. Use when adding vendor catalogs, commissions, refunds that cross vendors, or payout batches. | Payments and orders | 0.3.2 | MIT | null | ---
name: multi-vendor-payouts
description: "Split a marketplace order by vendor, record commission as ledger entries, and pay vendors only settled amounts. Use when adding vendor catalogs, commissions, refunds that cross vendors, or payout batches."
license: MIT
metadata:
author: Naser Sadrmanesh
version: "0.3.2"
... | # Multi-vendor payouts
- Put a `vendor_id` on every sellable line. Do not pay a line that has no vendor.
- Record commission as ledger entries. Do not rewrite the line price to remove the fee.
- Write payable entries only after the shopper's payment is confirmed. Authorization is not a payout.
- Hold entries until the... | [
{
"path": "references/ledger.md",
"content": "# Marketplace ledger\n\n## Entry types\n\n| Type | Who is credited | When it is written |\n| --- | --- | --- |\n| `goods` | Vendor | Order is paid, for that vendor's line totals after line discounts |\n| `commission` | Platform | Same moment, as the platform's s... | [] | 2 |
shopify-app-development | Build a Shopify app with the configured Admin API version, session-token auth for embedded admin requests, and HMAC-verified webhooks. Use when creating or changing a Shopify app, Admin GraphQL call, app proxy, or Shopify webhook handler. | Platforms and storefronts | 0.3.2 | MIT | null | ---
name: shopify-app-development
description: "Build a Shopify app with the configured Admin API version, session-token auth for embedded admin requests, and HMAC-verified webhooks. Use when creating or changing a Shopify app, Admin GraphQL call, app proxy, or Shopify webhook handler."
license: MIT
metadata:
author:... | # Shopify app development
- Configure the API version and app-specific webhooks in `shopify.app.toml`. Do not hard-code an API version in a handler.
- Authenticate before trusting a shop domain. Embedded admin requests need a validated session token. App proxy signatures do not authorize shop changes.
- Use the GraphQ... | [
{
"path": "references/auth-and-webhooks.md",
"content": "# Shopify auth and webhooks\n\nThese notes follow Shopify's app authentication and webhook delivery docs. Header names are case-insensitive on the wire.\n\n## HTTPS webhook headers\n\n| Header | Use |\n| --- | --- |\n| `X-Shopify-Topic` | Topic, such ... | [] | 2 |
headless-nextjs-storefront | Build a Next.js storefront that loads catalog data on the server, keeps admin secrets off the client, and revalidates price and stock. Use when adding product, cart, or checkout UI in a Next.js App Router storefront for WooCommerce or another headless commerce API. | Platforms and storefronts | 0.3.2 | MIT | null | ---
name: headless-nextjs-storefront
description: "Build a Next.js storefront that loads catalog data on the server, keeps admin secrets off the client, and revalidates price and stock. Use when adding product, cart, or checkout UI in a Next.js App Router storefront for WooCommerce or another headless commerce API."
li... | # Headless Next.js storefront
- Render catalog price and availability in server HTML. Do not require client JavaScript for the price a crawler should see.
- Keep WooCommerce consumer secrets and Shopify Admin tokens in server environment variables. Do not import them from a client component.
- Use the public storefron... | [
{
"path": "references/cache-and-cart.md",
"content": "# Cache and cart boundaries\n\n## Product cache\n\nTag each product fetch with a stable id:\n\n```js\nconst response = await fetch(productUrl, {\n next: { tags: [`product:${id}`] },\n});\n```\n\nThe exact `fetch` cache options depend on the installed Ne... | [] | 2 |
google-merchant-product-feeds | Build a Google Merchant Center product feed item with the required id, title, description, link, image, availability, and price fields. Use when exporting products to Merchant Center, Content API items, or a product feed file. | Catalog and search | 0.3.2 | MIT | The feed item checker requires Node.js 20 or newer. No network access. | ---
name: google-merchant-product-feeds
description: "Build a Google Merchant Center product feed item with the required id, title, description, link, image, availability, and price fields. Use when exporting products to Merchant Center, Content API items, or a product feed file."
license: MIT
compatibility: "The feed ... | # Google Merchant product feeds
- Emit one item per purchasable unit. Keep `id` stable and at most 50 characters. Share `item_group_id` across variants.
- Require `id`, `title` or `structured_title`, `description` or `structured_description`, `link`, `image_link`, `availability`, and `price`.
- Write `price` as major ... | [
{
"path": "references/attributes.md",
"content": "# Merchant Center item attributes\n\nSource: Google Merchant Center product data specification. Limits below are the ones that specification states for the common required attributes.\n\n## Identity\n\n- `id`: at most 50 characters, unique per product, stabl... | [
{
"path": "scripts/check-feed-item.mjs",
"content": "#!/usr/bin/env node\nimport { readFile } from \"node:fs/promises\";\n\nconst AVAILABILITY = new Set([\"in_stock\", \"out_of_stock\", \"preorder\", \"backorder\"]);\n\nexport function checkFeedItem(item) {\n const errors = [];\n if (!item || typeof item ... | 2 |
tax-and-shipping | Calculate tax and shipping from the destination and the store's configured rules, and store the breakdown on the order. Use when changing tax classes, shipping zones, rates, or the amount shown before payment. | Payments and orders | 0.3.2 | MIT | null | ---
name: tax-and-shipping
description: "Calculate tax and shipping from the destination and the store's configured rules, and store the breakdown on the order. Use when changing tax classes, shipping zones, rates, or the amount shown before payment."
license: MIT
metadata:
author: Naser Sadrmanesh
version: "0.3.2"... | # Tax and shipping
- Take tax rates from the store's configuration or its tax service. Do not invent a percent in the theme or the client.
- Store each tax line with its rate id and amount. Do not recompute a historical order from today's rate table.
- Respect inclusive versus exclusive catalog prices. Do not mix them... | [
{
"path": "references/woocommerce.md",
"content": "# WooCommerce tax and shipping\n\nUse WooCommerce's tax and shipping services. Do not reimplement a rate table in the theme.\n\n## Tax\n\n- Prices inclusive or exclusive are a store setting (`woocommerce_prices_include_tax`). Read it. Do not hard-code one m... | [] | 2 |
subscription-billing | Model subscription state, renewal charges, proration, and dunning without treating a renewal as a new one-time checkout. Use when adding or changing recurring billing, plan changes, cancellation, or failed renewal recovery. | Payments and orders | 0.3.2 | MIT | null | ---
name: subscription-billing
description: "Model subscription state, renewal charges, proration, and dunning without treating a renewal as a new one-time checkout. Use when adding or changing recurring billing, plan changes, cancellation, or failed renewal recovery."
license: MIT
metadata:
author: Naser Sadrmanesh
... | # Subscription billing
- Store the subscription separately from invoices: status, interval, and period start and end in UTC.
- Activate a paid plan only after the first charge is confirmed. A trial stores its end and does not pretend a charge succeeded.
- Create one renewal invoice per period. Retry that charge with t... | [
{
"path": "references/states.md",
"content": "# Subscription states\n\n## Allowed transitions\n\n| From | Event | To |\n| --- | --- | --- |\n| `trialing` | Trial converts and the first charge succeeds | `active` |\n| `trialing` | Shopper cancels during the trial | `canceled` |\n| `active` | Renewal charge s... | [] | 2 |
fraud-and-risk-basics | Hold or review risky payments using provider signals, velocity, and 3-D Secure without storing card numbers. Use when adding payment risk checks, a manual review queue, or decline handling for card abuse. | Payments and orders | 0.3.2 | MIT | null | ---
name: fraud-and-risk-basics
description: "Hold or review risky payments using provider signals, velocity, and 3-D Secure without storing card numbers. Use when adding payment risk checks, a manual review queue, or decline handling for card abuse."
license: MIT
metadata:
author: Naser Sadrmanesh
version: "0.3.2"... | # Fraud and risk basics
- Let the payment provider collect card data. Do not store PAN or CVV. Store the provider payment id and result codes.
- Treat AVS, CVV, and 3-D Secure results as signals. Do not treat a match as proof or a mismatch as automatic fraud.
- Do not capture while 3-D Secure is still pending.
- Put h... | [] | [] | 2 |
vector-product-search | Add vector retrieval beside lexical product search, with one embedding per purchasable unit and exact SKU lookup kept first. Use when adding embedding search, hybrid ranking, or re-embedding after catalog edits. | Catalog and search | 0.3.2 | MIT | null | ---
name: vector-product-search
description: "Add vector retrieval beside lexical product search, with one embedding per purchasable unit and exact SKU lookup kept first. Use when adding embedding search, hybrid ranking, or re-embedding after catalog edits."
license: MIT
metadata:
author: Naser Sadrmanesh
version: ... | # Vector product search
- Embed one vector per purchasable unit, not one vector per parent when variants differ.
- Use the same model, dimension, and similarity metric for the index and the query. Store `model_id` and a hash of the embedded text.
- Normalize text the same way as lexical search before embedding, includ... | [
{
"path": "references/index.md",
"content": "# Vector index beside lexical search\n\n## Document\n\n| Field | Role |\n| --- | --- |\n| `unit_id` | Purchasable unit. Primary key. |\n| `parent_id` | Set for variants. |\n| `sku`, `gtin` | Exact match. Not part of the embedded text. |\n| `text_hash` | Hash of t... | [] | 2 |
commerce-agent-skills
Twenty-nine skills and matching rules for coding agents that build e-commerce and marketplace products, from the commerce-agent-skills project, with 60 evaluation tasks that check whether an agent's answer applies them.
The skills follow the Agent Skills format: a folder with a SKILL.md file that has name and description frontmatter, plus optional reference notes and small Node.js scripts. Each skill has a short plain-Markdown rule for agents that keep rules in context.
Docs: https://sadrmanesh.github.io/commerce-agent-skills/ · Package: @sadrmanesh/commerce-agent-skills on npm · Source: GitHub
What the skills cover
| Category | Skills |
|---|---|
| Platforms and storefronts | WooCommerce plugins and REST API, WordPress plugin security, Shopify apps, headless Next.js storefronts |
| Payments and orders | Payment gateways, Stripe, Iranian gateways such as Zarinpal, order and webhook reliability, subscriptions, fraud and risk, tax and shipping, multi-vendor payouts |
| Catalog and search | Catalog modeling, marketplace search and ranking, vector product search, Google Merchant feeds, catalog import and migration |
| Conversion and growth | Checkout UX, SEO structured data, conversion event tracking, product description guardrails, RTL and Persian localization |
| Store operations | Inventory across warehouses, returns and refunds, B2B pricing, storefront accessibility and performance, MCP store tooling |
Configs
| Config | Rows | Fields |
|---|---|---|
skills |
29 | name, description, category, version, license, compatibility, skill_md (the full SKILL.md), rule_md, references and scripts (lists of path and content), eval_tasks |
evals |
60 | skill, task_id, task, must_include, must_not_include, example_answer |
The repository also holds the installable folders: skills/<name>/ (with SKILL.md, references/, scripts/, and evals/) and rules/<name>.md, exactly as published in version 0.3.2.
Usage
The simplest install is the npm CLI, which copies every skill to .agents/skills/ and every rule to .agents/rules/, or only the skills you name:
npx @sadrmanesh/commerce-agent-skills init
npx @sadrmanesh/commerce-agent-skills add woocommerce-plugin-development stripe-payments
Or take the folders straight from this dataset:
hf download sadrmanesh/commerce-agent-skills --repo-type dataset \
--include "skills/*" "rules/*" --local-dir .agents
Or load the records, for example to build a skill index or to score agent answers against the eval tasks:
from datasets import load_dataset
skills = load_dataset("sadrmanesh/commerce-agent-skills", "skills", split="train")
evals = load_dataset("sadrmanesh/commerce-agent-skills", "evals", split="test")
task = evals[0]
answer = "..." # the agent's answer to task["task"]
passed = all(term.lower() in answer.lower() for term in task["must_include"]) and not any(
term.lower() in answer.lower() for term in task["must_not_include"]
)
The repository's scripts/run-evals.mjs runs the same checks over a folder of answers, and every task comes with a worked example_answer that passes.
License
MIT © 2026 Naser Sadrmanesh
- Downloads last month
- 83