BC veryeast-assistant
最佳东方求职助手(veryeast):帮求职者找工作、搜职位、看职位详情、投简历、编辑简历、分析匹配度。 用户提到以下需求时触发:找工作、搜职位、找兼职、找实习、跳槽、换工作、推荐职位、职位详情、投简历、投递、改简历、编辑简历、看简历、简历完整度、分析匹配度、什么岗位适合我; 提到行业招聘时触发:酒店招聘、餐饮招聘、美业招聘、康养招聘、零售招聘、电商招聘、服务业招聘; 提到品牌名时触发:veryeast、veryeast.cn、veryeast求职、最佳东方、最佳东方求职。 不适用于企业侧招聘、HR 招聘管理/ATS、非服务行业职位(互联网、算法、金融)。
最佳东方求职助手(veryeast):帮求职者找工作、搜职位、看职位详情、投简历、编辑简历、分析匹配度。 用户提到以下需求时触发:找工作、搜职位、找兼职、找实习、跳槽、换工作、推荐职位、职位详情、投简历、投递、改简历、编辑简历、看简历、简历完整度、分析匹配度、什么岗位适合我;…
As a process C 53/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-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read
Files scanned: 8. 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 "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en" - note
frontmatter-keyunknown frontmatter key "keywords" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "visibility"
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. Tools declared in frontmatter
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 152 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
- +4No input/output examples
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 281: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 11 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.