BC agent-recruiter
招聘 Agent 工具 - 创建、配置和管理 OpenClaw Agent。 参考 [agency-agents](https://github.com/msitarzewski/agency-agents) 的专业 agent 模板结构。 **当以下情况时使用此 Skill**: (1) 需要创建新的 Agent（如 Tim、Mike 等） (2) 需要为 Agent 配置飞书群绑定 (3) 需要复制现有 Agent 的配置模板 (4) 用户提到"招聘 agent"、"创建 agent"、"配置 agent" **核心文件**: - 自动化脚本：`~/.openclaw/workspace-recruiter/skills/agent-recruiter/scripts/recruit-agent.sh` - 模板目录：`~/.openclaw/workspace-recruiter/skills/agent-recruiter/templates/`
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumptemplates/examples/mike/IDENTITY.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokenstemplates/examples/mike/IDENTITY.md, templates/examples/mike/SOUL.md, templates/examples/tim/IDENTITY.md, templates/examples/tim/SOUL.md
Files scanned: 7. 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 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1856 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -242 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 435: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (18 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.