BF industry-information
行业资讯与舆情监测技能。基于 FEEDAX API 查询特定行业的新闻资讯和舆情动态,支持证监会行业和申万行业分类体系,提供情感分析、行业正负面评估、资讯热度分析等多维度数据。 使用场景:用户研究行业趋势、分析行业舆情、进行行业对比、评估行业投资风险、了解政策对行业影响、追踪行业热点事件、进行行业配置研究等。 触发示例:"房地产行业最近怎么样"、"查询人工智能行业动态"、"新能源行业负面新闻"、"半导体行业趋势"、"医药行业舆情分析"、"对比房地产和基建行业"、"查看金融行业正面报道"等。 支持按关键词查询,按证监会/申万行业分类筛选,按情感倾向过滤,返回行业正负面分析、资讯热度、行业标签等多维度数据。
As a process F 33/100 · Will not run — References files that are not bundled: scripts/config.json
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.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvSKILL.md:26Reads a .env filecat .env
-
low Exfiltration
read-dotenvSKILL.md:579Reads a .env filecat .env | grep FEEDAX_API_KEY
Files scanned: 5. 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") - warning
missing-refreference to a missing file: scripts/config.json
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: scripts/config.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. 10 mutating operations with no state check
- 100Steps. 63 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2767 tokens
- low 15 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
- +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 7 example trigger phrases
- +3Description length 308: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (14 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.