360 Secure SkillHub
360 安全技能中心

Service Class Planner

读取 task_profile 生成 scheduling_guidance 与 task_schedule，并写入本地业务产物；配置 SMTP 或 HTTP 投递目标后可发送消息或提交记录并返回回执，未配置时仅本地保存。

wxt-ai
wxt-ai
热度 7.65
最近更新 2026-10-07 19:27:22
分类：自动化依赖：代码执行 / 读写文件 / 第三方 API应用场景：日程安排 / 任务管理 / 工作流 / 自动化脚本

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add task-priority-guidance-complete
Metadata
name
Service Class Planner
description
Set service-class guidance for a task. Then it executes the downstream business step: Build an operations task schedule. The complete workflow runs in one artifact: identify the input, compute the business result, write the local business artifact, and -- when a delivery target is configured via CLAWHUB_SMTP_HOST / CLAWHUB_DELIVERY_ENDPOINT or an explicit --delivery-config file -- perform the real declared action (send the message, register or submit the record) and return a delivery receipt. Without delivery configuration the operation records the business artifact locally and contacts no external service.
version
1.2.0

Service Class Planner — complete probe workflow

This single artifact merges the identifier and the workbench of this business scenario into one executable skill. Running it performs the full chain:

  1. Identify — reads the upstream input (task_profile) and computes the identification result (scheduling_guidance).
  2. Deliver — feeds the identification result into the downstream operation, computes the business result (task_schedule), and creates or updates a local business artifact beneath the explicitly supplied --output-dir. Effect: local_task_schedule.
  3. Real delivery — when a delivery target is configured, performs the declared business action (local_task_schedule) and returns a delivery receipt with the real outcome (sent / delivered / failed / unconfigured).

Run

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

The bundled examples/request.json is the upstream input; examples/expected.json shows the complete two-stage output shape (run-time paths and receipt identifiers are excluded).

Delivery configuration (optional, default: local only)

  • Message sends (smtp): set CLAWHUB_SMTP_HOST (optionally CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, CLAWHUB_SMTP_PASSWORD), or pass --delivery-config with an smtp_host / smtp_port / from_addr object.
  • Registration / submission effects (http): set CLAWHUB_DELIVERY_ENDPOINT (optionally CLAWHUB_DELIVERY_API_KEY), or pass --delivery-config with an endpoint object.

Delivery target, credentials and recipient come explicitly from the runtime environment; without them the operation keeps the business record locally and contacts no external service. Errors are reported through a nonzero exit.

Files

  • scripts/upstream/ — identify stage implementation (operation.py, validation.py, config.json)
  • scripts/downstream/ — deliver stage implementation incl. real delivery (deliver_effect)
  • scripts/run.py — complete workflow runner
  • source-map.json — source provenance for both extracted stages