SKILLEMALL.ai
GitHub ↗ RU Sign in

BC vibe-prospecting

Use this skill when the user wants to find companies (businesses) or people (contacts/prospects/leads) using the AgentSource B2B database. Trigger keywords include: find companies, find leads, find prospects, find contacts, B2B search, sales prospecting, market research, export to CSV, company events, funding signals, hiring signals, buying intent, intent signals, who is hiring, companies using [technology], decision makers at, CTO/CMO/VP of, enrich companies, enrich contacts, company firmographics, technographics, tech stack, Series A/B/C companies, target list. Requires: EXPLORIUM_API_KEY (env var or ~/.agentsource/config.json).

modbender/skill-library-mcp Agent Skills author: modbender MIT 8 files · 1 script body ≈ 3 871 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Trigger keywords include: find companies, find leads, find prospects, find contacts, B2B search, sales prospecting, market research, export to CSV, company…

As a process C 62/100 · Has gaps — weak spots: result and completion, consistency, running it twice

ProcedureSalesforceNotionHubSpotSales and CRMData and analyticstype 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
89/100
safety, quality, tests
Safety 60%
90
Quality 40%
88
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Running it twice w 4
30
Consistency w 8
40
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.

Dangerous commands 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 skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • medium Dangerous commands cmd-shell-rc setup.sh:88
      Writes to a shell startup file
      echo "To also set it as an environment variable, add this to ~/.zshrc or ~/.bashrc:"
    • medium Dangerous commands cmd-shell-rc setup.sh:123
      Writes to a shell startup file
      echo "  echo 'export PATH=\"\$HOME/.agentsource/bin:\$PATH\"' >> ~/.zshrc"

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Result and completion. Does not say what the result is
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (vibe-prospecting) differs from the folder (explorium-agentsource)
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 33 steps, 3 vague phrases
    • 100Failures and branches. 3 branches, has a failure section
    • 100Execution cost. Instruction body is 3871 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 638: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 33 items
    • +4Has examples (24 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

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