AC prospect-enrichment
Enriches prospect and company profiles by scraping their website and searching for additional context to build comprehensive profiles. Use when the user wants to enrich a prospect, analyze a prospect site, do site enrichment, learn about a company, build a company profile, do prospect research, find out what a company does, or do a company deep dive. Also use when the user mentions 'enrich prospect,' 'company profile,' 'prospect research,' 'company deep dive,' or 'what does this company do.' This skill combines site scraping with web search for comprehensive prospect profiles -- for raw site scraping, see firecrawl-cli; for raw company search, see exa-company-research; for lead list building, see exa-lead-generation. See cold-email for using enriched profiles in outreach, see competitive-intelligence for competitor-focused research.
As a process C 59/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- 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: 2. 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 59/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (prospect-enrichment) differs from the folder (abm-prospect-enrichment)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 1866 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)
- +3Description length 844: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 18 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.