CD recruitment-agent
招聘Agent：通过 opencli(Boss直聘) + lark-cli(飞书多维表格) 管理招聘流程。支持：(1) 查看Boss直聘最近/未读消息; (2) 将候选人存入人才库（先搜索比对，再新建/更新）; (3) 添加人才决策记录（加入库/约面试/跟进/发Offer/归档）; (4) 更新人才库中某候选人的指定信息; (5) 约面试（发邀约消息、心跳检测、确认时间、创建飞书日程）。当用户说「查boss消息」「把XXX存入人才库」「我对XXX感兴趣」「对XXX做个决策记录」「更新XXX的信息/字段」「帮我给XXX约个面试」「约一下XXX」时触发。
招聘Agent：通过 opencli(Boss直聘) + lark-cli(飞书多维表格) 管理招聘流程。支持：(1) 查看Boss直聘最近/未读消息; (2) 将候选人存入人才库（先搜索比对，再新建/更新）; (3) 添加人才决策记录（加入库/约面试/跟进/发Offer/归档）; (4)…
As a process D 43/100 · Unfinished process — 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: 9. 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")
Process rating: all ten parameters 43/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
- 30Running it twice. 2 mutating operations with no state check
- 50Steps. 2 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 356 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 278: enough signal without eating the budget
- +4Structure: 7 headings
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.