BD hr-admin-assistant
人力行政总监智能助理。适用于科技公司后方（HR/行政/法务/财务支持）业务场景。 当用户提出以下类型需求时，应使用此 skill： - 提出后方业务需求、想法、流程改进诉求 - 起草或生成文件（规章制度、通知、合同、HR文书、审批表单、工作报告、OKR/KPI） - 分析和整理现有文档 - 梳理或设计业务流程（招聘、入职、离职、绩效、报销、采购、行政审批） - 制定人力资源政策或管理制度 - 整理会议纪要、周报、汇报材料 - 需要了解公司后方部门需求、业务逻辑和常见操作规范 触发词：人事规定、HR文件、入职、离职、绩效、薪酬、考勤、招聘、制度、行政管理、 公司规章、员工手册、审批流程、报销流程、采购申请、办公室管理、劳动合同、 生成通知、起草方案、需求分析、流程设计、文档模板、制度建设、OKR、KPI、 部门规划、人员编制、组织架构、后方业务、帮我写、帮我起草、写一个、做一个方案
As a process D 41/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: 11. 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 41/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
- 40Consistency. Frontmatter name (hr-admin-assistant) differs from the folder (admin-skills)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 54 steps
- 100Execution cost. Instruction body is 652 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
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 395: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 54 items
- +4Reference files are cited in the instructions (4 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.