CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-core-workflow-b

Implement Apollo.io email sequences and outreach workflow. Use when building automated email campaigns, creating sequences, or managing outreach through Apollo. Trigger with phrases like "apollo email sequence", "apollo outreach", "apollo campaign", "apollo sequences", "apollo automated emails".

64

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

65%

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 with executable Apollo API code, but it duplicates material held in an orphaned reference file and omits validation checkpoints for batch enrollment. Tightening the duplication and adding verification steps would raise conciseness and workflow clarity.

Suggestions

Replace the inline full implementations with a concise overview and link to references/implementation-guide.md for the complete code, removing the duplication that hurts conciseness and progressive disclosure.

Add explicit validation checkpoints to the outreach pipeline (e.g. confirm each contact was created/found before enrolling, and inspect contacts_already_in_campaign before proceeding) so batch operations have feedback loops.

Signal the reference from the body (e.g. a 'Full implementation: See [implementation-guide.md](references/implementation-guide.md)') so the existing bundle file is discoverable rather than orphaned.

DimensionReasoningScore

Conciseness

The body is code-forward and avoids explaining concepts Claude knows, but it duplicates full implementations (search, add contacts, outreach pipeline) that also appear in references/implementation-guide.md, and the 'Output' section restates endpoints already shown in code, so it could be tightened.

2 / 3

Actionability

Provides fully executable TypeScript with real Apollo endpoints, typed parameters, and concrete return shapes — copy-paste ready with no pseudocode.

3 / 3

Workflow Clarity

Steps 1–6 and the launchOutreach pipeline are clearly sequenced, but batch contact enrollment lacks explicit validate-before-proceed checkpoints (e.g. verify contacts were created, check contacts_already_in_campaign before continuing), which caps batch operations at 2 per the rubric.

2 / 3

Progressive Disclosure

A bundle file (references/implementation-guide.md) exists but is never referenced from the body, and the inline full-code steps duplicate content that should live one level deep in that reference, so navigation and content splitting are not well signaled.

2 / 3

Total

9

/

12

Passed

Description

90%

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 description with explicit 'Use when' triggers and natural, distinctive Apollo-keyworded phrases. The only weakness is that the capability statement is broad rather than enumerating concrete actions, capping specificity at 2.

DimensionReasoningScore

Specificity

Names the Apollo email-sequence domain and a couple of actions ('Implement Apollo.io email sequences and outreach workflow'), but does not list multiple specific concrete actions like the level-3 anchor, so it is not comprehensive.

2 / 3

Completeness

Explicitly answers both what ('Implement Apollo.io email sequences and outreach workflow') and when ('Use when building automated email campaigns, creating sequences, or managing outreach through Apollo') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say — 'apollo email sequence', 'apollo outreach', 'apollo campaign', 'apollo sequences', 'apollo automated emails' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Apollo-specific scope and Apollo-prefixed trigger phrases carve a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.