SKILLEMALL.ai

BC Lead Radar

Every morning, scans Reddit, Hacker News, Indie Hackers, Stack Overflow, Quora, Hashnode, Dev.to, GitHub, and Lobsters for people actively asking for what you sell. Delivers the top 10 buying-intent leads to your Telegram with a pre-drafted reply. Powered by Gemini 2.5 Flash.

ClawHub Hermes author: snoow v1.3.5 20 files body ≈ 1 519 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

GeneratorTelegramGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
77/100
safety, quality, tests
Safety 60%
93
Quality 40%
54
Run on models
none yet
Process rating
C
56/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

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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 7

✓ No critical or high findings

Medium and low: 7
  • low Exfiltration exfil-secret-in-url lib/intentScorer.js:73
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    `https://generativelanguage.googleapis.com/v1beta/models/gemi…ent?key=…
    placeholder
  • low Exfiltration exfil-webhook-url lib/telegram.js:41
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    `https://api.telegram.org/bot${token}/sendMessage`,
    placeholder
  • low Secrets in code secret-high-entropy-token package-lock.json:63
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…FSj+bWLt…2sH/Kn8E…h6w==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:179
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…wHD+vkj3…wBQ/hCAQ…tUp/3Qh6…OOw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:185
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…CpK+FtMRQVdIMN6/Df5j…tIC+7KYK…qaA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:238
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…RFW+TK4J…oUr/txX3…6Ns/A==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:282
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…JgI+2Q5U…e1E+Nyvgdz/aIyN…n58/GELp3+w==",
    detector

Files scanned: 20. 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-long-hermes description is 277 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "entry"
  • note frontmatter-key unknown frontmatter key "cron"
  • note frontmatter-key unknown frontmatter key "channels"
  • note frontmatter-key unknown frontmatter key "install"
  • note frontmatter-key unknown frontmatter key "config"
  • note frontmatter-key unknown frontmatter key "trial_days"

Process rating: all ten parameters 56/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. 8 mutating operations with no state check
  • 40Consistency. Frontmatter name (Lead Radar) differs from the folder (lead-radar)
  • 100Tools and files. No external tools needed
  • 100Steps. 22 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1519 tokens

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 276: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 22 items

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

External checks

ClawHub: clean
Lead Radar appears to do what it advertises, with disclosed daily scanning, Gemini scoring, and Telegram delivery, though users should understand the external data flows.
LLM: benign (high) · VirusTotal: · 29 May 2026