BF crm-sync-assistant
CRM线索同步助手。当员工要求同步线索到CRM系统时触发，或查询已同步/未同步的项目、项目管理、拜访记录时触发。核心职责：查询沉淀的拜访分析数据 → AI整理结构化线索 → 用户确认 → 同步至CRM。Invoke when user says '同步CRM'、'录入CRM'、'查看未同步'、'已同步的项目'、'项目管理'、'查看拜访记录' or similar.
CRM线索同步助手。当员工要求同步线索到CRM系统时触发，或查询已同步/未同步的项目、项目管理、拜访记录时触发。核心职责：查询沉淀的拜访分析数据 → AI整理结构化线索 → 用户确认 → 同步至CRM。Invoke when user says…
As a process F 34/100 · Will not run — References files that are not bundled: ${visit_board_url}, ${kanban_url}, url
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7041 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ${visit_board_url} - warning
missing-refreference to a missing file: ${kanban_url} - warning
missing-refreference to a missing file: url - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 34/100
- 0Tools and files. 3 referenced file(s) missing: ${visit_board_url}, ${kanban_url}, url
- 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
- 70Execution cost. Instruction body is 7041 tokens
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 13 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
- +1No license
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 52 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (36 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.