Calendar Handoff Reader turns an event handoff into a normalized calendar record and can optionally deliver the resulting business action.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install calendar-coordination-entry-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 calendar-coordination-entry-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Calendar Handoff Reader is an executable workflow for processing a calendar handoff from input through business outcome. It reads an event_ics request, computes an event_digest, then creates or updates a coordination calendar artifact in a caller-specified local output directory.
As an Openclaw Skills workflow, it combines identification and downstream processing in one run. Delivery is optional: with SMTP or HTTP delivery configuration, it performs the configured action and returns a receipt; without configuration, it saves the artifact locally and contacts no external service.
--input; the expected input includes the event_ics handoff.event_digest.calendar_artifact business result.--output-dir.--delivery-config, perform the declared delivery action.sent, delivered, failed, or unconfigured; delivery errors result in a nonzero exit.Run the workflow with Python and provide an input request and output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
The bundled examples/request.json is the sample upstream input. examples/expected.json documents the two-stage output shape; runtime paths and receipt identifiers are omitted from that example.
Delivery is optional. For SMTP message delivery, configure CLAWHUB_SMTP_HOST and, as needed, CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. Alternatively, pass a --delivery-config file containing SMTP settings such as smtp_host, smtp_port, and from_addr.
For HTTP registration or submission, configure CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY, or provide an endpoint in the delivery configuration file. Example with an explicit configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
Delivery targets, credentials, and recipients are supplied explicitly at runtime. Without delivery configuration, the workflow only records the artifact locally and makes no external calls.
The workflow processes a two-stage business payload:
| Stage or field | Purpose |
|---|---|
event_ics |
Upstream calendar handoff input. |
event_digest |
Identification result computed from the input. |
calendar_artifact |
Downstream business result used to create or update the local coordination artifact. |
delivery |
Receipt describing the real delivery outcome when a target is configured, or unconfigured when it is not. |
The caller chooses the local destination with --output-dir. The skill's implementation is organized into scripts/upstream/ for identification (operation.py, validation.py, and config.json), scripts/downstream/ for delivery processing and deliver_effect, and scripts/run.py for the complete workflow runner. source-map.json records source provenance for both extracted stages. The bundled examples/expected.json illustrates the output structure without runtime paths or receipt identifiers.
Loading
Customer Record Field Prep transforms an input record note into a prepared field and reporting export artifact, with optional configured delivery.

Turn referral form JSON into a validated handoff digest and business packet, with optional configured delivery and a receipt.

Supplier Terms Reader converts supplier input into purchase terms and a purchase draft, with optional configured delivery and a receipt.

Turn GeoJSON field stops into a sequenced route and dispatch manifest, with optional real-world delivery.

Support Intake Digest transforms a support request snippet into a case comment, saves the business record locally, and optionally delivers it through configured SMTP or HTTP.

Knowledge Note Segmenter turns an input note into a segmented record, updates a local knowledge index, and optionally delivers the result to a configured target.








































