agentsclimarketplace

Find product

Skill skuio/sku-skills/dist/claude/products/find-product

Open-source e-commerce agent skills for the SKU.io API — authored once, generated for Claude, OpenAI, and Gemini.

Install
npx -y skills add skuio/sku-skills --skill find-product

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Look up a product in the SKU.io catalog by SKU, barcode, or a free-text search over name and SKU. Use this whenever you need to resolve a product reference to its SKU.io product record and id — for example before adding it to a sales order, checking stock, or reporting on it.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, 925 tokens by cl100k_base, as published. Nobody here has run it

Find a Product

Use this skill to turn "the blue widget" or a scanned barcode into a concrete SKU.io product — its id, sku, name, and details — so downstream skills have an unambiguous reference.

Pick the right lookup

You have…CallWhy
An exact SKUGET /api/products/by-sku?sku=WIDGET-BLUE-01Direct, single result
A scanned barcode (UPC/EAN/GTIN)GET /api/products/barcode-lookup?code=0123456789012Resolves the barcode to its product (param is code)
A partial name or SKUGET /api/products/search?query=blue widgetFuzzy, may return several matches
A numeric product idGET /api/products/{id}Full record when you already have the id

Always prefer the most specific lookup you can. Use search only when you don't have an exact SKU or barcode — it can return multiple candidates that you must disambiguate.

Steps

  1. Choose the lookup above based on what you were given.

  2. Send the request with your Bearer token (scope products:read):

    curl -sS "https://$SKU_TENANT.sku.io/api/products/by-sku?sku=WIDGET-BLUE-01" \
      -H "Authorization: Bearer $SKU_PAT" -H "Accept: application/json"
    
  3. Handle the result:

    • Exactly one match → capture its id and sku; you're done.
    • Search returned several → narrow by matching the exact sku, or surface the top candidates (name + sku) to the user and ask which one. Do not silently pick the first.
    • No match → the product may not exist or may be archived. Report that rather than inventing an id. Consider a broader search query before giving up.

Notes

  • search is paginated — see shared/pagination.md. The best matches are on the first page; you rarely need to page for a lookup.
  • Product id is the stable key other skills expect (e.g. product_id on a sales-order line). Prefer passing id downstream over re-resolving by SKU each time.

API operations

MethodPathWhat it does
GET/api/products/searchFuzzy search products by name or SKU fragment.
GET/api/products/by-skuFetch a single product by its exact SKU.
GET/api/products/barcode-lookupResolve a scanned barcode (UPC/EAN/GTIN) to a product.
GET/api/products/{id}Fetch the full product record by its numeric id.

Authentication

Every request authenticates with a SKU.io Personal Access Token sent as a Bearer token:

Authorization: Bearer <YOUR_SKU_PAT>
  • Base URL: https://{tenant}.sku.io (replace {tenant} with your account subdomain)
  • Required scopes: products:read

Mint a token under Settings → Developer → Personal Access Tokens in the SKU.io web app. See shared/authentication.md for the full flow.


Improve this skill

Did this skill fall short—an unclear step, a wrong endpoint, or something it couldn't finish? Don't just work around it: capture what was off and open a pull request so the next agent does better.

  • Repo: https://github.com/skuio/sku-skills
  • Edit the canonical skill under skills/<domain>/<name>/ (not this generated file), then run npm run build and open a PR. External contributors: fork the repo and PR from the fork.
  • The full agent workflow is in AGENTS.md.

Your agent can do this end to end. The library gets better every time someone sends a fix.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.