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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-core-workflow-b/SKILL.mdQuality
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), provides explicit trigger guidance with natural phrases, and is highly distinctive. Its main weakness is that the capability description could be more specific about the concrete actions it performs beyond the general 'implement', 'build', 'create', and 'manage' verbs.
Suggestions
Add more specific concrete actions such as 'compose email templates, configure follow-up timing, set up A/B tests, manage contact lists, track sequence performance' 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 doesn't list multiple concrete specific actions like composing email templates, setting follow-up intervals, tracking open rates, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Apollo.io email sequences and outreach workflow) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases like' section listing specific activation terms). | 3 / 3 |
Trigger Term Quality | Includes a well-defined 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 of how users would refer to this task. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'Apollo.io' and the combination of email sequences + outreach workflow. The trigger terms all include 'apollo' which makes it very unlikely to conflict with generic email or campaign skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 fully executable TypeScript code covering the Apollo email sequences API comprehensively. Its main weaknesses are the lack of validation checkpoints in a workflow that triggers real email sends (a potentially destructive operation), and the monolithic structure that could benefit from splitting detailed code into supporting files. The error handling table is a nice touch but doesn't compensate for missing in-workflow validation.
Suggestions
Add explicit validation checkpoints: verify the sequence exists and is active before enrollment, confirm contact creation succeeded before collecting IDs, and validate the sender account has remaining daily send capacity.
Add a feedback loop for partial failures in the batch contact creation — e.g., log failures, retry, or return a summary of which leads failed and why.
Consider splitting the detailed code examples into a separate reference file (e.g., sequences-api.ts) and keeping SKILL.md as a concise overview with the pipeline workflow and key decision points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary commentary (e.g., explaining what sequences are called in the API, the 'Contacts must exist in your Apollo CRM before adding to sequences' preamble). The Output section largely restates what was already shown in the code. Some inline comments are helpful but others are redundant. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, typed parameters, and real API endpoints. The full outreach pipeline in Step 6 ties everything together into a copy-paste-ready workflow. Error handling table provides specific causes and solutions. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the full pipeline in Step 6 shows the correct order. However, there are no explicit validation checkpoints — no verification that contacts were actually created successfully before proceeding, no check that the sequence exists and is active before enrollment, and no feedback loop for handling partial failures in the batch contact creation. For an outreach operation that sends real emails, this is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill has good section structure and references external docs and a related skill (apollo-core-workflow-a, apollo-common-errors). However, the content is quite long (~150+ lines of code) and could benefit from splitting detailed API examples into a separate reference file while keeping SKILL.md as a concise overview. No bundle files are provided to support progressive disclosure. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.