Agent Skills › DotHarness/dotcraft › workflow-authoring

workflow-authoring

GitHub

用于编写、编辑、审查和调试 DotCraft Dynamic Workflow JavaScript 脚本。涵盖从创建、修改到诊断运行时契约失败的完整工作流开发流程，强调遵循特定规范和 API。

src/DotCraft.Core/Skills/BuiltIn/workflow-authoring/SKILL.md DotHarness/dotcraft

Trigger Scenarios

创建或修改工作流脚本检查工作流正确性诊断工作流作者身份或运行时契约失败

Install

npx skills add DotHarness/dotcraft --skill workflow-authoring -g -y

More Options

Non-standard path

npx skills add https://github.com/DotHarness/dotcraft/tree/main/src/DotCraft.Core/Skills/BuiltIn/workflow-authoring -g -y

Use without installing

npx skills use DotHarness/dotcraft@workflow-authoring

指定 Agent (Claude Code)

npx skills add DotHarness/dotcraft --skill workflow-authoring -a claude-code -g -y

安装 repo 全部 skill

npx skills add DotHarness/dotcraft --all -g -y

预览 repo 内 skill

npx skills add DotHarness/dotcraft --list

SKILL.md

Frontmatter

{
    "name": "workflow-authoring",
    "description": "Write, edit, review, or debug DotCraft Dynamic Workflow JavaScript. Use when creating or changing an inline or saved Workflow script, checking it for correctness, or diagnosing authoring and runtime-contract failures; do not use merely to run an existing saved Workflow unchanged."
}

Workflow Authoring

Use DotCraft's current Workflow contract as the authority. Do not copy APIs or metadata shapes from other workflow runtimes.

Read the matching reference

For every script-writing or editing task, read references/runtime.md first.
For topology selection or a new orchestration design, also read references/patterns.md.
For review, diagnosis, repair, or resume-sensitive edits, also read references/review-debug.md.

Preserve these invariants

Start with a literal export const meta and explicitly return plain JSON data.
Keep enumeration, identity, ordering, deduplication, bounds, and failure accounting in JavaScript; delegate semantic work to Agents.
Give every intended Agent operation a stable, unique label and preserve its work ID before filtering results.
Treat null as missing coverage, not as a negative finding or successful check.
Bound fan-out and loops to the task. Do not invent token or time limits the user did not request.
Use only APIs documented by this skill and names supplied by the current DotCraft context.