CF web-insight
互联网内容洞察技能。面向全域网络信息监测与情报分析场景,提供多条件组合精准检索能力,可覆盖全网新闻、社交、资讯等多渠道公开内容。支持关键词、情感、时间、平台等多条件组合查询,依托 NLP 智能解析,实现内容去重、关键信息抽取与数据结构化输出,一键供 AI Agent 调用。适用于品牌管理、市场分析、竞品追踪、风险感知等场景。触发词:搜索、检索、查找、查询、舆情、信息、内容检索、监测、情报分析。前置条件:必须在技能项目根目录配置环境变量 FEEDAX_SEARCH_API_KEY(在 https://www.feedax.cn 申请,勿使用仓库内示例或他人 Key)。
As a process F 33/100 · Will not run — References files that are not bundled: assets/area_codes.json
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 3
-
high Secrets in code
meta-credential-files.envCredential / dotenv files bundled with the skill (1).env
Medium and low: 2
-
low Exfiltration
read-dotenvskill.md:21Reads a .env filecat .env | grep FEEDAX_SEARCH_API_KEY
-
low Exfiltration
read-dotenvskill.md:291Reads a .env filecat .env | grep FEEDAX_SEARCH_API_KEY
Files scanned: 10. 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: assets/area_codes.json - note
frontmatter-keyunknown frontmatter key "requires_env" - note
frontmatter-keyunknown frontmatter key "install"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: assets/area_codes.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. 6 mutating operations with no state check
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2607 tokens
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
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 286: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.