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".

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/apollo-pack/skills/apollo-core-workflow-a/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-3

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

The content is highly actionable with executable endpoint code and a clear five-step sequence, but it is verbose with repetition and—critically—fails to use the bundled implementation guide, keeping everything inline. Batch enrichment also lacks an explicit validation feedback loop.

Suggestions

Signal the existing references/implementation-guide.md from the body (e.g., 'Full implementation details: see [implementation-guide.md](references/implementation-guide.md)') and move the long per-step code listings there, keeping SKILL.md as a concise overview.

Add an explicit validation/retry loop around the credit-spending bulk enrichment step (verify enriched count vs. requested, handle null matches, re-try failures) to earn the workflow-clarity checkpoint.

Tighten repetition: state the free-search vs. credit-enrichment distinction once and consolidate the shared axios client setup instead of restating it across steps.

DimensionReasoningScore

Conciseness

The body is mostly executable code with tight prose, but restates the free-vs-credit distinction repeatedly and duplicates axios setup and response-mapping patterns across steps; it could be tightened without losing meaning.

2 / 3

Actionability

Each step supplies complete, executable TypeScript with real endpoints, parameter mappings, and return shapes — copy-paste ready, not pseudocode.

3 / 3

Workflow Clarity

Steps are clearly sequenced (1-5) and the combined pipeline shows the flow, but batch/credit-spending operations like bulk enrichment have no explicit validate/retry feedback loop; the rubric caps workflow clarity at 2 for batch operations lacking validation checkpoints.

2 / 3

Progressive Disclosure

A bundle file references/implementation-guide.md exists but is never referenced or signaled in the body, which is a ~250-line monolithic wall of inline code; this matches the 'monolithic wall of text / poorly organized' anchor.

1 / 3

Total

8

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, third-person description that states concrete capabilities and provides explicit 'Use when' triggers with natural phrasing. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'lead search and enrichment workflow', 'building lead generation features', 'searching for contacts', 'enriching prospect data' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Implement Apollo.io lead search and enrichment workflow') and when ('Use when building lead generation features...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides five natural trigger phrases users would actually say ('apollo lead search', 'search apollo contacts', 'find leads in apollo', 'apollo people search', 'enrich contacts apollo'), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Apollo.io lead-generation is a clear, narrow niche with distinct triggers, unlikely to fire for unrelated skills.

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.