agent-harness-construction
- Repo stars 188,749
- Author updated Live
- Author repo ECC
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @affaan-m · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: agent-harness-construction
description: 当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。 runs entirely locally. Works with Claude Code, Curso…
category: documentation
runtime: no special runtime
---
# agent-harness-construction output preview
## PART A: Task fit
- Use case: 当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “核心模型 / 行动空间设计 / 粒度规则” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心模型 / 行动空间设计 / 粒度规则” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “核心模型 / 行动空间设计 / 粒度规则”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-harness-construction
description: 当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。 runs entirely locally. Works with Claude Code, Curso…
category: documentation
source: affaan-m/ECC
---
# agent-harness-construction
## When to use
- 当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。 1. 行动空间质量 2. 观察质量 3. 恢复质量 4. 上下文预算质量 1. 使用稳定、明确的工具名称。 2. 保持输入模式优先且范围狭窄。 3.…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “核心模型 / 行动空间设计 / 粒度规则” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-harness-construction" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 核心模型 / 行动空间设计 / 粒度规则
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 智能体框架构建
当你在改进智能体的规划、调用工具、从错误中恢复以及收敛到完成状态的方式时,使用此技能。
核心模型
智能体输出质量受限于:
- 行动空间质量
- 观察质量
- 恢复质量
- 上下文预算质量
行动空间设计
- 使用稳定、明确的工具名称。
- 保持输入模式优先且范围狭窄。
- 返回确定性的输出形状。
- 除非无法隔离,否则避免使用全能型工具。
粒度规则
- 对高风险操作(部署、迁移、权限)使用微工具。
- 对常见的编辑/读取/搜索循环使用中等工具。
- 仅当往返开销是主要成本时使用宏工具。
观察设计
每个工具响应都应包括:
status: success|warning|errorsummary: 一行结果next_actions: 可执行的后续步骤artifacts: 文件路径 / ID
错误恢复契约
对于每个错误路径,应包括:
- 根本原因提示
- 安全重试指令
- 明确的停止条件
上下文预算管理
- 保持系统提示词最少且不变。
- 将大量指导信息移至按需加载的技能中。
- 优先引用文件,而不是内联长文档。
- 在阶段边界处进行压缩,而不是任意的令牌阈值。
架构模式指导
- ReAct:最适合路径不确定的探索性任务。
- 函数调用:最适合结构化的确定性流程。
- 混合模式(推荐):ReAct 规划 + 类型化工具执行。
基准测试
跟踪:
- 完成率
- 每项任务的重试次数
- pass@1 和 pass@3
- 每个成功任务的成本
反模式
- 太多语义重叠的工具。
- 不透明的工具输出,没有恢复提示。
- 仅输出错误而没有后续步骤。
- 上下文过载,包含不相关的引用。
Decide Fit First
Design Intent
How To Use It
Boundaries And Review