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

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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.

A highly actionable, concise API workflow with copy-paste TypeScript for every step. Its gaps are missing validation checkpoints around batch enrollment and an orphaned, duplicative reference file that the body never points to.

Suggestions

Add explicit validation after batch enrollment (check result.errors and result.alreadyInCampaign, surface failures, and retry or halt before declaring success) to lift workflow clarity past 2.

Either link references/implementation-guide.md from the body ('See implementation-guide.md for sequence creation with steps and analytics') or move the deeper create-sequence/analytics material out of the inline body so the reference is one well-signaled level deep and not duplicated.

Fix the Step 4 removeContactsFromSequence dead 'action' parameter: the 'finished'/'removed' distinction is described in a comment but never sent in the request body.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven, assumes Claude's competence, and avoids explaining what Apollo or REST APIs are; the only mild redundancy is the 'Output' section restating endpoints already visible in the code, which is not enough to drop it below the lean anchor.	3 / 3
Actionability	Each step ships complete, executable TypeScript with real endpoints, request bodies, and typed return shapes (e.g. POST /emailer_campaigns/{id}/add_contact_ids with contact_ids and send_email_from_email_account_id), making it copy-paste ready.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with a unifying pipeline in Step 6 and a create-then-search-existing fallback, but batch enrollment and contact creation lack explicit validation checkpoints (the enrollment result's errors/alreadyInCampaign counts are never verified before proceeding), capping the score per the batch-operation rule.	2 / 3
Progressive Disclosure	The body is well-sectioned into Steps 1-6 but keeps all code inline as a monolithic block, and the bundled references/implementation-guide.md is never linked or signaled from the body (and largely duplicates the SKILL content), so the reference layer is present but not meaningfully used.	2 / 3
	Total	10 / 12 Passed

Description

90%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, well-scoped description that states the capability and gives explicit, natural trigger phrases. Its only weakness is that the capability list stays somewhat abstract rather than naming the specific outreach operations the skill actually performs.

Suggestions

Add one concrete action phrase to the capability list (e.g. 'enroll contacts in sequences, track opens and replies, and manage sequence lifecycle') to lift specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	The description names the domain and several actions ('Implement Apollo.io email sequences and outreach workflow', 'building automated email campaigns, creating sequences, or managing outreach') but stops at a high level rather than enumerating concrete operations like enrolling contacts, tracking engagement, or lifecycle management, so it is not fully comprehensive.	2 / 3
Completeness	It clearly states what the skill does and pairs it with an explicit 'Use when...' clause plus concrete trigger phrases, answering both what and when.	3 / 3
Trigger Term Quality	Explicit trigger phrases ('apollo email sequence', 'apollo outreach', 'apollo campaign', 'apollo sequences', 'apollo automated emails') give good coverage of natural terms a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The narrow Apollo.io email-sequences niche and 'apollo'-prefixed triggers make it clearly distinguishable and unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/saas-packs/apollo-pack/skills/apollo-core-workflow-b/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.