BD signalhire
Prospect and enrich contacts via the SignalHire API (Search, Person and Credits)
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationInfrastructureSales and CRMtype and topics are labelled automatically from the skill text
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlREADME.md:64Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)# This prints a public URL such as https://red-example.trycloudflare.com
placeholder -
low Exfiltration
exfil-webhook-urlREADME.md:67Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)Set `SIGNALHIRE_CALLBACK_URL` to `https://red-example.trycloudflare.com/signalhire/callback`.
placeholder
Files scanned: 5. 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")
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (signalhire) differs from the folder (signalhire-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 1623 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)
- +3Description length 80: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 7 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
The skill is a disclosed SignalHire enrichment connector, but it exposes unauthenticated public callback/status endpoints and stores sensitive contact data in plaintext CSV files without adequate safeguards.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026