跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

deal-pipeline-reconstructor

Rebuild a sales pipeline from Littlebird records. Use to identify stage, evidence, next action, and stale deals. Read README.md for the guide map.

Mario Aldayuz / Littlebird · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add legioncodeinc/vibe-coding-tools --skill deal-pipeline-reconstructor

技能说明


name: deal-pipeline-reconstructor description: "Rebuild a sales pipeline from Littlebird records. Use to identify stage, evidence, next action, and stale deals. 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)"

Deal Pipeline Reconstructor

You sell. You do not maintain a CRM. The CRM is empty, or it has four deals in it from March and one of them closed.

But the activity is all there. The DM from someone asking if you have capacity. The discovery call you took on Tuesday. The quote you built in a spreadsheet and pasted into WhatsApp. The calendar hold with a name you half recognise. The follow-up you meant to send eleven days ago.

This skill assembles that into the board you never built: every deal placed at a stage, with the evidence that put it there, how long each one has been silent, and which ones are dying.

Every stage on this board is an inference. The skill shows its reasoning for each placement and asks you to confirm before the board is treated as real. That is not timidity. The forecasting literature's consistent finding is that human judgment combined with mechanical method beats either alone (references/research/distilled-b2b-pipeline-management.md, section 3).

The board is internal. Nothing here goes to a prospect.


Purpose

Turn captured sales activity into a stage-by-stage deal board with last-touch recency, a ranked going-cold list, and one next action per deal, for an operator whose pipeline currently exists only in their memory.


Capability gate

This skill requires the Littlebird MCP on a Power or Pro plan.

  1. LIST the tools actually available in this session. Do not assume tool names. Use the real names you find.
  2. 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 memory or guesswork.
  3. If the tools are present but return plan errors, call the subscription status tool and report the plan gate.

Tool surface, parameters, and return shapes are in references/littlebird-mcp-reference.md. Read it before writing any query.


Littlebird MCP calls used

ToolUsed for
LB_INTERNAL_LIST_MEETINGSSales, discovery and demo calls across the window. Also run with a FUTURE end_date to get upcoming prospect holds. There is no separate calendar tool.
LB_INTERNAL_SEARCH_MEETINGSTopic search across transcripts and summaries for pricing, scope, proposal and contract discussion
LB_INTERNAL_GET_MEETINGThe structured summary per call: Decisions, Action Items with owners, Risks and Open Questions, For You
LB_INTERNAL_GET_MEETING_TRANSCRIPTOnly where exact wording matters and the summary is insufficient. Expensive, and weakly diarized.
search_user_context with data_source: messagesProspect threads, inbound enquiries, quotes pasted into chat
search_user_context with data_source: snapshotsProposals, quotes, contracts, e-signature screens, and any CRM screen on display
search_user_context with data_source: summariesCheap compressed day view, for filling gaps in the timeline
LB_INTERNAL_GET_SUBSCRIPTION_STATUSThe capability gate above, and the routine limit check
LB_INTERNAL_CREATE_ROUTINEThe weekly pipeline watcher, offered with approval. See Routine cadence.
LB_INTERNAL_GET_ROUTINE_REPORTSRead the watcher's own past reports before building a board
LB_INTERNAL_LIST_ROUTINES / LB_INTERNAL_GET_ROUTINE_CONFIG / LB_INTERNAL_UPDATE_ROUTINECheck whether the watcher already exists and amend it rather than duplicating

Anything outside this table is a different MCP server. Gmail, HubSpot, Salesforce, Pipedrive, GoHighLevel and the rest are separate connectors that may or may not be present. See references/board-output-and-export.md, section 5.


Trigger

Run this when the user says any of: "what deals do I have open", "rebuild my pipeline", "my CRM is empty", "who am I about to lose", "which deals went cold", "what did I quote and to whom", "build my deal board", "who hasn't replied to my proposal", "I've lost track of my deals", "what's in my pipeline".

Also run it on the Monday after the weekly watcher routine posts a report.


Routine cadence

Weekly, plus on demand. The routine observes and reports. The Cowork session builds the board. Offer to create the routine per the Routine wiring section below.


Process

Step 1: Frame the pipeline. Do not guess.

Ask with AskUserQuestion, in one batch:

  1. What do you sell. One line. It drives every query in step 2.
  2. Typical deal size and typical time from first conversation to signed. Used to calibrate going-cold thresholds. "I don't know" is an acceptable answer and switches the skill to the published defaults.
  3. The window. Default 90 days. Offer 60 and 90, and a custom range. 60 days for a fast transactional cycle, 90 for anything with a proposal step.
  4. Any deals you already know about. Names only. These become seeds that get looked up directly, and any deal the retrieval MISSES that the user named is a coverage finding worth reporting.
  5. Where the board should be written. Default: the working directory.

Step 2: Retrieval brief

Run MULTIPLE NARROW queries, not one broad one. Parallel narrow beats one broad: it scores better and avoids the oversized-result file dump (references/littlebird-mcp-reference.md, retrieval patterns). Every query is bounded by the window from step 1. Substitute what the user actually sells.

A. Calls. LB_INTERNAL_LIST_MEETINGS across the full window, then LB_INTERNAL_SEARCH_MEETINGS for:

阅读完整来源 ↗