Skill Market

sequence load

Find leads matching criteria and bulk-add them to an Apollo outreach sequence. Handles enrichment, contact creation, deduplication, and enrollment in one flow.

GitHub
githubcommunityclaudemcp
0.0
0 installs24.9K GitHub starsby anthropics

Skill Introduction

Overview
Find leads matching criteria and bulk-add them to an Apollo outreach sequence. Handles enrichment, contact creation, deduplication, and enrollment in one flow.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, claude, mcp work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from anthropics.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, claude, mcp that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, claude, mcp, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install sequence-load-c96c53
View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: sequence-load description: "Find leads matching criteria and bulk-add them to an Apollo outreach sequence. Handles enrichment, contact creation, deduplication, and enrollment in one flow." user-invocable: true argument-hint: "[targeting criteria + sequence name]"

Sequence Load

Find, enrich, and load contacts into an outreach sequence — end to end. The user provides targeting criteria and a sequence name via "$ARGUMENTS".

Examples

  • /apollo:sequence-load add 20 VP Sales at SaaS companies to my "Q1 Outbound" sequence
  • /apollo:sequence-load SDR managers at fintech startups → Cold Outreach v2
  • /apollo:sequence-load list sequences (shows all available sequences)
  • /apollo:sequence-load directors of engineering, 500+ employees, US → Demo Follow-up
  • /apollo:sequence-load reload 15 more leads into "Enterprise Pipeline"

Step 1 — Parse Input

From "$ARGUMENTS", extract:

Targeting criteria:

  • Job titles → person_titles
  • Seniority levels → person_seniorities
  • Industry keywords → q_organization_keyword_tags
  • Company size → organization_num_employees_ranges
  • Locations → person_locations or organization_locations

Sequence info:

  • Sequence name (text after "to", "into", or "→")
  • Volume — how many contacts to add (default: 10 if not specified)

If the user just says "list sequences", skip to Step 2 and show all available sequences.

Step 2 — Find the Sequence

Use mcp__claude_ai_Apollo_MCP__apollo_emailer_campaigns_search to find the target sequence:

  • Set q_name to the sequence name from input

If no match or multiple matches:

  • Show all available sequences in a table: | Name | ID | Status |
  • Ask the user to pick one

Step 3 — Get Email Account

Use mcp__claude_ai_Apollo_MCP__apollo_email_accounts_index to list linked email accounts.

  • If one account → use automatically
  • If multiple → show them and ask which to send from

Step 4 — Find Matching People

Use mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with the targeting criteria.

  • Set per_page to the requested volume (or 10 by default)

Present the candidates in a preview table:

#NameTitleCompanyLocation

Ask: "Add these [N] contacts to [Sequence Name]? This will consume [N] Apollo credits for enrichment."

Wait for confirmation before proceeding.

Step 5 — Enrich and Create Contacts

For each approved lead:

  1. Enrich — Use mcp__claude_ai_Apollo_MCP__apollo_people_bulk_match (batch up to 10 per call) with:

    • first_name, last_name, domain for each person
    • reveal_personal_emails set to true
  2. Create contacts — For each enriched person, use mcp__claude_ai_Apollo_MCP__apollo_contacts_create with:

    • first_name, last_name, email, title, organization_name
    • direct_phone or mobile_phone if available
    • run_dedupe set to true

Collect all created contact IDs.

Step 6 — Add to Sequence

Use mcp__claude_ai_Apollo_MCP__apollo_emailer_campaigns_add_contact_ids with:

  • id: the sequence ID
  • emailer_campaign_id: same sequence ID
  • contact_ids: array of created contact IDs
  • send_email_from_email_account_id: the chosen email account ID
  • sequence_active_in_other_campaigns: false (safe default)

Step 7 — Confirm Enrollment

Show a summary:


Sequence loaded successfully

FieldValue
Sequence[Name]
Contacts added[count]
Sending from[email address]
Credits used[count]

Contacts enrolled:

NameTitleCompanyEmail

Step 8 — Offer Next Actions

Ask the user:

  1. Load more — Find and add another batch of leads
  2. Review sequence — Show sequence details and all enrolled contacts
  3. Remove a contact — Use mcp__claude_ai_Apollo_MCP__apollo_emailer_campaigns_remove_or_stop_contact_ids to remove specific contacts
  4. Pause a contact — Re-add with status: "paused" and an auto_unpause_at date

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet