Processing Capacity Planner identifies a processing profile from an input workload, records the resulting queue entry, and optionally delivers it to a configured service.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install processing-capacity-profile-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 processing-capacity-profile-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Processing Capacity Planner is an executable Openclaw Skills workflow that turns a workload note into a processing profile and a recorded business result. Its identify and deliver stages run together in one artifact, creating or updating a local job queue record under the output directory you specify.
Delivery is optional: configure SMTP or an HTTP endpoint to perform the declared external action and receive a delivery receipt. Without delivery configuration, the skill records the business artifact locally and contacts no external service.
examples/request.json.processing_profile.recorded_profile and create or update a job_queue_record beneath the supplied output directory.sent, delivered, failed, or unconfigured. Delivery errors result in a nonzero exit.Run the workflow with Python and provide an input file plus an explicit output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
To configure delivery, either set environment variables or pass --delivery-config delivery.json.
CLAWHUB_SMTP_HOST; optionally set CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD.CLAWHUB_DELIVERY_ENDPOINT; optionally set CLAWHUB_DELIVERY_API_KEY.smtp_host, smtp_port, and from_addr, or an HTTP endpoint, in the delivery configuration file.Without a delivery target, the workflow runs in local-only mode and does not contact external services. examples/expected.json documents the complete output shape, excluding runtime paths and receipt identifiers.
The workflow handles data in two stages:
| Stage | Input or result | Purpose |
|---|---|---|
| Identify | workload_note → processing_profile |
Reads and validates the upstream input, then computes a processing profile. |
| Deliver | processing_profile → recorded_profile |
Computes the downstream business result and creates or updates the job_queue_record. |
| Optional external delivery | Delivery configuration → delivery receipt |
Performs the configured action and reports its outcome. |
Files and locations:
examples/request.json — bundled upstream input.examples/expected.json — example of the complete two-stage output shape.--output-dir — explicitly supplied directory beneath which the local business artifact is written.scripts/upstream/operation.py, scripts/upstream/validation.py, and scripts/upstream/config.json — identify-stage implementation and configuration.scripts/downstream/ — downstream delivery implementation, including deliver_effect.scripts/run.py — complete workflow runner.source-map.json — provenance information for both extracted stages.Run-time paths and receipt identifiers may vary and are excluded from the bundled expected-output example.
source-map.json.Loading
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 a report request into a grouped account report, with optional real-world delivery and a receipt confirming the outcome.

Calculate a replenishment quantity, record the inventory planning result, and optionally deliver it to a configured business endpoint.

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








































