원클릭으로 Manus에서 모든 스킬 실행

sales-instantly

스타58

포크7

업데이트2026년 6월 27일 14:12

Instantly (instantly.ai) platform help — high-volume cold email outreach: campaigns/sequences across unlimited inboxes, free warmup, inbox-placement tests, Unibox, and separate Lead Finder (Credits) + CRM. REST API v2 (api.instantly.ai/api/v2, Bearer token, cursor pagination, OpenAPI spec; v2 incompatible with v1) plus webhooks (reply received, email events, meeting booked). Use when building an Instantly API or webhook integration, pushing leads into a campaign or syncing reply/opportunity events to a CRM, your warmup score looks healthy but emails still land in spam, DFY pre-warmed domains arriving burned, the real cost ballooning past the $47 headline once you add Credits and CRM, choosing Growth vs Hypergrowth vs Light Speed, or generating a v2 API key. Do NOT use for cold-email deliverability/warmup strategy across tools (use /sales-deliverability), outbound sequence/copy strategy (use /sales-cadence), or building a prospect list across tools (use /sales-prospect-list).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

sales-skills

sales-skills/sales

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

파일 탐색기

4 개 파일

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

sales-do

sales-skills/sales

Routes any sales, marketing, ad, or GTM objective to the right specialized skill and outputs the install command for that skill plus a ready-to-paste prompt packed with the user's context. Asks clarifying questions when the objective is ambiguous, then hands back a copy-paste-runnable next step. Covers prospecting, outbound cadences, deals, proposals, forecasting, deliverability, enrichment, intent, content, coaching, CRO, SEO, launch directories, newsletters, email/SMS/push marketing, chatbots, influencer marketing, social media, employee advocacy, media relations, reviews, data hygiene, B2B advertising, retargeting, affiliate, loyalty, digital products, memberships, webinars, checkout, and platform-specific help. Use when the user has a sales or marketing question and isn't sure which skill to use, or wants a multi-skill sequence with a batch install command. Do NOT use to solve problems directly — this skill only routes.

2026-06-2858

sales-phantombuster

sales-skills/sales

PhantomBuster (phantombuster.com) platform help — code-free web/LinkedIn automation + scraping + lead-gen: 'Phantoms' (LinkedIn search export, scrapers, auto-connect, email finder), Flows that chain them, AI Agents + a cloud LinkedIn Leads database. Developer surface: a REST API (base phantombuster.com/api/v2, X-Phantombuster-Key-1 header) to launch agents (POST /agent/{id}/launch → container id) and fetch run results (/containers/fetch-result-object), plus the Leads storage and per-agent webhooks (secret param, 11s timeout) on run completion. Billed by execution time + slots; API on all paid plans. Use when launching a Phantom or fetching its scraped output via the API, wiring a run-finished webhook, handling the async agent→container model, managing slots/execution-time, or LinkedIn cookie/safety issues. Do NOT use for prospect-list / lead-sourcing strategy across tools (use /sales-prospect-list), enrichment strategy across vendors (use /sales-enrich), or outbound cadence strategy (use /sales-cadence).

2026-06-2858

sales-prospect-list

sales-skills/sales

Builds targeted B2B prospect lists for outbound campaigns from database providers (Apollo, ZoomInfo, Clay, Cognism). Use when you don't know who to target, your outbound list is too broad and response rates are low, you can't find the right decision-makers at target accounts, your ICP is vague, or your prospect list is full of bad-fit contacts. Do NOT use for enriching existing contacts with emails/phones (use /sales-enrich), interpreting buying signals (use /sales-intent), general Apollo platform help (use /sales-apollo), or hyperlocal / door-to-door / territory / route-based outbound to local SMBs that aren't on databases — restaurants, gas stations, salons, contractors, HVAC — (use /sales-field-sales).

2026-06-2858

sales-intent

sales-skills/sales

Interprets buying signals and prioritize accounts for outreach. Use when drowning in intent data and not sure what matters, can't tell which accounts to prioritize, buying signals aren't translating to pipeline, job change alerts are noisy, intent topics feel too broad, lead scores don't match actual deal quality, or not sure how to act on signals in outreach. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), ZoomInfo-specific intent config (use /sales-zoominfo), or general Apollo platform help (use /sales-apollo).

2026-06-2858

sales-syncgtm

sales-skills/sales

SyncGTM (syncgtm.com) platform help — AI-native GTM data engine that unifies buying signals (job changes, funding, hiring, LinkedIn posts, web-traffic, custom AI signals), waterfall enrichment (verified emails/mobiles, 40+ providers), AI lead scoring (0–100 vs ICP), AI research agents, and a no-code Workflow Builder. Developer surface: an MCP server (api.syncgtm.com/mcp, OAuth browser sign-in, free-plan — works with Claude Code/Cursor to enrich, find emails/phones, read signals), a REST API (api.syncgtm.com, API key), webhooks, and 40+ integrations (HubSpot/Salesforce/Slack/Attio). Use when connecting the MCP server to an AI agent, enriching contacts via the API, acting on buyer signals, scoring leads vs an ICP, building a signal→enrich→outreach workflow, or choosing SyncGTM vs Clay/Trigify. Do NOT use for intent-data strategy across tools (use /sales-intent), prospect-list building (use /sales-prospect-list), or enrichment strategy across vendors (use /sales-enrich).

2026-06-2858

sales-cadence

sales-skills/sales

Designs multi-channel outbound cadences with timing, A/B testing, and content. Use when outbound sequences getting low reply rates, unsure how many touchpoints or what spacing to use, cadence emails sound generic, prospects ignoring calls, A/B tests not moving the needle, sequence performance plateauing, or not sure which channels to include in outreach. Do NOT use for marketing cold email (use /cold-email), automated email flows (use /email-sequence), or general Salesloft platform help (use /sales-salesloft).

2026-06-2858

name	sales-instantly
description	Instantly (instantly.ai) platform help — high-volume cold email outreach: campaigns/sequences across unlimited inboxes, free warmup, inbox-placement tests, Unibox, and separate Lead Finder (Credits) + CRM. REST API v2 (api.instantly.ai/api/v2, Bearer token, cursor pagination, OpenAPI spec; v2 incompatible with v1) plus webhooks (reply received, email events, meeting booked). Use when building an Instantly API or webhook integration, pushing leads into a campaign or syncing reply/opportunity events to a CRM, your warmup score looks healthy but emails still land in spam, DFY pre-warmed domains arriving burned, the real cost ballooning past the $47 headline once you add Credits and CRM, choosing Growth vs Hypergrowth vs Light Speed, or generating a v2 API key. Do NOT use for cold-email deliverability/warmup strategy across tools (use /sales-deliverability), outbound sequence/copy strategy (use /sales-cadence), or building a prospect list across tools (use /sales-prospect-list).
argument-hint	[describe what you need help with in Instantly]
license	MIT
version	1.0.0
tags	["sales","outbound","cold-email","platform"]

Instantly Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

What are you trying to do?
- A) Build an API/webhook integration — push leads into a campaign, sync reply/opportunity events out
- B) Fix deliverability — warmup looks healthy but emails land in spam, inbox placement, secondary domains
- C) Configure a module — campaigns/sequences, email accounts/warmup, Unibox, Lead Finder, CRM
- D) Understand cost — the $47 headline vs the real stack (Credits + CRM as separate paid products)
- E) Generate a v2 API key (v1 keys don't work on v2) or pick a plan
- F) Fix a problem — DFY domains arriving burned, support delays, buried settings
API or strategy? A concrete Instantly API/webhook/config task → stay here. A cross-tool strategy question (deliverability, sequence copy, list building) → route in Step 2.

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.

Step 2 — Route or answer directly

If the question is about...	Route to...
Cold-email deliverability / warmup / inbox placement strategy across tools	`/sales-deliverability {question}`
Outbound sequence design / copywriting / cadence across tools	`/sales-cadence {question}`
Building/sourcing a prospect list across tools	`/sales-prospect-list {question}`
Contact enrichment / verification strategy	`/sales-enrich {question}`
Connecting Instantly to a CRM/other tools generically (iPaaS)	`/sales-integration {question}`

When routing, give the exact command, e.g. "This is a deliverability question — run: /sales-deliverability my warmup score is green but I'm landing in spam".

Step 3 — Instantly platform reference

Read references/platform-guide.md for the full reference — the module map (what's API vs webhook vs UI-only), the pricing model (warmup free on all plans; Lead Finder Credits and CRM are separate paid products; Unibox is Hyper-Growth+), the data model with JSON shapes, and quick-start recipes (push leads to a campaign; react to replies via webhook; nightly analytics export).

Read references/instantly-api-reference.md for the integration surface — base https://api.instantly.ai/api/v2, Bearer-token auth (scoped, revocable; generate a new v2 key), cursor pagination (starting_after+limit), the endpoint list (campaigns, leads, lead-lists, accounts, analytics, emails, inbox-placement-tests, webhooks, api-keys), the OpenAPI spec URL, and the webhook event types + setup.

Answer using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

Focus on the user's specific situation:

Trust seed tests, not the heat score. Instantly's warmup pool creates synthetic engagement; a green warmup score can coexist with real campaigns landing in spam. Validate with inbox-placement (seed-list) tests before scaling volume, and treat deliverability strategy as /sales-deliverability.
API is v2 + Bearer. Generate a new v2 key (v1 keys are incompatible), call https://api.instantly.ai/api/v2 with Authorization: Bearer, and import the OpenAPI spec for exact schemas. API is on all Outreach plans.
Webhooks over polling. Subscribe to reply_received / status events (meeting booked, not interested) and make your endpoint idempotent with retries; don't poll /emails. Webhooks may need a higher tier.
Model the true cost. The Outreach seat price excludes Lead Finder (Credits) and CRM — both separate paid products. The real Growth stack is ≈$118/mo, not $47.
Vet DFY infrastructure. Done-for-you pre-warmed domains/inboxes sometimes arrive with poor reputation (or get provider-disabled). Run your own placement test on them before trusting the heat score.
Spread the sending. Many low-volume inboxes across secondary domains beat blasting one; SISR rotates IPs/servers but per-account daily caps still apply.

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research (2026-06) — review these, especially pricing and plan-gated features, which change.

Warmup score ≠ real inbox placement. The #1 complaint: green heat scores while live emails hit spam. The warmup pool's synthetic engagement doesn't guarantee placement with real prospects — verify with seed tests.
The $47 price is not the real cost. Lead Finder (Credits) and CRM are separate paid products; a functional stack is ~$118/mo on Growth. Budget accordingly.
API v2 is incompatible with v1. You must generate a brand-new v2 key; v1 keys and payloads won't work on v2 endpoints.
DFY pre-warmed domains can arrive burned. A frequently-cited issue — heat scores read 90+ while real placement collapses; some Google accounts get disabled. Test before sending at volume.
Unibox and (likely) webhooks are tier-gated. Unibox is Hyper-Growth+; webhook access is reported to need a higher tier than the entry plan — verify on your plan before building.
Support and UX friction. Slow support and settings buried across panels are common review themes; budget time for setup and don't expect fast ticket resolution.
Pagination is cursor-based. Use starting_after+limit, not page numbers; back off on 429.
Custom variables drive personalization. Put merge data in custom_variables on the lead so sequence merge tags resolve — missing variables send blank or fallback text.

Related skills

/sales-deliverability — Cold-email deliverability, warmup, and inbox-placement strategy across tools (Instantly's biggest strength and its #1 pain point)
/sales-cadence — Outbound sequence design, multichannel cadences, and copywriting across tools
/sales-prospect-list — Building and sourcing prospect lists (Instantly's Lead Finder is one source)
/sales-enrich — Contact enrichment and email verification
/sales-integration — Connecting Instantly to a CRM/other tools via webhooks/Zapier
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: Push leads into a campaign and react to replies (developer/automation)

User says: "When someone downloads my lead magnet, add them to my Instantly campaign and notify me when they reply." Skill does: Walks Recipe 1 — POST /api/v2/leads with email + custom_variables + the campaign id, authed with Authorization: Bearer (a v2 key). Then Recipe 2 — register a reply_received webhook (Settings → Integrations → Webhooks) that posts to Slack/creates a CRM task, with idempotent handling. Notes v1 keys won't work and webhooks may need a higher tier. Result: Leads flow into the campaign and replies trigger real-time follow-up.

Example 2: Warmup is green but I'm landing in spam

User says: "Instantly says my warmup health is 95% but my campaign still goes to spam." Skill does: Explains the warmup pool generates synthetic engagement that doesn't equal real-prospect placement — the platform's most-reported gap. Recommends running an inbox-placement (seed-list) test, checking SPF/DKIM/DMARC + custom tracking domain, lowering per-inbox volume, and spreading across secondary domains. Routes the deeper playbook: "run: /sales-deliverability warmup is green but I'm in spam on Instantly." Result: User stops trusting the heat score alone and gets a real placement-diagnosis path.

Example 3: Is the $47 plan really $47?

User says: "Growth is $47/mo — is that all I'll pay to run cold email?" Skill does: Clarifies that warmup is free, but the Lead Finder (Credits) and CRM are separate paid products, so a working stack is ~$118/mo on Growth. Breaks down what each add-on buys, notes Unibox is Hyper-Growth+, and frames pricing as best-effort to verify on the live page. Result: User budgets the true cost instead of the headline.

Troubleshooting

My API calls return 401/unauthorized

Symptom: Every request is rejected. Cause: Using a v1 key on v2 (they're incompatible), a missing Authorization: Bearer header, or a key without the needed scope. Solution: Generate a fresh v2 key in-app with the right scopes, send it as Authorization: Bearer YOUR_KEY against https://api.instantly.ai/api/v2, and confirm API access is enabled on your Outreach plan. Import the OpenAPI spec to match request shapes.

My emails land in spam despite a healthy warmup score

Symptom: Warmup dashboard is green; real campaigns hit spam. Cause: The warmup pool's engagement is synthetic and doesn't guarantee placement with actual prospects; auth records, sending volume, or a burned domain can still tank you. Solution: Run an inbox-placement seed test, verify SPF/DKIM/DMARC + a custom tracking domain, reduce per-inbox daily volume, warm new domains longer, and spread across secondary domains. For the full diagnosis, use /sales-deliverability.

My webhook isn't firing / I can't find it

Symptom: No events arrive, or there's no webhook option. Cause: Webhook access may be gated to a higher Outreach tier, the endpoint isn't public HTTPS, or no events were selected for the campaign scope. Solution: Confirm your plan includes webhooks, add the webhook under Settings → Integrations → Webhooks (or POST /api/v2/webhooks) with an HTTPS endpoint and the right event types, send a test, and implement retries + idempotency on your side so transient failures don't drop events.