BF global-invoicing-research
生成全球开票系统的国家调研报告,输出结构化的 .docx 文档,同时服务产品经理、研发、售前三类角色。 当用户提到以下任意场景时,务必使用本 Skill: - "调研 XX 国家的开票/发票/电子发票要求" - "我要做全球开票系统,帮我调研某个国家" - "帮我生成 XX 国家的开票调研报告" - "开票合规调研"、"e-invoicing research"、"VAT invoice research" - 用户提到 KSeF、Peppol、CFDI、NF-e、GST 等具体的国家电子发票标准 即使用户没有明确说"生成报告",只要涉及对某个国家的开票要求进行结构化调研,就应使用本 Skill。
As a process F 35/100 · Will not run — References files that are not bundled: references/docx-template-structure.md, references/docx-coding-rules.md
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: 2. 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/docx-template-structure.md - warning
missing-refreference to a missing file: references/docx-coding-rules.md
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: references/docx-template-structure.md, references/docx-coding-rules.md
- 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
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 818 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
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 302: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.