BF agent-interaction
Agent 交互链路 skill。基于 One Click 的"三步确认链路"(自然语言→填表高亮→确认提交)+ 隐式校验层,设计 Agent 的完整交互流程。触发场景:用户说"交互设计"、"Agent 流程"、"Copilot 交互"、或 workflow-start 路由到此 skill。
Agent 交互链路 skill。基于 One Click 的"三步确认链路"(自然语言→填表高亮→确认提交)+ 隐式校验层,设计 Agent 的完整交互流程。触发场景:用户说"交互设计"、"Agent 流程"、"Copilot 交互"、或 workflow-start 路由到此 skill。
As a process F 31/100 · Will not run — References files that are not bundled: ../../lessons/by-role/agent.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 0. 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") - warning
missing-refreference to a missing file: ../../lessons/by-role/agent.md
Process rating: all ten parameters 31/100
- 0Tools and files. 1 referenced file(s) missing: ../../lessons/by-role/agent.md
- 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
- 40Consistency. Frontmatter name (agent-interaction) differs from the folder (workflow-dlc-agent-interaction)
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 1124 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 147: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.