Delivery Acknowledgement Guide for Openclaw

Process delivery inputs into acknowledgement guidance and confirmation records, with optional real-world delivery and a receipt.

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

Install & Download

1. ClawHub CLI

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

npx clawhub@latest install export-confirmation-style-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 export-confirmation-style-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 Delivery Acknowledgement Guide?

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.

Delivery Acknowledgement Guide Use Cases

  • Convert a delivery request or profile into acknowledgement guidance and a confirmation result.
  • Create or update a local confirmation record for review or downstream processing.
  • Send an acknowledgement through SMTP when mail settings and recipient details are supplied at runtime.
  • Register or submit a record through an HTTP endpoint when a delivery endpoint is configured.
  • Run the workflow locally without external network effects when no delivery target is configured.
  • Integrate a repeatable, receipt-producing acknowledgement process into a command-line workflow.

How Delivery Acknowledgement Guide Works

  1. Read and validate the upstream input, such as the bundled examples/request.json delivery profile.
  2. Run the identification stage to compute acknowledgement_guidance.
  3. Pass the guidance to the downstream operation and compute confirmation_result.
  4. Create or update the local business artifact under the explicitly supplied --output-dir.
  5. If SMTP or HTTP delivery is configured through environment variables or --delivery-config, perform the declared external action.
  6. Return workflow results and a delivery receipt indicating the outcome, such as sent, delivered, failed, or unconfigured; errors produce a nonzero exit.

Delivery Acknowledgement Guide 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 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.

Delivery Acknowledgement Guide Data Schema & Taxonomy

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 Acknowledgement Guide Advanced Features

  • Runs identification, business processing, local artifact creation, and optional delivery as one complete workflow.
  • Supports SMTP message delivery and HTTP-based registration or submission through explicit runtime configuration.
  • Accepts delivery settings from environment variables or an optional --delivery-config file.
  • Defaults to local-only operation, avoiding external service calls when no target is configured.
  • Returns a delivery receipt that distinguishes successful, failed, and unconfigured outcomes.
  • Reports errors with a nonzero process exit, supporting command-line monitoring and automation.
  • Includes separate upstream and downstream implementations, validation, configuration, and source provenance.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*