Overview

Automated lead capture and lifecycle management for Claw-based agents, storing leads and conversation history in Supabase and triggering Make.com email automations from initial contact through qualification.

Key Advantages

1.End-to-end lead flow: capture, track, and qualify leads in one integrated skill.

2.Persistent storage in Supabase with structured leads and conversations tables for later analytics and reporting.

3.Built-in integration point with Make.com to trigger auto-reply email sequences on lead creation.

4.Clear lifecycle management via status updates (e.g., new → qualified → won/lost).

5.Supports manual conversation logging so agents can keep a complete interaction history per lead. - Provides filters and listing to help prioritize by status, priority, and date.

Use Cases

Automating lead capture from chatbots or virtual assistants into a central CRM-like database.
Triggering immediate email auto-responses to inbound leads while preserving all details for sales follow-up.
Running qualification workflows where AI agents update lead status based on conversation outcomes.
Centralizing multi-channel inquiries (chat, email, phone) into a single lead + conversation record.
Building lightweight sales pipelines for small teams not yet using a full CRM, but needing structured tracking.

Evaluation Scores

7.6

/ 10

Reliability

7.6

Functionality

8.6

Usability

8.4

Safety

5.5

Performance

8.0

Compatibility

7.5

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

7.6/103/19/2026win32-x64

▼

OS: win32-x64LLM: anthropic/claude-opus-4.6

**Quick judgement** A solid, specialized skill for turning Claw-based conversations into trackable leads with automated email follow-up. It behaves like a mini-CRM backed by Supabase and Make.com, well-suited for sales/chat agents that need structured lead tracking and quick auto-replies. **What it does well** - Captures lead data (email, contact info, custom fields) and stores it in Supabase. - Immediately triggers Make.com webhooks so a predefined email workflow can respond within ~60 seconds. - Exposes a clear lifecycle: create leads, list/filter them, retrieve full details, update status (e.g., `qualified`, `won`, `lost`), and log conversation messages. - Provides an `automation_status` check to verify email workflows actually fired. - Designed for agent usage patterns (capture → verify automation → qualify → log conversations). **Key risks / limitations** - **Security of Supabase Service Role Key**: The config explicitly requires the Supabase *service-role* key (full DB access). If this key is exposed in logs, prompts, or misconfigured environments, it poses a significant security and data-breach risk. - **PII handling**: Emails, names, and phones are stored; you must handle privacy, consent, and data retention for your jurisdiction (GDPR/CCPA etc.). - **External dependency on Make.com & Supabase**: Reliability and latency depend on those services. Automation timeouts (>5 minutes) are explicitly a possible error. - **Not a full CRM**: While it covers core lead tracking, advanced CRM features (complex pipelines, multi-owner assignments, reporting dashboards) are not inherent and must be built on top. **Recommended scenarios** - AI chat or website bots that need to reliably turn interested users into structured leads with instant auto-reply emails. - Early-stage or small teams who want a simple, API-driven lead inbox without adopting a heavyweight CRM. - Integrators who already use Supabase + Make.com and want a standardized way for agents to write/read leads and conversations. - Prototyping lead funnels where fast implementation matters more than deep CRM features. Use this skill when you control a Supabase project and Make.com scenario, can securely manage a service-role key, and want your Claw agents to behave like a lightweight, automated sales desk.

lead-generating