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".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Apollo.io email sequences/outreach), includes explicit 'Use when' guidance, and provides specific trigger phrases. Its main weakness is that the capability description could be more specific about the concrete actions it performs beyond the general 'implement', 'build', and 'manage' verbs.
Suggestions
Add more specific concrete actions such as 'configure multi-step sequences', 'set follow-up delays', 'add personalization tokens', or 'manage contact lists' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io email sequences and outreach) and some actions ('implement', 'building automated email campaigns', 'creating sequences', 'managing outreach'), but lacks specific concrete actions like 'configure follow-up steps', 'set delay intervals', 'add personalization variables', or 'track open rates'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Apollo.io email sequences and outreach workflow) and 'when' (explicit 'Use when' clause for building automated email campaigns, creating sequences, managing outreach, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger phrases users would say: 'apollo email sequence', 'apollo outreach', 'apollo campaign', 'apollo sequences', 'apollo automated emails'. These are specific and cover common variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Apollo.io' platform focus combined with email sequence/outreach terminology. Unlikely to conflict with generic email skills or other CRM/outreach tool skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with complete executable TypeScript code covering the full Apollo email sequence workflow. Its main weakness is the lack of validation checkpoints in the multi-step outreach pipeline — there's no verification that the sequence is active, that the email account has sufficient daily send capacity, or that batch operations completed successfully before proceeding. The content could also be slightly more concise by trimming the Output section which restates the steps.
Suggestions
Add validation checkpoints in the pipeline: verify the sequence is active before enrollment, check daily send limits against batch size, and validate that contact creation succeeded before proceeding to enrollment.
Add a verification step after addContactsToSequence that checks for errors in the response and handles partial failures (e.g., retry or report which contacts failed).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary commentary (e.g., 'Contacts must exist in your Apollo CRM before adding to sequences') and the Output section largely restates what was already shown in the steps. The code comments are generally useful but some are redundant. | 2 / 3 |
Actionability | Fully executable TypeScript code with complete function signatures, proper API endpoints, request/response handling, and a full pipeline example in Step 6. Every step includes copy-paste ready code with real API paths and parameter names. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the full pipeline in Step 6 ties everything together with basic error handling (try/catch for existing contacts). However, there are no explicit validation checkpoints — no verification that contacts were actually created successfully before enrolling, no check that the sequence is active before adding contacts, and no feedback loop for handling partial failures in batch enrollment. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Overview, Prerequisites, numbered Steps, Output summary, Error Handling table, Resources with direct links, and Next Steps). References to related skills (apollo-core-workflow-a, apollo-common-errors) are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 12 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.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.