Processing Capacity Planner for Openclaw

Processing Capacity Planner identifies a processing profile from an input workload, records the resulting queue entry, and optionally delivers it to a configured service.

wxt-ai
v1.2.0
Oct 7, 2026
0
56
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install processing-capacity-profile-complete

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

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).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Processing Capacity Planner?

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.

Processing Capacity Planner Use Cases

  • Convert an incoming workload note into a processing profile and queue record.
  • Run a repeatable, two-stage business workflow from the command line.
  • Keep processing records local when no external delivery target is configured.
  • Submit or register a queue record through an explicitly configured HTTP endpoint.
  • Send a message through configured SMTP when the workflow requires email delivery.
  • Validate an integration and inspect its delivery outcome through the returned receipt.

How Processing Capacity Planner Works

  1. Read the upstream workload input, such as examples/request.json.
  2. Run the identify stage to validate the input and compute a processing_profile.
  3. Pass that profile into the downstream operation to compute a recorded_profile and create or update a job_queue_record beneath the supplied output directory.
  4. If SMTP or an HTTP delivery target is configured through environment variables or a delivery configuration file, perform the declared external action.
  5. Return workflow output, including a delivery receipt with an outcome such as sent, delivered, failed, or unconfigured. Delivery errors result in a nonzero exit.

Processing Capacity Planner Setup

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.

  • For SMTP, set CLAWHUB_SMTP_HOST; optionally set CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD.
  • For HTTP registration or submission, set CLAWHUB_DELIVERY_ENDPOINT; optionally set CLAWHUB_DELIVERY_API_KEY.
  • Alternatively, provide SMTP settings such as 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.

Processing Capacity Planner Data Schema & Taxonomy

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.

Processing Capacity Planner Advanced Features

  • Combines identification, business-result computation, local artifact creation, and optional delivery in one executable workflow.
  • Supports local-only execution by default; no external service is contacted unless a delivery target is configured.
  • Offers SMTP delivery through environment variables or an explicit configuration file.
  • Supports HTTP registration or submission with an optional API key.
  • Reports delivery outcomes in a receipt and signals errors with a nonzero process exit.
  • Separates upstream identification and downstream delivery implementations, with source provenance recorded in source-map.json.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*