SKILLEMALL.ai
RU Sign in

BC Hidden Business Opportunity Detector Skill

This skill builds an automated business intelligence engine that: 1. Apify scrapes App Store reviews, Amazon reviews, Reddit, niche forums, and Product Hunt 2. Claude (OpenClaw) deep-analyzes the r...

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 5 788 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill builds an automated business intelligence engine that: 1.

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

AnalyzerNotionAI and agentstype 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
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
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.

Exfiltration 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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

✓ No critical or high findings

Medium and low: 1
  • medium Exfiltration exfil-webhook-url SKILL.md:667
    Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation of a security skill)
    SLACK_WEBHOOK_URL=https://hooks.slack.com/services/xxx/xxx/xxx
    security skill

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5788 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 60/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Hidden Business Opportunity Detector Skill) differs from the folder (business-opportunity-detector)
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5788 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Running it twice. No mutating operations
  • 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (19 code blocks)

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