Calendar Handoff Reader for Openclaw

Calendar Handoff Reader turns an event handoff into a normalized calendar record and can optionally deliver the resulting business action.

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 calendar-coordination-entry-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 calendar-coordination-entry-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 Calendar Handoff Reader?

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.

Calendar Handoff Reader Use Cases

  • Normalize an incoming calendar event handoff and compute its event digest.
  • Create or update a local coordination calendar artifact from a request.
  • Run a calendar workflow locally without enabling external delivery.
  • Send a message through SMTP when a delivery target and credentials are configured.
  • Register or submit a record through an HTTP endpoint when configured.
  • Verify whether a delivery completed, failed, or was left unconfigured by inspecting the receipt.

How Calendar Handoff Reader Works

  1. Read the upstream request supplied with --input; the expected input includes the event_ics handoff.
  2. Run the upstream identification stage to validate and process the input, producing an event_digest.
  3. Pass the identification result to the downstream stage, which computes the calendar_artifact business result.
  4. Create or update the local business artifact beneath the explicitly supplied --output-dir.
  5. If SMTP or HTTP delivery is configured through the environment or --delivery-config, perform the declared delivery action.
  6. Return the workflow output, including a delivery receipt indicating sent, delivered, failed, or unconfigured; delivery errors result in a nonzero exit.

Calendar Handoff Reader Setup

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.

Calendar Handoff Reader Data Schema & Taxonomy

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.

Calendar Handoff Reader Advanced Features

  • Combines identification and downstream business processing in a single executable workflow.
  • Supports local-only operation by default, with no external service contact when delivery is unconfigured.
  • Provides optional SMTP message delivery through environment variables or a delivery configuration file.
  • Supports HTTP registration or submission through a configured endpoint and optional API key.
  • Returns a delivery receipt with a concrete outcome and uses a nonzero exit to report errors.
  • Separates upstream identification, downstream delivery effects, and orchestration into distinct implementation files.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*