CtrlK
BlogDocsLog inGet started
Tessl Logo

data-enrichment

Enrich contact and company data using x402-protected APIs at stableenrich.dev. Superior to generic web search for structured business data. USE FOR: - Enriching person profiles by email, LinkedIn URL, or name - Enriching companies by domain - Finding contact details (email, phone) with confidence scores - Searching for people or companies by criteria - Verifying email deliverability before outreach TRIGGERS: - "enrich", "lookup", "find info about", "research" - "who is [person]", "company profile for", "tell me about" - "find contact for", "get LinkedIn for", "get email for" - "employee at", "works at", "company details" - "verify email", "check email", "is this email valid" ALWAYS use agentcash.fetch for stableenrich.dev endpoints - never curl or WebFetch. Returns structured JSON data, not web page HTML. IMPORTANT: Call check_endpoint_schema before first fetch on any endpoint. Field names are provider-specific — do not reuse Apollo, PDL, or other-provider shapes on FullEnrich routes.

75

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and well-structured with executable examples and a useful quick-reference table. Minor gaps: the parallel-calls workflow lacks an explicit post-fetch verification step, and the detailed endpoint reference could be progressively disclosed into a separate file.

Suggestions

Add an explicit verification checkpoint after parallel fetch calls (e.g., confirm each response's billing/status field before acting on results) to close the batch-validation gap.

Move the per-endpoint detail blocks (URL, price, valid inputs) into a separate references/endpoints.md and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Make the Mandatory workflow's schema-check gate explicit as a hard validation step with a retry loop (re-check_endpoint_schema if the fetch 400s on field names), mirroring the missing-data recovery pattern.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no basic-concept explanations, just executable fetch examples and a compact quick-reference table, so every token earns its place.

5 / 5

Actionability

It provides copy-paste-ready agentcash.fetch calls with real URLs, methods, and bodies for every endpoint, plus a quick-reference table with prices and a status-meaning table, covering the common cases.

5 / 5

Workflow Clarity

The Mandatory workflow and Standard Enrichment checklist give a clear discover→check_endpoint_schema→fetch sequence with a schema-validation gate, but parallel/batch fetch calls lack an explicit post-fetch verification checkpoint, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Structure is good with a clearly signaled one-level reference (rules/getting-started.md) and well-organized sections, but the bulk per-endpoint API reference is inlined rather than split into a separate reference file.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it states concrete capabilities, gives natural trigger phrases, and clearly scopes usage to the stableenrich.dev x402 APIs via agentcash. It uses correct third-person voice and contains no fluff.

DimensionReasoningScore

Specificity

The USE FOR list enumerates multiple concrete actions (enrich persons by email/LinkedIn/name, enrich companies by domain, find contact details with confidence scores, verify email deliverability), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both 'what' (enrich contact/company data via x402-protected APIs at stableenrich.dev) and 'when' (USE FOR and TRIGGERS sections with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

TRIGGERS provides comprehensive natural phrases users would say ('enrich', 'lookup', 'who is [person]', 'company profile for', 'find contact for', 'verify email') with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (stableenrich.dev x402 enrichment via the agentcash MCP tool) with distinct triggers and an explicit guard against curl/WebFetch, minimizing conflict with other skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
Merit-Systems/agentcash-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.