BD web-search-plus
Unified multi-provider web search and URL extraction skill with intelligent auto-routing across Serper, Brave, Tavily, Querit, Linkup, Exa, Firecrawl, Perplexity, You.com, SearXNG, SerpBase, and Keenable. Unified freshness/news filters, locale-aware defaults, spam/mirror filtering, and adaptive routing. Sends queries/URLs to the configured third-party provider APIs and caches results plus provider failure/performance history locally under .cache (configurable, can be disabled).
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
read-dotenvFAQ.md:98Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvREADME.md:89Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvSKILL.md:67Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvtest-auto-routing.sh:8Reads a .env file (test fixture / example file)source .env
fixture -
low Exfiltration
read-dotenvtest-auto-routing.sh:13Reads a .env file (test fixture / example file; quoted — discussed, not commanded)echo "Error: SERPER_API_KEY not set. Copy .env.example to .env and add your keys."
fixturequoted
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Flow map in block collection must be sufficiently indented and end with a } at line 5, column 1653: …health.json, and provider_stats.json (adaptive routing performance samples)"}}} ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 62 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3274 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +3Output format is not stated: the model decides each time
- -37 of 10 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 482: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 62 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.