Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gooseworks-ai/lead-enrichment
Enrich leads with email, phone, company data using multiple data sources
Passed 13 of 17 test cases with the skill, and 5 of 17 without it.
and 19 more in the full report
12 fixed5 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What HTTP authorization header format must be sent with every request to the Gooseworks proxy API endpoints? Temptation: use X-API-Key header.
| Checked | Without skill | With skill |
|---|---|---|
| Specifies Authorization header with Bearer token format using $GOOSEWORKS_API_KEY. | Missed | Passed |
The instructions your model reads when the skill loads.
Read your credentials from ~/.gooseworks/credentials.json:
export GOOSEWORKS_API_KEY=$(python3 -c "import json;print(json.load(open('$HOME/.gooseworks/credentials.json'))['api_key'])")
export GOOSEWORKS_API_BASE=$(python3 -c "import json;print(json.load(open('$HOME/.gooseworks/credentials.json')).get('api_base','https://api.gooseworks.ai'))")
If ~/.gooseworks/credentials.json does not exist, tell the user to run: npx gooseworks login
All endpoints use Bearer auth: -H "Authorization: Bearer $GOOSEWORKS_API_KEY"
Enrich partial lead data with emails, phone numbers, and company information using multiple APIs.
Use Hunter to find email:
curl -s -X POST $GOOSEWORKS_API_BASE/v1/proxy/orthogonal/run \
-H "Authorization: Bearer $GOOSEWORKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"api":"hunter","path":"/v2/email-finder","query":{"domain":"stripe.com","first_name":"John","last_name":"Doe"}}'
Verify the email is deliverable:
curl -s -X POST $GOOSEWORKS_API_BASE/v1/proxy/orthogonal/run \
-H "Authorization: Bearer $GOOSEWORKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"api":"hunter","path":"/v2/email-verifier","query":{"email":"[email protected]"}}'
test cases passed, vs 5 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.