360 Secure SkillHub
360 安全技能中心

Service Capacity Window Planner

读取 capacity_request，计算 capacity_window 并生成 capacity_ledger_entry 本地台账；配置 SMTP 或 HTTP 目标后执行投递并返回回执，默认不联系外部服务。包含 Python 运行脚本与示例，但 lint 提示 upstream/downstream 引用缺失。

wxt-ai
wxt-ai
热度 7.65
最近更新 2026-10-07 19:25:05
分类：自动化依赖：代码执行 / 读写文件 / 第三方 API应用场景：日程安排 / 工作流 / 数据处理 / 报告撰写

安装技能

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

执行命令安装此 skill： npx secure-skills-cli add service-capacity-window-complete
Metadata
name
Service Capacity Window Planner
description
Select a service capacity window. Then it executes the downstream business step: Record a capacity-window entry. 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 Capacity Window 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 (capacity_request) and computes the identification result (capacity_window).
  2. Deliver — feeds the identification result into the downstream operation, computes the business result (capacity_ledger_entry), and creates or updates a local business artifact beneath the explicitly supplied --output-dir. Effect: capacity_window_ledger.
  3. Real delivery — when a delivery target is configured, performs the declared business action (capacity_window_ledger) 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