BF TrendScope
舆情趋势洞察技能。根据用户需求自动生成专业的舆情分析报告,包含情感分布、地域分布、关键词分析、媒体分布、时间趋势等多维度分析。触发词:舆情、报告、生成报告、舆情报告、分析报告、品牌分析、市场分析、竞品分析、趋势分析。
As a process F 26/100 · Will not run — References files that are not bundled: references/domains.json, references/scenes.json, references/media_names.json
IntegrationSoftware developmentData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
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.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvREADME.md:35Reads a .env filecp .env.example .env
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/domains.json - warning
missing-refreference to a missing file: references/scenes.json - warning
missing-refreference to a missing file: references/media_names.json - warning
missing-refreference to a missing file: references/aggregation_types.json - warning
missing-refreference to a missing file: assets/area_codes.json
Process rating: all ten parameters 26/100
Will not run. References files that are not bundled: references/domains.json, references/scenes.json, references/media_names.json
- 0Tools and files. 5 referenced file(s) missing: references/domains.json, references/scenes.json, references/media_names.json
- 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
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (TrendScope) differs from the folder (trend-scope-report)
- 70Execution cost. Instruction body is 4121 tokens
- 100Steps. 45 steps
- low 11 top-level sections: this looks like several domains in one skill
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)
- +3Description length 108: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 49 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (9 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.
External checks
ClawHub: suspicious
The skill mostly matches its report-generation purpose, but it uses API credentials and report queries with a fixed non-HTTPS IP endpoint and an undeclared fallback API key.
LLM: suspicious (high) · VirusTotal: · 29 May 2026