AF lead-gen
Lead generation, prospecting, and qualification for B2B sales. Use when asked to find leads, build prospect lists, research target companies, qualify leads against an ICP, enrich contact data, find decision-maker email formats, scrape company info, score leads, or build a sales pipeline from scratch. Triggers on phrases like "find leads", "build a prospect list", "who should I target", "lead generation", "find decision makers", "ICP research", "sales prospecting", "qualify leads", "enrich contacts", "find emails", "pipeline building".
As a process F 45/100 · Will not run — References files that are not bundled: references/email-formats.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/email-formats.md
Process rating: all ten parameters 45/100
- 0Tools and files. 1 referenced file(s) missing: references/email-formats.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (lead-gen) differs from the folder (lead-gen-x)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 27 steps
- 100Execution cost. Instruction body is 593 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 540: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.