Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计通过

sequence-load顺序加载

Agent Skill

sequence-load 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

216

周安装

9

GitHub Stars

12

下载量

72
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sequence-load(顺序加载)
来源仓库:https://github.com/scientiacapital/skills
仓库路径:skills/sequence-load
安装命令:
npx skills add https://github.com/scientiacapital/skills --skill sequence-load
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/scientiacapital/skills --skill sequence-load

简介

sequence-load 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 可结合来源仓库和原始 README 进一步核验具体用法和功能边界。

SKILL.md

Sequence Load Skill

<quick_start> Trigger: Monday 7:15 AM ET (runs after prospect-refresh at 6:30 AM) Manual Trigger: "Load prospects into sequences" or "Enroll new leads" Dependencies: Requires Apollo credits, prospect-refresh output, HubSpot portal 21530819 Output: Enrollment confirmation per prospect, sequence assignment, contact IDs for HubSpot creation </quick_start>

<success_criteria>

  • Read prospect-refresh output (30 net-new prospects from Gmail drafts + HTML report)
  • Query HubSpot to verify prospect not already enrolled in any sequence
  • Validate phone number exists (from prospect-enrich or Apollo)
  • Apply Golden Rules (skip customers, channel, device owners, NEVER ATL)
  • Find target Apollo sequence(s) by ICP vertical
  • Get email account ID (tim@epiphan.com or primary)
  • Batch add prospects to sequence (max 100 per request)
  • Confirm enrollments (check Apollo contact.sequence_id)
  • Create HubSpot contacts if not exist (pull contact IDs for HubSpot sync)
  • Report: total enrolled, per-sequence breakdown, any failures </success_criteria>

Stage 1: Read Prospect Refresh Output

Input Source: prospect-refresh HTML report + Gmail drafts

Extract from HTML Report:

  • Prospect name, email, title, company, vertical, ATL/BTL tier
  • Apollo person_id, organization_id, phone
  • Company revenue, headcount, funding

Validation:

  • Email format is valid
  • Phone exists (from enrichment)
  • Vertical is one of: Higher Ed, Courts, Gov, Corporate AV, Healthcare, HoW, K-12

Output: Structured list of 30 prospects (or fewer if filtering applied)


Stage 2: Deduplicate Against HubSpot + Apollo

Step A: Check HubSpot for existing contact

MCP Tool: search_crm_objects (HubSpot)

objectType: "contacts"
filterGroups: [{
  filters: [
    { propertyName: "email", operator: "EQ", value: prospect.email }
  ]
}]
properties: ["email", "phone", "hs_lead_status"]

Decision Logic:

  • If contact exists + NOT in "Sequenced" or "Active Sequence" status → REUSE contact (get contact ID)
  • If contact exists + in sequence → SKIP (avoid re-enrollment)
  • If contact does not exist → PROCEED to Stage 3 (create new)

Step B: Check Apollo for duplicate enrollments

MCP Tool: apollo_contacts_search

q_keywords: prospect.email
per_page: 10

Decision Logic:

  • If Apollo contact exists + already in a sequence → SKIP
  • If Apollo contact exists + no sequence → PROCEED (re-enroll)
  • If Apollo contact does not exist → PROCEED to Stage 3 (create new)

Dedup Output: List of unique prospects (typically 60-70% of input after dedup)


Stage 3: Validate Golden Rules + Phone Exists

Golden Rules (Hard Exclusions):

Skip if:

  • Email domain matches known customer domain (cross-check crm_customers)
  • Contact tagged "Channel Partner" in HubSpot
  • Contact tagged "Device Owner" in HubSpot
  • Company in "Product Page Engagers" tag
  • Title in NEVER ATL list: Warehouse Manager, Network Manager, Systems Admin, AV Technician, Graphic Design Instructor, Program Administrator, Web Designer, Classroom Support, Lab Coordinator, Maintenance, Building Engineer, Multimedia Services Manager, Video Production Specialist, Streaming Crew

Phone Validation:

  • Phone must be non-null (from Apollo enrichment or prospect-enrich)
  • Format: +1-XXX-XXX-XXXX (US) or +1-XXX-XXX-XXXX (Canada)
  • If phone missing → LOG as "Phone Missing" but DO NOT ENROLL (requires phone for Apollo compliance)

Output: Verified prospect list (typically 80-90% after phone validation)


Stage 4: Map Prospects to Target Sequences

MCP Tool: apollo_emailer_campaigns_search

Search for sequences by vertical + template:

VerticalSequence Name PatternTarget Sequence ID
Higher EdBDR_HigherEd_OutboundX[search by name]
CourtsBDR_Courts_OutboundX[search by name]
GovernmentBDR_Government_OutboundX[search by name]
Corporate AVBDR_CorporateAV_OutboundX[search by name]
HealthcareBDR_Healthcare_OutboundX[search by name]
Houses of WorshipBDR_HoW_OutboundX[search by name]
K-12BDR_K12_OutboundX[search by name]

Query Logic:

per_page: 100
# Search returns: id, name, status, num_contacts, num_enrolled

Sequence Selection Rule:

  • Map prospect.vertical to sequence_name_pattern
  • Choose sequence with LOWEST current enrollment (load balancing)
  • Fallback: default "BDR_Outbound_General" if vertical-specific not found

Output: Prospect + sequence_id mapping


Stage 5: Create Apollo Contacts (If New)

MCP Tool: apollo_contacts_search

For new prospects (not found in Stage 2):

per_page: 10
q_keywords: prospect.email

If not found, create contact via:

MCP Tool: apollo_contacts_create

email: prospect.email
first_name: prospect.first_name
last_name: prospect.last_name
title: prospect.title
organization_name: prospect.company
phone: prospect.phone (if available)
label_names: [prospect.vertical, "BDR_Prospect", "2026_Q1"]

Output: New Apollo contact ID (apollo_contact_id)


Stage 6: Get Email Account ID

MCP Tool: apollo_email_accounts_index

Query all linked email accounts:

# Returns: [{ id, email, status, daily_send_limit, ... }]

Selection Logic:

  • Look for email containing "epiphan" or "tkipper"
  • Use primary email account if multiple
  • If none found → ERROR (cannot proceed without email account)

Output: email_account_id (e.g., "6633baaece5fbd01c791d7ca")


Stage 7: Batch Add to Sequences

MCP Tool: apollo_emailer_campaigns_add_contact_ids

For each sequence (group prospects by sequence_id):

id: sequence_id (from Stage 4 mapping)
emailer_campaign_id: sequence_id (same as id)
send_email_from_email_account_id: email_account_id (from Stage 6)
contact_ids: [contact_id_1, contact_id_2, ..., contact_id_N] (max 100 per batch)
sequence_active_in_other_campaigns: true (allow multi-sequence enrollment)
sequence_unverified_email: false (require verified emails)
status: "active" (start sequence immediately)

Batch Logic:

  • Group prospects by target sequence
  • Send 100 contacts max per API call
  • Retry if rate limited

Expected Success Rate: 95%+ (most failures due to email validation)


Stage 8: Confirm Enrollments

MCP Tool: apollo_contacts_search

For each enrolled contact, verify enrollment:

q_keywords: contact.email
per_page: 1

Check response:

  • contact.sequences (should contain sequence_id from Stage 7)
  • contact.last_sequence_enrollment_date (should be "today")
  • contact.status (should be "active")

Log Enrollment:

✓ jane@acme.com → BDR_HigherEd_Outbound (sequence_id: abc123)
✗ bob@example.com → Phone validation failed
✗ carol@company.com → Already enrolled in BDR_Corporate_AV

Stage 9: Create HubSpot Contacts (Sync)

For newly created Apollo contacts, create HubSpot counterparts:

MCP Tool: manage_crm_objects (HubSpot createRequest)

objectType: "contacts"
properties: {
  firstname: prospect.first_name,
  lastname: prospect.last_name,
  email: prospect.email,
  phone: prospect.phone,
  jobtitle: prospect.title,
  company: prospect.company_name,
  lifecyclestage: "subscriber",
  hs_lead_status: "open",
  custom_apollo_contact_id: apollo_contact_id,
  custom_apollo_sequence: sequence_name,
  custom_atl_btl_tier: prospect.atl_btl_tier,
  custom_prospect_vertical: prospect.vertical,
  custom_prospect_icp_score: prospect.icp_score
}
associations: [
  {
    targetObjectId: company_id, # Find or create company in HubSpot
    targetObjectType: "companies"
  }
]

Company Association Logic:

  • Search HubSpot for company by domain
  • If found: use company_id from existing record
  • If not found: create company via manage_crm_objects

Output: Created contact IDs (to link Gmail drafts)


Stage 10: Output Enrollment Report

Format: Markdown table + summary stats

Enrollment Table:

ProspectEmailPhoneVerticalSequenceApollo IDHubSpot IDStatus
Jane Smithjane@acme.com+1-555-0123Higher EdBDR_HigherEd_1apollo-123hs-456✓ Enrolled
Bob Jonesbob@example.comnullCourts---✗ Phone missing
Carol Whitecarol@corp.com+1-555-0124Corp AVBDR_CorporateAV_1apollo-789hs-012✓ Enrolled

Summary Stats:

  • Total prospects processed: X
  • Successfully enrolled: Y (Y% of X)
  • Phone validation failures: Z
  • Duplicate/already enrolled: W
  • HubSpot synced: Y (new contacts)
  • Per-sequence breakdown:

- BDR_HigherEd_1: 5 enrolled - BDR_Courts_1: 4 enrolled - BDR_CorporateAV_1: 5 enrolled - etc.

Next Steps: Prospects now enrolled in Apollo sequences. Gmail drafts (from prospect-refresh) ready for manual review + send-from-draft workflow.


Emit Outcome Sidecar

As the final step, write to ~/.claude/skill-analytics/last-outcome-sequence-load.json:

{"ts":"[UTC ISO8601]","skill":"sequence-load","version":"1.0.0","variant":"default",
 "status":"[success|partial|error]","runtime_ms":[estimated ms from start],
 "metrics":{"contacts_loaded":[n],"sequences_updated":[n],"duplicates_skipped":[n],"phone_validation_failures":[n]},
 "error":null,"session_id":"[YYYY-MM-DD]"}

Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated.


Skill Metadata

Version: 1.0 Last Updated: 2026-03-19 Author: Tim Kipper Status: Production Integration: Apollo + HubSpot (portal 21530819) Tier: P1 (Core BDR Automation) Triggers: Scheduled (Monday 7:15 AM) + Manual ("Load sequences") Dependencies: prospect-refresh (6:30 AM) → sequence-load (7:15 AM) → morning-brief (7:30 AM)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.66%
按下载量换算25

Claude

33.02%
按下载量换算24

Cursor

20.01%
按下载量换算14

Gemini CLI

9.79%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills