BC power-search
Self-hosted research tool combining Brave Search API + Browserless content fetching. Search the web with optional full-page content extraction and HTML parsing.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:54High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:122High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:163High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Eg5+wW0/QaZM…swK/w2MWU+Gw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:207High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uff+RtWa…OPA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:219High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CUH+OiuIgU++RB0+94Nl…dMw==",
detector
Files scanned: 12. 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") - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 57/100
- 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. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1157 tokens
- low 14 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)
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 24 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +3All 5 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: clean
Power Search is a coherent web-search skill, but users should understand that searches leave the host and Browserless can make server-side page fetches.
LLM: benign (high) · VirusTotal: · 29 May 2026