Calculate a replenishment quantity, record the inventory planning result, and optionally deliver it to a configured business endpoint.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install inventory-reorder-quantity-complete
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install inventory-reorder-quantity-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Stock Replenishment Planner is an executable Openclaw Skills workflow for turning an inventory_note into a replenishment quantity and a recorded inventory planning result. It combines identification, business-result calculation, and local artifact creation in one run, producing an inventory_planning_record beneath the explicitly supplied output directory.
When delivery is configured, the skill can also perform the declared downstream action through SMTP or an HTTP endpoint and return a receipt indicating the outcome. Without delivery configuration, it operates locally and contacts no external service.
examples/request.json, containing the inventory_note.quantity.recorded_quantity and creates or updates an inventory_planning_record in the specified output directory.sent, delivered, failed, or unconfigured; errors produce a nonzero exit.Run the workflow with Python and provide an input file and output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
To enable delivery, optionally add a delivery configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
Alternatively, configure delivery through environment variables. For SMTP, set CLAWHUB_SMTP_HOST; optionally provide CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. For HTTP registration or submission, set CLAWHUB_DELIVERY_ENDPOINT; optionally provide CLAWHUB_DELIVERY_API_KEY. A delivery target, credentials, and recipient must be supplied explicitly at runtime. With no delivery configuration, the workflow remains local-only.
The workflow uses JSON input and produces a local business artifact plus workflow results.
| Data or file | Purpose |
|---|---|
examples/request.json |
Bundled upstream input for the identification stage. |
examples/expected.json |
Example of the complete two-stage output shape; runtime paths and receipt identifiers are excluded. |
inventory_note |
Upstream input read by the identify stage. |
quantity |
Quantity computed by the identify stage and passed downstream. |
recorded_quantity |
Business result calculated by the downstream operation. |
inventory_planning_record |
Local business artifact created or updated beneath the supplied --output-dir. |
delivery |
Receipt describing the real delivery outcome when configured, including sent, delivered, failed, or unconfigured. |
scripts/upstream/ |
Identify-stage implementation: operation.py, validation.py, and config.json. |
scripts/downstream/ |
Delivery-stage implementation, including deliver_effect. |
scripts/run.py |
Runner for the complete workflow. |
source-map.json |
Provenance information for both extracted stages. |
--delivery-config.Loading
Processing Capacity Planner identifies a processing profile from an input workload, records the resulting queue entry, and optionally delivers it to a configured service.

Identify the appropriate reviewer group, create a local business record, and optionally deliver the request to a configured external service.

Determine whether a delivery requires a signature, create the corresponding documentation record, and optionally deliver it to a configured target.

Identify a callback URL, create its subscription record, and optionally deliver the registration to a configured external service.

Turn inventory lot data into an allocation plan and a fulfillment reservation, with optional configured delivery.

Regional Rollout Planner identifies a deployment region, creates a deployment brief record, and optionally delivers the result through SMTP or HTTP.








































