BF spider-web
蜘蛛网智能技能路由系统。自动扫描所有已安装技能的触发词，构建统一的触发词数据库， 实现串/并联匹配引擎，将用户自然语言查询智能路由到对应技能。 支持精确匹配、中文语义匹配、AND/OR逻辑组合、模糊匹配和交互式Web管理面板。 触发词：蜘蛛网系统, 触发词匹配, 技能路由, 智能匹配, 技能调度, 触发词网络, spider web, skill router, trigger match, 串并联匹配, 触发词数据库, 技能触发词映射, 查技能匹配, 这个触发哪个技能, 哪个技能可以处理, match skill, 技能推荐, 我应该用哪个技能, route to skill, 触发词管理
蜘蛛网智能技能路由系统。自动扫描所有已安装技能的触发词，构建统一的触发词数据库， 实现串/并联匹配引擎，将用户自然语言查询智能路由到对应技能。 支持精确匹配、中文语义匹配、AND/OR逻辑组合、模糊匹配和交互式Web管理面板。 触发词：蜘蛛网系统, 触发词匹配, 技能路由, 智能匹配, 技能调度, 触发词网络…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/trigger_db.json
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
- 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 · 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 Skill TaskCreate TaskUpdate TaskList TaskGet AskUserQuestion
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/trigger_db.json - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/trigger_db.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
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 825 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 299: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.