BF itsm-ticket-analyzer
嘉为蓝鲸 ITSM 工单分析技能。支持多流程工单数据读取、字段智能映射、新工单处理建议、趋势分析、高频问题识别、SLA 监控。Use when: 需要分析 ITSM 工单数据、为新工单提供处理建议、生成工单日报/周报、识别高频问题、监控 SLA 超时风险。支持不同流程的工单（字段自动适配）。
As a process F 35/100 · Will not run — References files that are not bundled: references/config.json, references/blueking-api.md, references/ticket-classification.md
AnalyzerCustomer supportInfrastructuretype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: 嘉为蓝鲸 ITSM 工单分析技能。支持多流程工单数据读取、字段智能映射、新工单处理建议、趋势分析、高频问题识别、SLA 监控。Use… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: references/config.json - warning
missing-refreference to a missing file: references/blueking-api.md - warning
missing-refreference to a missing file: references/ticket-classification.md - warning
missing-refreference to a missing file: references/sla-policy.md - warning
missing-refreference to a missing file: references/webhook-config.md
Process rating: all ten parameters 35/100
Will not run. References files that are not bundled: references/config.json, references/blueking-api.md, references/ticket-classification.md
- 0Tools and files. 5 referenced file(s) missing: references/config.json, references/blueking-api.md, references/ticket-classification.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. 46 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1140 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
- +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
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (16 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.
External checks
ClawHub: clean
This skill is a local ITSM ticket analysis helper, but users should treat ticket exports and generated reports as sensitive.
LLM: benign (high) · VirusTotal: · 29 May 2026