Description

Open-source B2B AI SDR template. 7-layer context system with 10-stage sales pipeline, 4-layer anti-amnesia memory, 13 automated cron jobs, WhatsApp IP isolat...

README (SKILL.md)

B2B SDR Agent — AI Sales Development Representative

Name: B2B SDR Agent
Author: ipythoning

Turn any B2B export business into an AI-powered sales machine. Full-stack SDR that handles lead capture → qualification → follow-up → quoting → closing across WhatsApp, Telegram, and email.

7-Layer Context System

Layer	File	Purpose
Identity	IDENTITY.md	Company name, role, product catalog
Soul	SOUL.md	Personality, values, communication rules
Workflow	AGENTS.md	10-stage sales pipeline with stage gates
User	USER.md	Owner profile, ICP scoring, admin whitelist
Heartbeat	HEARTBEAT.md	13-item pipeline inspection (cron)
Memory	MEMORY.md	4-layer anti-amnesia protocol
Tools	TOOLS.md	CRM, channels, integrations

Key Features

10-Stage Sales Pipeline: Cold Lead → Engaged → Qualified → Proposal → Negotiation → Closed
4-Layer Memory: L1 pinned context, L2 session KV, L3 vector search, L4 CRM snapshots
13 Cron Jobs: Auto heartbeat, follow-up reminders, lead scoring, pipeline reports
Multi-Channel: WhatsApp, Telegram, Email — with channel-specific strategies
WhatsApp IP Isolation: Per-tenant Cloudflare WARP proxy for multi-tenant deployments
Human-Like Conversations: SDR humanizer skill for natural, trust-building messages
Operator Bilingual Mode (opt-in): English to customers + Chinese self-chat sync for non-English operators, enable via operator_bilingual: true in IDENTITY.md

Deploy

# One-click deploy
cp deploy/config.sh.example deploy/config.sh
# Edit config.sh with your server, API keys, and channel settings
./deploy/deploy.sh your-client-name

IP Isolation (Multi-Tenant)

Each tenant gets a unique Cloudflare exit IP so WhatsApp sees independent devices:

./deploy/ip-isolate.sh tenant-name

Architecture: tenant → wireproxy (SOCKS5, ~4MB) → WARP account → unique Cloudflare IP

Skills Included

sdr-humanizer — Human-like conversation rules
delivery-queue — Async message delivery with retry
lead-discovery — AI-driven lead search and ICP scoring
quotation-generator — PDF proforma invoice generation
chroma-memory — Per-turn conversation memory with ChromaDB
telegram-toolkit — Telegram-specific SDR strategies
graphify — Knowledge graph for product catalog, customer intelligence, and market research

Requirements

Linux server (Ubuntu 20.04+)
Node.js 18+
AI model API key (OpenAI, Anthropic, Google, etc.)
OpenClaw gateway

Links

Usage Guidance

Do not run the deploy/install scripts or give secrets to this skill until you perform a manual audit. Actionable checks: - Verify what deploy.sh and install.sh will do: open the scripts and review every external network call, package install, and file-write. Run them only in an isolated VM or container. - Inventory required secrets: the repo references MEMOS_API_KEY, AI provider keys, WEBHOOK_SECRET, Cloudflare/WARP credentials, and implied Gmail access. Ask the publisher to list required env vars in registry metadata; do not provide high-privilege credentials (owner/root, primary Gmail) — create scoped service accounts with least privilege. - Review ip-isolate.sh carefully: wireproxy / WARP setup will change network routing and requires provider keys; ensure you trust the WARP account and understand tenant isolation design. - Audit data flows: the skill stores per-turn conversation data in external services (MemOS, ChromaDB). Confirm retention, encryption, and access controls meet your privacy/compliance needs. - Treat automatic system-prompt injection, cron jobs, and webhook endpoints as sensitive: require manual human approval before enabling cron/webhook ingress or automatic prompt modifications. - If unsure, run the code in an ephemeral sandbox (container) with no real secrets and monitor outbound connections before deploying to production. If you want, I can highlight specific lines in deploy scripts and the ANTI-AMNESIA/Memory API code that you should review first.

Capability Analysis

Type: OpenClaw Skill Name: b2b-sdr-agent Version: 3.6.0 The skill bundle is classified as suspicious due to high-risk configuration changes and potential supply chain risks. The deployment script (deploy/deploy.sh) automatically disables human-in-the-loop approvals for agent tool execution by setting 'ask': 'off' in the exec-approvals.json configuration, which significantly increases the risk of Remote Code Execution (RCE) via prompt injection. Additionally, both deploy/deploy.sh and skills/graphify/SKILL.md instruct the system to install a Python package named 'graphifyy', which appears to be a typosquatted version of the legitimate 'graphify' library. The bundle also includes telemetry pings to pulseagent.io in install.sh and fetches remote binaries (wgcf, wireproxy) in deploy/ip-isolate.sh, which are common indicators of suspicious installer behavior.

Capability Tags

cryptorequires-walletcan-make-purchases

Capability Assessment

⚠ Purpose & Capability

The SKILL.md describes a B2B SDR agent (OpenClaw integration, multi-channel outreach, memory stack). However the repository includes deployment scripts (deploy/*.sh, install.sh), ip-isolate.sh (Cloudflare WARP / wireproxy logic), MemOS/ChromaDB integration code, and auto-install instructions (Python, graphify) that would require credentials and system/network privileges. The registry metadata declares no required env vars or binaries, which is inconsistent with the documented requirements (MEMOS_API_KEY, AI model keys, WEBHOOK_SECRET, Cloudflare/WARP credentials, Gmail/Google credentials for mailbox scanning). These additional requirements are plausible for the described product, but they are not declared up-front — that's an incoherence the user should be aware of.

⚠ Instruction Scope

SKILL.md + ANTI-AMNESIA.md instruct the agent to: inject structured memory into the System Prompt, run post-conversation hooks or minute-level cron jobs, read and write MemOS via an API key (explicit code sample), store per-turn data into ChromaDB, trigger proactive compaction when tokens exceed thresholds, and run deployment scripts that auto-upload local skills and install packages. Documentation also references scanning Gmail and enabling webhook ingress. These instructions access and transmit potentially sensitive user data to external services, modify prompt/system context automatically, and run recurring background jobs — all beyond a simple 'instruction-only' helper. The docs include explicit automation of system-prompt injection and cron-based processing, which increases the risk surface.

⚠ Install Mechanism

Although declared as instruction-only (no install spec in registry), the repo contains multiple shell scripts (deploy/deploy.sh, install.sh, ip-isolate.sh, skills/*/deliver.sh) and JS modules that the deploy process will run. The changelog and README state deploy.sh auto-installs Python and third-party packages (graphify) and auto-uploads local skills. Running those scripts can write files, install software, and modify the OpenClaw workspace/gateway — effectively acting as an installer. There is no single trusted-release-url install mechanism in the registry metadata and no declaration of what the deploy scripts will do to the host, so executing them without review is risky.

⚠ Credentials

Registry metadata lists no required env vars, but repository docs and code explicitly reference multiple secrets and env vars: MEMOS_API_KEY, MEMOS_NAMESPACE, CHROMA_COLLECTION, WEBHOOK_SECRET (for webhook ingress), AI provider keys (OpenAI/Anthropic/Google), Cloudflare WARP/WireProxy credentials, and implied Gmail/Google credentials for mailbox scanning. This is a disproportionate set of credentials given the registry declaration. Several environment variables named in docs would grant broad access to external systems and stored customer data; they should be explicitly declared and justified before installation.

ℹ Persistence & Privilege

The skill is not marked always:true and can be user-invoked (normal). However deploy scripts claim to auto-upload and enable many local skills and to configure webhook endpoints and cron jobs. That means installing/running the repo can create persistent automation (scheduled jobs, webhooks, gateway endpoints) and modify workspace configuration. This persistent presence is plausible for a production SDR agent but requires explicit admin review and controlled secrets/allowlists before enabling.

Version History

v3.6.0

feat: graphify knowledge graph integration + bilingual mode opt-in

v3.4.0

feat: WhatsApp IP isolation for multi-tenant deployments via per-tenant Cloudflare WARP proxy.

v3.3.0

feat: dual-threshold compression (50% background save + 65% compress), recency-weighted search ranking, expand command to recover compressed turns, score+0.5 bugfix

v3.2.0

v3.2.0: 4-layer anti-amnesia, Telegram best practices, 13 cron jobs

v3.0.0

v3.0: 3-layer Anti-Amnesia system (MemOS + Proactive Summary + ChromaDB). AI SDR now remembers every customer, quote, and commitment across sessions. Includes full implementation spec with code, prompts, cron config, and verification checklist.

v2.0.0

Major upgrade: 10-stage sales pipeline (was 8), 10 automated cron jobs, 3-engine memory architecture, dynamic ICP scoring, multi-channel orchestration (WhatsApp+Email+Telegram), 3-layer enrichment pipeline via Jina AI, timezone-aware scheduling, new skills (lead-discovery, quotation-generator)

v1.0.1

Fix: add missing CRM Entry stage to match 8-stage workflow

v1.0.0

Initial release — open-source AI SDR template for complete B2B sales pipeline automation. - Supports lead capture, BANT qualification, quoting, negotiation, reporting, and lead nurture via WhatsApp, Telegram, and email. - Features a modular 7-layer context architecture, each customizable for your business. - Includes automated pipeline inspection, CRM integration, and memory management layers. - Built on OpenClaw and tested with real B2B exporters. - Companion skills and managed deployment options available for enhanced functionality.

Metadata

Slug b2b-sdr-agent

Version 3.6.0

License MIT-0

All-time Installs 1

Active Installs 1

Total Versions 8

Frequently Asked Questions

What is B2B SDR Agent?

Open-source B2B AI SDR template. 7-layer context system with 10-stage sales pipeline, 4-layer anti-amnesia memory, 13 automated cron jobs, WhatsApp IP isolat... It is an AI Agent Skill for Claude Code / OpenClaw, with 295 downloads so far.

How do I install B2B SDR Agent?

Run "/install b2b-sdr-agent" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is B2B SDR Agent free?

Yes, B2B SDR Agent is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does B2B SDR Agent support?

B2B SDR Agent is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created B2B SDR Agent?

It is built and maintained by iPythoning (@ipythoning); the current version is v3.6.0.

More Skills

B2B SDR Agent