跳到主内容
智客 ZICQ

技能库 智客分类:设计创意 dynamic-workflow-mode

Dynamic Workflow Mode

为克洛德动态工作流程模式和其他适应性代理机床设计任务局部取用,evall gates,以及可再利用的技能取用. 用于构建任务本地化的牵引,添加等离子闸门,或从特设工作中提取可再使用的技能.

3893 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

为克洛德动态工作流程模式和其他适应性剂使用设计任务-局部取用、电子闸门和再利用技能提取

何时用

* 建立任务局部控制系统,增加电子闸门,或从临时工作中提取可重复使用的技能

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Dynamic Workflow Mode、When To Activate、Core Contract、Dynamic Harness Decision Tree、Task-Local Harness Template、Dynamic Workflow Harness。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work.

Dynamic Workflow ModeWhen To ActivateCore ContractDynamic Harness Decision TreeTask-Local Harness TemplateDynamic Workflow HarnessShared Skill ExtractionControl Pane CheckpointsEval GatesAnti-PatternsOutput Standard

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
dynamic-workflow-mode
description
Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「dynamic-workflow-mode」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-2658de7b1641c6f2-%E5%8A%A8%E6%80%81%E5%B7%A5%E4%BD%9C%E6%B5%81%E7%A8%8B%E6%A8%A1%E5%BC%8F.html
请存为 .cursor/skills/dynamic-workflow-mode/SKILL.md 或 .claude/skills/dynamic-workflow-mode/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/affaan-m/ecc' --list

npx skills add 'https://github.com/affaan-m/ecc' --skill 'dynamic-workflow-mode'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: dynamic-workflow-mode description: "Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work." metadata: origin: ECC --- # Dynamic Workflow Mode Use this skill when a coding agent can generate or adapt a task-local harness instead of only following a static command flow. The goal is to turn dynamic workflow mode into a disciplined system: temporary harnesses for one-off work, shared skill extraction for repeated work, and observable control pane checkpoints for teams. ## When To Activate - The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode. - A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard. - Multiple agents need the same repeatable process but the process is not yet captured as a shared skill. - A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge. ## Core Contract Dynamic workflow mode should produce a task-local harness only when the harness is cheaper and safer than manually driving the same steps. The harness must have: - **Objective**: the outcome it owns and the outcome it explicitly does not own. - **Inputs**: files, URLs, prompts, data sources, credentials policy, and user-provided constraints. - **Outputs**: commits, reports, screenshots, status files, or control pane snapshots. - **Eval**: at least one pass/fail check tied to the task, not only "it ran". - **Handoff**: a short artifact that tells the next operator what happened, what is blocked, and how to resume. ## Dynamic Harness Decision Tree 1. **One-shot task**: keep it inline. Do not invent a harness. 2. **Repeated task with changing inputs**: create a task-local harness and keep it under a temp or project-local working area. 3. **Repeated task across teammates or repos**: extract the pattern into a shared skill. 4. **Task with external state, queueing, or approvals**: add control pane visibility before adding more automation. 5. **Task with safety risk**: add an eval gate and a human merge gate before autonomous execution. ## Task-Local Harness Template Use this structure before writing code: ```markdown # Dynamic Workflow Harness Objective: - Ship: - Do not ship: Inputs: - Repo or workspace: - External systems: - Credentials policy: Loop: 1. Discover current state. 2. Generate or update the smallest useful artifact. 3. Run eval checks. 4. Record status and handoff. 5. Stop on failed gate, unclear ownership, or unsafe external action. Eval: - Command: - Expected pass signal: - Failure owner: Handoff: - Status: - Evidence: - Next action: ``` ## Shared Skill Extraction Promote a task-local harness into a shared skill only when at least two of these are true: - The same workflow appears in multiple sessions, repos, teams, or launches. - The workflow needs specific language, tool, or safety sequencing. - Failures repeat because operators skip a gate or lose context. - The workflow has a stable input/output contract. - The workflow benefits from a control pane, status board, or team handoff. When extracting, write the skill first in `skills//SKILL.md`. Add command shims only if a legacy slash-entry surface is still required. ## Control Pane Checkpoints Dynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session: - **Plan**: objective, owner, acceptance criteria, and risky external systems. - **Queue**: work items, assigned agent role, branch/worktree, and dependency edges. - **Run**: active harness, current loop step, recent eval result, and token/cost signal if available. - **Gate**: test results, browser screenshots, security review, and merge readiness. - **Handoff**: what is done, what failed, what needs a human decision. If the repo has ECC2 state enabled, prefer adding or reading checkpoints through the ECC control pane or state-store-backed scripts instead of scattering untracked notes. ## Eval Gates Every dynamic harness needs a task-specific eval. Pick the cheapest reliable gate: | Work Type | Eval Gate | | --- | --- | | Code feature | Focused test, lint, coverage, and one integration path | | UI/control pane | Browser smoke with screenshot and overflow/error checks | | Agent workflow | Fixture transcript or seeded work item with expected routing | | Research/content | Source-neutral brief, claim checklist, and publish-ready outline | | Integration | Dry-run command, config validation, and no-secret scan | Do not claim a dynamic workflow is reusable until the eval can be rerun by another teammate. ## Anti-Patterns - Generating scripts that hide the real decision logic from the operator. - Treating dynamic workflow mode as permission to skip tests. - Creating one-off docs when a shared skill or status artifact is the real product. - Running multiple agents without ownership, merge gate, or conflict policy. - Letting raw private research data leak into public docs. ## Output Standard Finish with: - The harness or skill path. - The eval commands and results. - The control pane or handoff artifact path. - The next reusable extraction candidate.

相关技能

设计创意

Automation Workflows

设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…

设计创意

Ui Ux Pro Max

UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…

设计创意

Frontend Design

创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.

设计创意

N8n Workflow Automation

设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.