AC jd-market-research
当用户提供岗位JD（职位描述）或明确指定岗位名称时，自动联网深度调研该岗位在市场上的 人才供需、薪资分布、职级体系、组织架构，并对比主要目标公司的事业线稳定性、业务前景、 团队氛围、工作强度与薪酬竞争力，识别风险点与核心优势。 适用场景：职业规划、求职决策、面试准备、offer比较、行业分析、招聘策略制定。 触发条件：（1）用户直接粘贴JD文本要求分析；（2）用户要求调研/分析某个岗位的市场情况； （3）用户想了解某岗位在不同公司的差异；（4）用户要求对比多个公司的同一岗位； （5）用户询问某岗位的薪资、前景、团队氛围等市场信息。
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: 4. 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 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. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 966 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
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.