agentsclimarketplace

Adjust inventory

Skill skuio/sku-skills/dist/claude/inventory/adjust-inventory

Adjust the on-hand quantity of a product at a warehouse in SKU.io — an increase, a decrease, or a set-to-value. Use this for stock takes, corrections, damage/shrinkage write-offs, or found stock. Resolve the product with find-product first so the adjustment targets the right product and warehouse.From its SKILL.md

Install
npx -y skills add skuio/sku-skills --skill adjust-inventory

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

One thing to look at

  • 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 file declares

Copied from the file, not written here

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

4.2 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Adjust Inventory

Use this skill to change the on-hand quantity of a product at a warehouse — a stock take correction, a write-off for damage/shrinkage, or booking in found stock. It maps to POST /api/inventory-adjustments (scope inventory:write; also requires the inventory.adjust permission on the token's user).

Choose the adjustment type

Intentadjustment_typequantity means
Add stock (found, returned to stock, receipt correction)increasehow many to add
Remove stock (damage, shrinkage, write-off)decreasehow many to remove
Reconcile to a counted figure (stock take)setthe new on-hand total

Prefer set when you have a physically counted number — it's unambiguous and doesn't require you to compute the delta. Use increase/decrease when you know the change, not the total.

Before you post

  1. Resolve the product with find-product to get product_id.
  2. Know the warehouse — you need a warehouse_id. If the account has multiple warehouses and you weren't told which, ask; don't guess.
  3. Cost for increases — if you're increasing stock for a product that has no average cost yet, include unit_cost, or the request will be rejected. Decreases don't need a cost.

Request

curl -sS -X POST "https://$SKU_TENANT.sku.io/api/inventory-adjustments" \
  -H "Authorization: Bearer $SKU_PAT" \
  -H "Content-Type: application/json" -H "Accept: application/json" \
  -d '{
    "adjustment_date": "2026-07-09",
    "product_id": 1567,
    "warehouse_id": 3,
    "adjustment_type": "set",
    "quantity": 240,
    "notes": "Q3 stock take — counted 240 on shelf A2"
  }'

Handle the response

  • 200/201 → the adjustment was recorded; on-hand is updated.
  • 422 → validation failed. Common causes: zero quantity (not allowed), missing unit_cost on a first-time increase, or a product_id/warehouse_id that doesn't exist. Read the errors map and fix the named field. See shared/errors.md.
  • 403 → the token lacks inventory:write, or the user lacks the inventory.adjust permission.

Guardrails

  • Adjustments move real stock and post cost — confirm product, warehouse, type, and quantity before sending, especially for set (it overwrites the on-hand total).
  • Always include notes with the reason — adjustments are audited.
  • Not idempotent: a blind retry after a timeout can double-apply. On an ambiguous failure, check current on-hand before re-posting.

API operations

MethodPathWhat it does
POST/api/inventory-adjustmentsCreate an inventory adjustment (increase, decrease, or set) for a product at a warehouse.

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: inventory:write, 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.

What ships with it: 4 files

11.3 KB alongside SKILL.md

Gives 0 of the 12 instructions most operations skills give in ~1.0k tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • resolve product with find-product before adjusting
  • ask for warehouse if multiple exist
  • include unit_cost for first-time stock increases
  • prefer set when using a physically counted number
  • read errors map and fix named field on validation failure
  • confirm product warehouse type and quantity before sending

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.