BC mc-monthly-visitor-report
用 ideamake-cli 拉取营销云数据，端到端生成案场月度到访客户全量分析 HTML+PDF 报告。 触发："用 ideamake-cli 生成月度报告"、"/mc-monthly-visitor-report"、"分析某项目X月到访"。 适用：新房案场月度汇报、营销总决策、团队复盘。
用 ideamake-cli 拉取营销云数据，端到端生成案场月度到访客户全量分析 HTML+PDF 报告。 触发："用 ideamake-cli 生成月度报告"、"/mc-monthly-visitor-report"、"分析某项目X月到访"。 适用：新房案场月度汇报、营销总决策、团队复盘。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash Glob Grep Agent WebFetch
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") - note
frontmatter-keyunknown frontmatter key "intent" - note
frontmatter-keyunknown frontmatter key "type"
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. 66 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1211 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 3 example trigger phrases
- +3Description length 146: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 66 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.