BF conspect
全自动多源数据智能分析与商务报表渲染工具。上传Excel数据源,AI自动完成数据解析、图表选型、商务排版、可视化渲染,输出可直接开会投屏的专业报表。v3.1 全流程托管AI自动生成,零用户确认环节,端到端稳定丝滑。适用场景:生成报表/数据看板/Excel出图/投屏数据/多表合并分析。不适用:简单数据整理/桌面BI工具/纯文本报告。
全自动多源数据智能分析与商务报表渲染工具。上传Excel数据源,AI自动完成数据解析、图表选型、商务排版、可视化渲染,输出可直接开会投屏的专业报表。v3.1…
As a process F 34/100 · Will not run — References files that are not bundled: references/output-spec, references/trigger-guide, references/examples
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 46. 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") - warning
missing-refreference to a missing file: references/output-spec - warning
missing-refreference to a missing file: references/trigger-guide - warning
missing-refreference to a missing file: references/examples - warning
missing-refreference to a missing file: references/quality-audit - warning
missing-refreference to a missing file: references/ai-reviewer - warning
missing-refreference to a missing file: references/cli-ai-workflow - warning
missing-refreference to a missing file: references/agent-communication - warning
missing-refreference to a missing file: references/chart-selection - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "language"
Process rating: all ten parameters 34/100
- 0Tools and files. 8 referenced file(s) missing: references/output-spec, references/trigger-guide, references/examples
- 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 4391 tokens
- 100Steps. 85 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 14 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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 166: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 85 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (8 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.