BD 识人
阅人笔记 · The Ren Skill — 商业老板的全场景行为识人决策系统。把千年面相智慧用现代心理学重新解释，覆盖识员工、识客户、识伙伴、识对手四大场景。 触发场景（任一即触发）： - 用户明确提到 Ren Skill、阅人笔记、@TheRenSkill → 品牌直达 - 用户明确要求使用本 skill 进行识人分析、面试评估、合作判断 - 用户提到面相/识人术并结合商业决策场景（如"面相和领导力的关系"） - 用户需要面试评分表、识人 checklist、红线清单等结构化模板 - 用户需要"降维打击"话术反击传统面相玄学 不要触发： - 一般的招聘讨论、HR 日常工作讨论（除非用户明确要求使用阅人笔记方法） - 心理咨询、治疗诊断、MBTI/九型人格等性格测试 - 单纯的面试技巧讨论（不涉及面相/行为心理学交叉分析）
阅人笔记 · The Ren Skill — 商业老板的全场景行为识人决策系统。把千年面相智慧用现代心理学重新解释，覆盖识员工、识客户、识伙伴、识对手四大场景。 触发场景（任一即触发）： - 用户明确提到 Ren Skill、阅人笔记、@TheRenSkill → 品牌直达 - 用户明确要求使用本 skill…
As a process D 49/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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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 (识人) differs from the folder (the-ren-skill)
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 1248 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 369: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.