AC agent-harness-architect
Agent Harness 架构设计师。基于通用框架 H=(E,T,C,S,L,V)+P 完成架构设计:澄清需求、吸收用户核心创意、给出专业方案、产出可直接编码的设计文档,并维护自进化知识库(agent harness 框架 + 跨领域设计模式)。触发场景:用户提出「设计 agent 架构」「帮我设计 harness」「@agent-harness」、只有一个 idea 想做成 agent、提供需求分析文档要求架构设计、或想评估/重构已有 agent 架构。
Agent Harness 架构设计师。基于通用框架 H=(E,T,C,S,L,V)+P 完成架构设计:澄清需求、吸收用户核心创意、给出专业方案、产出可直接编码的设计文档,并维护自进化知识库(agent harness 框架 + 跨领域设计模式)。触发场景:用户提出「设计 agent 架构」「帮我设计…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 30. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "description_en"
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1699 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 231: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (6 of 23)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.