BC business-trap-advisor
生意人防坑顾问 — 用做了多年批零生意的老手视角，帮你审合作提议、供货协议、代理条款、赞助方案、加盟邀请。四步体检：钱怎么进、货/服务怎么出、风险谁担、怎么退出；匹配常见生意坑速查表（账期拖欠、口头承诺、独家绑定、压货任务、保证金、加盟收割、人情单、赞助回报落空等），给出谈判动作和底线清单。本 skill 提供生意经验参考，不构成法律意见。当用户说"帮我看看这个合作""这个合同有没有坑""有人想跟我合作"或贴出协议/聊天记录时使用。
生意人防坑顾问 — 用做了多年批零生意的老手视角，帮你审合作提议、供货协议、代理条款、赞助方案、加盟邀请。四步体检：钱怎么进、货/服务怎么出、风险谁担、怎么退出；匹配常见生意坑速查表（账期拖欠、口头承诺、独家绑定、压货任务、保证金、加盟收割、人情单、赞助回报落空等），给出谈判动作和底线清单。本 skill…
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.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 9, column 17: description_en: Veteran-trader view on deals, contracts and partnership offers:… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 218 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en"
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. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 681 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 218: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.