Service Class Planner for Openclaw

Service Class Planner converts a task profile into scheduling guidance and a task schedule, then saves the result locally or delivers it to a configured target.

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

Install & Download

1. ClawHub CLI

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

npx clawhub@latest install task-priority-guidance-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 task-priority-guidance-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 Service Class Planner?

Service Class Planner is an end-to-end business workflow skill that reads a task_profile, computes scheduling_guidance, and uses that result to build a task_schedule. It writes a local business artifact under the explicitly provided output directory, bringing identification and downstream execution together in one run.

When configured with an SMTP or HTTP delivery target, the skill can perform the declared delivery action and return a receipt describing the outcome. Without delivery configuration, it operates locally and contacts no external service. This makes it a practical addition to Openclaw Skills for repeatable task planning with an optional, explicit delivery step.

Service Class Planner Use Cases

  • Convert an incoming task profile into scheduling guidance and a complete operations task schedule.
  • Create or update a local task-schedule artifact for downstream business workflows.
  • Send a configured message through SMTP when the workflow requires notification.
  • Register or submit a business record through a configured HTTP endpoint.
  • Run the workflow locally without external calls when no delivery target is configured.
  • Inspect the expected output structure using the bundled example input and expected result.

How Service Class Planner Works

  1. Read the upstream task_profile from the input JSON file.
  2. Validate and process the input using the upstream identification stage to calculate scheduling_guidance.
  3. Pass the guidance into the downstream operation, which computes the task_schedule.
  4. Create or update the local business artifact beneath the specified --output-dir.
  5. If SMTP or HTTP delivery is configured through environment variables or a delivery configuration file, perform the declared action.
  6. Return a delivery receipt with an outcome such as sent, delivered, failed, or unconfigured; delivery errors produce a nonzero exit.

Service Class Planner Setup

Run the bundled workflow with Python and provide an input JSON file and output directory:

python scripts/run.py --input examples/request.json --output-dir ./workspace

To provide optional delivery settings in a file, add --delivery-config:

python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json

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, provide an SMTP object with smtp_host, smtp_port, and from_addr in the delivery configuration.

For HTTP registration or submission, configure CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY, or provide an endpoint object in the delivery configuration. Delivery targets, credentials, and recipients are supplied at runtime. With no delivery configuration, the skill writes the local artifact only and makes no external requests. The bundled examples/expected.json documents the output shape; runtime paths and receipt identifiers are excluded.

Service Class Planner Data Schema & Taxonomy

The workflow uses JSON input and output data:

Data element Role
task_profile Upstream input describing the task to plan.
scheduling_guidance Identification-stage result used by the downstream operation.
task_schedule Computed business result for the operations schedule.
delivery Receipt reporting the real delivery outcome when applicable.

Key files and directories:

  • examples/request.json — bundled upstream input example.
  • examples/expected.json — example of the complete two-stage output structure.
  • --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 — provenance information for both extracted stages.

Service Class Planner Advanced Features

  • Combines identification and downstream scheduling into one executable workflow.
  • Supports optional SMTP message delivery and HTTP registration or submission.
  • Accepts delivery settings from runtime environment variables or an explicit --delivery-config file.
  • Keeps local-only execution as the default when no delivery target is configured.
  • Returns a delivery receipt that distinguishes outcomes such as sent, delivered, failed, and unconfigured.
  • Reports delivery errors with a nonzero exit status.
  • Includes stage-specific implementations, validation, configuration, and source provenance for inspection.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*