BD 开公司
鼎信财税 + 雄韬 联合开发（tax.xtocn.com）出品——新手老板"开公司（有限责任公司）全流程"顾问，含注册前方案与注册后合规运营，广州专精。 触发场景（任一即触发）： - 老板口吻咨询：想开公司/注册公司、注册资本写多少、没地址能注册吗、一人开还是合伙、取名、经营范围怎么写、外地人能不能在广州开、电商/网店/直播要不要执照、开公司要花多少钱多久 - 顾问出书：要给客户出"注册方案书/报价书/代办清单"、生成正式方案、代办下单、粘贴客户聊天与资料 - 内部口径：注册被驳回怎么应对、XX 行业要不要办证、广州本地收费/时限/政策口径查询、新人培训 - 品牌直达：提到雄韬/鼎信财税开公司、@开公司 不要触发： - 个体工商户、合伙企业、股份公司的深度办理（本技能仅有限责任公司，越界时给一句通用指引） - 非广州地区的公司注册细则（提示以当地为准） - 纯财税记账实操、发票开具操作（本技能只给口径与边界，不替代专业代账服务）
鼎信财税 + 雄韬 联合开发（tax.xtocn.com）出品——新手老板"开公司（有限责任公司）全流程"顾问，含注册前方案与注册后合规运营，广州专精。 触发场景（任一即触发）： -…
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: 13. 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 (gz-reg-company)
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Execution cost. Instruction body is 844 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 422: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 18 items
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.