CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-core-workflow-a

Implement Apollo.io lead search and enrichment workflow. Use when building lead generation features, searching for contacts, or enriching prospect data from Apollo. Trigger with phrases like "apollo lead search", "search apollo contacts", "find leads in apollo", "apollo people search", "enrich contacts apollo".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is highly actionable and reasonably concise, but its batch-enrichment workflow omits explicit validation checkpoints and it fails to route detail into the existing reference file, leaving both workflow_clarity and progressive_disclosure at the mid level.

Suggestions

Add an explicit validation checkpoint in buildLeadPipeline (e.g. confirm people were returned before enriching, check for null matches, retry failed enrichments) so the batch credit-spending workflow has a validate→fix→retry loop.

Slim the inline code in SKILL.md to a concise overview and link to references/implementation-guide.md (e.g. 'Full implementation: See [implementation-guide.md](references/implementation-guide.md)') instead of duplicating the pipeline in both files.

Remove or trim the 'Output' section that restates the endpoints already shown in the code to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is dense executable TypeScript with minimal explanatory prose and no padding of concepts Claude already knows; the only mild redundancy is the 'Output' recap restating endpoints already shown in code, keeping it just within the lean/efficient anchor.

3 / 3

Actionability

Every step ships complete, copy-paste-ready code using real endpoints and parameter names (e.g. 'POST /mixed_people/api_search', 'reveal_phone_number: true', 'q_organization_domains_list'), fully matching the executable-code anchor.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced, but the credit-consuming bulk-enrichment pipeline lacks an explicit validation checkpoint (e.g. verify search results, validate enrichment responses, retry on null), so per the batch-operations guideline workflow_clarity is capped at 2 rather than reaching the validate→fix→retry anchor.

2 / 3

Progressive Disclosure

A bundle file references/implementation-guide.md exists but is never linked from the body, and the body inlines ~250 lines of code that substantially duplicates the reference, matching the 'references present but not clearly signaled; content that should be separate is inline' anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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, includes an explicit 'Use when' trigger clause plus natural keyword phrases, and carves out a distinct Apollo lead-search/enrichment niche. It cleanly satisfies all four dimensions at the top of the scale.

DimensionReasoningScore

Specificity

Names the Apollo.io domain and lists multiple concrete actions — 'lead search and enrichment workflow', 'building lead generation features, searching for contacts, or enriching prospect data' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers both 'what' ('Implement Apollo.io lead search and enrichment workflow') and 'when' with an explicit 'Use when...' clause and a 'Trigger with phrases like...' list, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Provides natural phrases a user would say — 'apollo lead search', 'search apollo contacts', 'find leads in apollo', 'apollo people search', 'enrich contacts apollo' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Apollo-specific niche and Apollo-branded triggers make it clearly distinguishable and unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.