BC analytics-dashboard
数据看板查询Skill，通过dashboard-mcp获取实时统计/系统健康/租户概览/内容队列/事件订阅等看板数据。触发:数据看板/实时统计/系统健康/租户概览/内容队列/事件订阅/早朝简报/Agent状态 不触发:内容发布/商品管理/Cookie管理
数据看板查询Skill，通过dashboard-mcp获取实时统计/系统健康/租户概览/内容队列/事件订阅等看板数据。触发:数据看板/实时统计/系统健康/租户概览/内容队列/事件订阅/早朝简报/Agent状态 不触发:内容发布/商品管理/Cookie管理
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureDockerData and analyticsAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 1. 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") - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 53/100
- 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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 991 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
- +1No license
- +2Single-language instructions
- +3Description length 127: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: clean
This is a read-only dashboard skill whose stated MCP access matches its purpose, with some documentation gaps users should notice.
LLM: benign (high) · VirusTotal: · 15 Aug 2026