lead-harvester
Find hand-raisers in a comment-keyword campaign. Use to qualify leads, deduplicate, and prepare CRM handoff. Read README.md for the guide map.
Mario Aldayuz / Littlebird · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add legioncodeinc/vibe-coding-tools --skill lead-harvester技能说明
name: lead-harvester description: "Find hand-raisers in a comment-keyword campaign. Use to qualify leads, deduplicate, and prepare CRM handoff. Read README.md for the guide map." license: AGPL-3.0-or-later compatibility: Claude Cowork, Claude Code 2.1 or newer, Cursor 2.4 or newer, Codex metadata: hive-tier: standalone version: "1.0.0" author: "Mario Aldayuz / Littlebird" requires: "Littlebird MCP (Power or Pro plan)"
Lead Harvester
Purpose
You run a "comment KEYWORD to get it" campaign. Dozens or hundreds of people raise a hand. The platform shows them to you once, as a notification, and then they are gone. Some commented. Some skipped the comment and just DM'd you. Some sent a friend request. Some only reacted. A week later you have a vague memory of nine names and a folder of unanswered messages, one of which says "I DMd you and you haven't responded yet".
This skill reconstructs that list from what Littlebird already captured, ranks it by how hard each person waved, and writes the first message for every one of them.
It drafts. It does not send, and it does not automate platform actions. That is a
design decision, not a limitation, and references/platform-rules.md has the evidence.
It is the post-mortem. comment-to-crm-piper is the daily drip. Run this one after a
launch to reconstruct the whole roster with scoring and segmentation. Run the sibling every
day so the roster never has to be reconstructed. They share the extraction and matching
logic, and the sibling points at this skill's guides rather than duplicating them.
Littlebird MCP calls used
Real tool names, verified against references/littlebird-mcp-reference.md. LIST the tools
available in this session before calling anything and use the names you actually find. Do
not assume a tool exists because it is named here.
| Tool | Used for |
|---|---|
search_user_context | Every retrieval pass in step 3. search_queries carries the snapshot-side queries: notification pages, expanded comment threads, reaction lists, friend and connection request screens, and the campaign post itself. search_queries_messages carries the direct message and message request queries. date_range is bounded to the campaign window extended 2 days past the end date. filters sets data_source to snapshots or messages and app to chrome or the platform's native client. |
LB_INTERNAL_LIST_ROUTINES | Checking whether the campaign watcher already exists before offering to create one. |
LB_INTERNAL_GET_ROUTINE_REPORTS | The handoff. Reading the watcher's own past reports before step 3, for the day-by-day timeline and the running gap count. |
LB_INTERNAL_GET_ROUTINE_CONFIG | Reading the current routine before any update, because prompt and schedule each REPLACE the whole field. |
LB_INTERNAL_CREATE_ROUTINE | Creating the campaign watcher, from an interactive session only. |
LB_INTERNAL_UPDATE_ROUTINE | Rescheduling or pausing it later, from an interactive session only. |
LB_INTERNAL_GET_SUBSCRIPTION_STATUS | Explaining a plan gate or a routine-count limit. |
Not used, and deliberately. The meeting tools LB_INTERNAL_LIST_MEETINGS,
LB_INTERNAL_SEARCH_MEETINGS, LB_INTERNAL_GET_MEETING and
LB_INTERNAL_GET_MEETING_TRANSCRIPT are real, but a comment-keyword campaign lives on
social surfaces rather than in calls, so this skill does not touch them. There is also no
Littlebird tool that searches past Littlebird chat conversations and no calendar tool.
Anything that looks like search_chats or get_calendar is not real; use
search_user_context and say so.
CRM and platform tools are NOT Littlebird tools. GoHighLevel, HubSpot, Gmail and the rest are separate MCP servers that may or may not be connected in this session. List the tools first, and degrade to a file or a copy-paste block when a connector is absent.
Trigger
Fires on: who commented my keyword, harvest my campaign leads, who DMd me about the launch, build my outreach list, comment to get it campaign, I missed a bunch of DMs, rank my inbound leads, who raised their hand.
Also fires when the user opens Cowork after a notification from the campaign watcher routine.
Do NOT fire this for the everyday "anyone new since yesterday" question. That is
comment-to-crm-piper.
Routine cadence
On demand is primary. This skill is a campaign post-mortem and most runs are one-off.
The optional watcher runs DAILY during an active campaign window, default
{"frequency": "daily", "time": "17:00"} in the user's local timezone, so the nudge lands
while the window is still open. Offer it only when the user says they run these campaigns
constantly or has a window open right now, and offer to pause or delete it when the campaign
closes.
Offer to create it rather than telling the user to go set it up by hand.
LB_INTERNAL_CREATE_ROUTINE works from an interactive session and is only blocked from
inside a running routine. Show the exact prompt text and the schedule, get approval with
AskUserQuestion, then call it.
The routine OBSERVES and the Cowork session ACTS
(references/littlebird-mcp-reference.md, the Routines-observe Cowork-acts pattern). The
scoring, the ambiguous-merge questions, the drafting and the approval gate all happen in the
interactive session, because a routine cannot run an approval gate. Exact prompt text is in
the routine wiring section below.
Capability gate
This skill requires the Littlebird MCP on a Power or Pro plan.
- LIST the tools actually available in this session. Do not assume tool names. Use the real names you find.
- If no Littlebird tools are present, stop and tell the user the skill needs the Littlebird MCP connected, with a link to https://support.littlebird.ai/docs/mcp/. Do not proceed on capture-free guesswork.
- If the tools are present but return plan errors, call the subscription status tool and report the plan gate to the