Outreach Pipeline

Manage sales leads and outreach by tracking follow-ups, logging contacts, advancing stages, and generating weekly pipeline reports.

Security Scan

The plugin implements a local lead-tracking pipeline that matches its description: it stores data locally in LanceDB, exposes the stated tools, and does not request credentials or reach out to external endpoints — the main issue is a minor path-handling bug that can cause data to be written at a surprising location.

Purpose & Capability

Name/description match the implementation: tools for creating/updating leads, logging contacts, scheduling follow-ups, exporting/reporting, and computing stats. Declared dependencies (@lancedb/lancedb, @sinclair/typebox) and local LanceDB storage are coherent with an on-device outreach pipeline.

Instruction Scope

SKILL.md simply instructs the agent how and when to call the provided lead_* tools (e.g., lead_due at session start, lead_contact after outreach). It does not instruct reading unrelated files, accessing unexpected environment variables, or sending data to unknown endpoints. It suggests using a Notion skill for report writing but does not itself attempt network I/O.

Install Mechanism

No install spec is provided (instruction-only plugin) and the package files show normal npm dependencies from the registry. There are no downloads from untrusted URLs or extract steps. Using @lancedb is expected for local DB storage; this is a moderate-but-expected dependency.

Credentials

The skill requests no environment variables, no external credentials, and no config paths beyond a local dataDir (configurable). That is proportionate for a local lead management plugin. The package and code do not access other services or secret-bearing environment variables.

Persistence & Privilege

The plugin stores data on disk (expected). However, there is a bug in resolveDataDir: when a path begins with '~' (the default), the code uses join(homedir(), raw.slice(1)). Because the slice includes a leading '/', path.join may treat the second segment as absolute and resolve to '/.openclaw/...' (root) instead of the user's home directory. That could result in the plugin attempting to create directories at the filesystem root (permission issues or unexpected writes). This is a quality/security concern to address before enabling in production.

Assessment

This plugin appears to do what it claims: local lead tracking with no external network calls or secret requirements. Before installing or enabling it: 1) Fix or override the data directory: either patch resolveDataDir or set plugin config.dataDir to a full absolute path inside your home directory to avoid accidental writes at '/' (for now, avoid accepting the default if you don't want root-level files). 2) Confirm Node 18+ (LanceDB requirements). 3) Review and test in a safe environment (local dev user) to verify data is stored where you expect. 4) Remember the plugin stores potentially sensitive contact data locally—treat that directory accordingly (permissions, backups). 5) If you want to limit risk, run it with the plugin disabled for autonomous invocation until you are comfortable; note the plugin does not request credentials and does not include network exfiltration behavior in the code.

Finch Outreach - Lead Pipeline

You have access to a full outreach and lead tracking pipeline via the lead_* tools. Use them to manage the sales funnel for digital products and services.

Session Start

Always call lead_due first to check for overdue follow-ups. Handle the most overdue leads before starting new outreach.

After Sending Outreach

Every time you send an email (via gog/gmail), post on a forum, or DM someone:

1. Call lead_contact to log the interaction (type, channel, summary).
2. Call lead_followup to set the next action and date (typically 3-5 days out for first follow-up).

After Receiving a Reply

1. Call lead_contact to log the inbound message.
2. Call lead_stage to advance the stage (e.g., contacted -> replied).
3. Call lead_followup to schedule the next step.

Payment Confirmed

When a payment is confirmed via the payment plugin:

1. Call lead_contact with type payment_received.
2. Call lead_stage to move to won.
3. Call lead_update to set actualValue.

Follow-up Cadence

• First follow-up: 3 days after initial contact.
• Second follow-up: 5 days after first follow-up.
• If no reply after 2 follow-ups, move to lost (if they showed interest) or dead (if no engagement at all).

Weekly Report

At the end of each week:

1. Call lead_stats for pipeline summary.
2. Call lead_export with format markdown for the Notion report.
3. Write the report to Notion via the notion skill.

Stage Flow

identified -> researched -> contacted -> replied -> negotiating -> won
                                      \-> lost (can re-engage -> contacted)
                         any stage -> dead (terminal)

Tips

• Use tags to group leads by campaign, product, or priority.
• Set estimatedValue when creating leads to track pipeline value.
• Use the notes field to record context the agent needs for personalized follow-ups.
• Use lead_search with the due flag to find actionable leads.