嘉为蓝鲸 ITSM 工单数据分析技能，支持处理人工作量统计、响应时间分析、问题分类统计、日报/周报生成。
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a local ITSM ticket analysis skill, with the main cautions being optional API/webhook/cron configuration and some documented helper scripts that are not included.
Safe to consider for local ITSM ticket analysis, but treat ticket exports and reports as sensitive, verify any missing helper scripts before using them, and only enable API keys, webhooks, or cron scheduling with approved scope and recipients.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If configured, the API key could grant access to ITSM ticket data beyond the local CSV/Excel workflow.
The documentation mentions an optional ITSM API key even though registry metadata declares no required credentials; this is coherent for an ITSM integration but users should scope and protect the key.
export BK_ITSM_API_URL="https://<your-domain>/api/v1/itsm" export BK_ITSM_API_KEY="your-api-key"
Use a least-privilege API key, avoid pasting secrets into prompts, and only enable API access if the included workflow actually needs it.
Ticket summaries may include internal incidents, employee names, or operational details and could be posted to a chat channel if the webhook is used.
The skill documents an optional Enterprise WeChat webhook for pushing reports, which is purpose-aligned but creates an external data-sharing channel for ticket reports.
export WEBHOOK_URL="https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxx"
Only configure approved webhooks, confirm the recipient channel, and redact sensitive ticket details before automated sharing.
A user or agent may expect functionality that is not present and might be tempted to fetch unreviewed replacement scripts.
The documentation references helper scripts for clustering and SLA monitoring that are not included in the provided file manifest, so those documented features would require separately sourced code.
python scripts/cluster_issues.py --input /path/to/tickets.csv --threshold 0.8 ... python scripts/sla_monitor.py --input /path/to/tickets.csv --warning-hours 4
Use only the included scripts unless additional helpers are obtained from a trusted, reviewed source.
If a schedule is manually created, reports may continue to be generated or shared after the initial task.
The documentation suggests optional scheduled report pushing; no artifact shows automatic cron installation, but configuring it would make the workflow persistent.
# 每天早上 9 点推送昨天的工单日报 cron: 0 9 * * *
Create scheduled jobs only intentionally, document where they are configured, and remove them when daily pushes are no longer needed.