Process delivery inputs into acknowledgement guidance and confirmation records, with optional real-world delivery and a receipt.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install export-confirmation-style-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 export-confirmation-style-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Delivery Acknowledgement Guide is an executable workflow that turns an upstream delivery profile into acknowledgement guidance, computes a confirmation result, and writes a business artifact to a specified local output directory. It combines identification and downstream processing in one run, making it useful for repeatable acknowledgement workflows with clear outputs.
When configured with an SMTP host or HTTP delivery endpoint, the skill can also perform the declared external action and report its outcome. Without delivery configuration, it operates locally and contacts no external service. This explicit opt-in behavior makes the skill a practical addition to Openclaw Skills for controlled business-process automation.
examples/request.json delivery profile.acknowledgement_guidance.confirmation_result.--output-dir.--delivery-config, perform the declared external action.sent, delivered, failed, or unconfigured; errors produce 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 supply delivery settings from a configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
For SMTP, configure CLAWHUB_SMTP_HOST and, as needed, CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. Alternatively, provide an SMTP configuration containing smtp_host, smtp_port, and from_addr in the delivery config.
For HTTP registration or submission, configure CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY, or provide an endpoint object in the delivery config. Delivery target, credentials, and recipient details are supplied at runtime. Without delivery configuration, the workflow only writes the local business artifact and makes no external requests. See examples/expected.json for the expected output shape; runtime paths and receipt identifiers are omitted there.
The workflow processes two business stages and produces a local artifact plus, when applicable, a delivery receipt.
| Stage or output | Description |
|---|---|
delivery_profile |
Upstream input read from the supplied request JSON. |
acknowledgement_guidance |
Identification result computed from the input. |
confirmation_result |
Business result computed by the downstream operation. |
local_confirmation_receipt |
Local business artifact created or updated beneath --output-dir; it is also the declared business action for configured delivery. |
delivery receipt |
Reports the real delivery outcome, including sent, delivered, failed, or unconfigured, when applicable. |
Key files are organized by workflow responsibility:
scripts/upstream/: identification implementation, validation, and config.json.scripts/downstream/: delivery-stage implementation, including deliver_effect.scripts/run.py: complete workflow runner.source-map.json: provenance information for both extracted stages.examples/request.json: bundled upstream input; examples/expected.json: example output structure.--delivery-config file.Loading
Artifact Delivery Planner identifies an incoming request, creates a local delivery route record, and optionally performs the configured external delivery action.

Resolve supplier aliases into canonical names, produce a business match report, and optionally deliver the result to a configured destination.

Turn a content profile into handling guidance and a local review plan, with optional configured email or HTTP delivery.

Convert delivery failure details into a bounded retry schedule and a next-action handoff record, with optional real-world delivery.

Service Class Planner converts a task profile into scheduling guidance and a task schedule, then saves the result locally or delivers it to a configured target.

Classify a stakeholder brief, create a client-facing preview from approved sections, and optionally deliver it while recording the outcome.








































