Release Configuration Brief transforms a configuration note into a stakeholder report, saving it locally and optionally delivering it through SMTP or HTTP.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install release-report-label-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 release-report-label-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Release Configuration Brief is an executable Openclaw Skills workflow that takes an upstream config_note, computes a configuration_entry, and uses that result to produce a downstream report_entry. It writes the resulting business artifact beneath an explicitly supplied output directory, combining identification, report generation, and artifact creation in one run.
Delivery is optional and local-only by default. When configured with SMTP or an HTTP endpoint, the skill performs the declared delivery action and returns a receipt with the outcome. Without delivery configuration, it contacts no external service and keeps the business record local.
examples/request.json, containing the config_note.configuration_entry.report_entry.--output-dir.sent, delivered, failed, or unconfigured as applicable.Run the complete workflow with Python, providing an input file and an explicit output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
To supply an optional delivery configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
Delivery configuration is optional; without it, the workflow writes the business artifact locally and contacts no external service. For SMTP, configure CLAWHUB_SMTP_HOST and, if needed, CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. Alternatively, provide an SMTP configuration through --delivery-config. For HTTP registration or submission, set CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY, or provide an endpoint in the delivery configuration file. Delivery targets, credentials, and recipient information must be supplied explicitly at runtime.
The workflow uses a two-stage business data flow:
| Stage | Input or result | Purpose |
|---|---|---|
| Upstream identification | config_note → configuration_entry |
Reads and validates the configuration note, then computes the identification result. |
| Downstream report | Identification result → report_entry |
Computes the business report and writes the local artifact. |
| Optional delivery | Runtime SMTP or HTTP settings → delivery receipt |
Performs the configured action and reports its outcome. |
Key files and outputs:
examples/request.json — bundled upstream input example.examples/expected.json — example of the complete two-stage output shape; runtime paths and receipt identifiers are excluded.--output-dir — required destination for the local business artifact.scripts/upstream/operation.py, scripts/upstream/validation.py, and scripts/upstream/config.json — identification-stage implementation and configuration.scripts/downstream/ — downstream delivery-stage implementation, including deliver_effect.scripts/run.py — complete workflow runner.source-map.json — source provenance for both extracted stages.sent, delivered, failed, and unconfigured.Loading
Convert a project intake note into a delivery ledger entry, save the business record locally, and optionally perform a configured real-world delivery action.

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.

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.

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

ClawVet Guard scans untrusted OpenClaw skills, validates scan coverage, and enforces a grade-based installation decision.

Retrieve and interpret Meta Ads account, campaign, and performance insights through secure, read-only Graph API requests.








































