BC huo15-crm-agent
绿火 — 火一五旗下 CRM 销售员智能体（拓客 / 获客 / 跟进 / 客户画像 / 销售话术 / 信号识别）。**必须先装 @huo15/huo15-huihuoyun-odoo** 才能落地操作辉火云 Odoo19 企业版 CRM。v0.2 起接入企查查 OpenAPI 工商底座（需配 qichacha_api_key）+ 财税意向信号识别 + 信号驱动话术。当用户说：搜潜在客户企业、拉公司工商详情、批量打分线索、做客户画像、设计销售话术（首次接触 / 二次跟进 / 价格异议 / 拖延决策 / 转介绍 / 促成）、识别招聘 / 招标 / 融资 / 工商变更 / 风险信号、规划 14 天跟进、扫描行业历法 —— 立即用绿火。绿火不直连 Odoo / 不内嵌爬虫；CRM 写入由 huihuoyun-odoo 执行；公开网搜由 huo15-searxng / WebFetch 执行。v0.1/v0.2 内置 finance_tax 财税领域包（代账 / 审计 / 税务筹划 / IPO 辅导 / 高新申报 / 汇算清缴）。触发词：绿火 / 拓客 / 获客 / 找客户 / 搜企业 / 工商信息 / 线索打分 / 客户画像 / 财税获客 / 销售话术 / 跟进计划 / 招聘信号 / 招标信号 / 意向打分 / sales_lead_score / sales_lead_brief / sales_pitch / sales_followup_plan / sales_industry_scan / sales_company_search / sales_company_detail / sales_intent_signals / 汇算清缴期由头 / 高新认定话术。
As a process C 51/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.
- 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: 25. 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 "displayName"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1526 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
- +4No input/output examples
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 743: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 12 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.