SKILLEMALL.ai
GitHub ↗ RU Sign in

BC search-intelligence-skill

Advanced AI-powered search skill using SearXNG as the universal search backend. Multi-engine dork generation, 90+ search engines, intelligent search strategies, intent parsing, result analysis, and adaptive query refinement. No API keys required.

modbender/skill-library-mcp Agent Skills author: modbender MIT 14 files body ≈ 9 953 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Advanced AI-powered search skill using SearXNG as the universal search backend.

As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubDockerWriting and documentsSoftware developmentSecuritytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
77/100
safety, quality, tests
Safety 60%
89
Quality 40%
60
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

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.

For the author

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

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • medium Secrets in code secret-private-key search_dorks_skill/config.py:416
    Private key material (key header without key body; quoted — discussed, not commanded)
    'site:{domain} "-----BEGIN PRIVATE KEY----- …
    header onlyquoted
  • medium Secrets in code secret-private-key search_dorks_skill/config.py:417
    Private key material (key header without key body; quoted — discussed, not commanded)
    'site:{domain} "-----BEGIN PRIVATE KEY----- …
    header onlyquoted
  • low Risky intent intent-offensive-security SKILL.md:765
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    IntentCategory.SECURITY   # Vulnerabilities, exposed files, pentesting

Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 9953 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 52/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. 1 mutating operations with no state check
  • 40Execution cost. Instruction body is 9953 tokens: crowds the task out of the window
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • low 13 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
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 246: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (63 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.