BD dating
Pre-date research assistant — scan someone's public social media profiles to understand their interests, personality, lifestyle and values before meeting them. Generates a "Dating Prep Report" with interest mapping, personality insights, conversation topics, restaurant suggestions, and things to watch out for. 约会/相亲前的功课助手——扫描对方的公开社交主页，了解 TA 的兴趣、性格、生活方式和价值观。生成一份「约会准备报告」：兴趣图谱、性格洞察、聊天话题建议、餐厅推荐、注意事项。带着准备去赴约。
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: 5. 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 "depends"
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 (dating) differs from the folder (dating-prep)
- 100Tools and files. No external tools needed
- 100Steps. 60 steps
- 100Execution cost. Instruction body is 1822 tokens
- 100Running it twice. No mutating operations
- low 12 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
- +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
- -241 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 407: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (11 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.