Release Configuration Brief for Openclaw

Release Configuration Brief transforms a configuration note into a stakeholder report, saving it locally and optionally delivering it through SMTP or HTTP.

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

Install & Download

1. ClawHub CLI

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

npx clawhub@latest install release-report-label-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 release-report-label-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 Release Configuration Brief?

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.

Release Configuration Brief Use Cases

  • Convert a configuration note into a structured stakeholder configuration report.
  • Generate and retain a local release or business report without contacting external services.
  • Send a report through SMTP when mail delivery settings and recipient details are provided at runtime.
  • Register or submit a business record to an HTTP endpoint when an endpoint is configured.
  • Automate a two-stage identify-and-deliver workflow from a single command.

How Release Configuration Brief Works

  1. Read the upstream input JSON, such as examples/request.json, containing the config_note.
  2. Run the upstream identification stage to validate the input and compute a configuration_entry.
  3. Pass the identification result to the downstream stage, which computes the business result as a report_entry.
  4. Create or update the local business artifact beneath the required --output-dir.
  5. If SMTP or HTTP delivery is configured, perform the declared action and include a delivery receipt reporting sent, delivered, failed, or unconfigured as applicable.
  6. Return an error through a nonzero exit status if an operation fails.

Release Configuration Brief Setup

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.

Release Configuration Brief Data Schema & Taxonomy

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.

Release Configuration Brief Advanced Features

  • Combines identification, business-result computation, local artifact writing, and optional delivery in one executable workflow.
  • Supports SMTP message sending through environment variables or an explicit delivery configuration file.
  • Supports HTTP registration or submission through a configured endpoint, with an optional API key.
  • Produces a delivery receipt that distinguishes outcomes such as sent, delivered, failed, and unconfigured.
  • Defaults to local-only operation, avoiding external service calls when delivery is not configured.
  • Reports operation errors with a nonzero exit status.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*