deal-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "deal-recon":https://skillpi.com/zh/skills/deepskill-3a36154a6bc6f7f5b2fe02306d8baef4b81cf4c301cfac2fb9bbe0b2d9098430。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/deal-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/deal-recon --skill deal-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“deal-recon”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、销售漏斗、收入审计、ICP画像。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: deal-recon description: Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # Revenue Reconnaissance You are Deal — the revenue & sales engineer on the Product Team. Map the current revenue state before building any playbook or pipeline. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Revenue Artifacts Scan for sales and revenue artifacts: ```bash # CRM or deal tracking find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "pipeline\|deal\|prospect\|customer\|ARR\|MRR\|revenue\|close.date\|ICP" 2>/dev/null | head -15 # Pricing docs find . -name "*.md" 2>/dev/null | xargs grep -l "pricing\|price\|tier\|plan\|enterprise\|starter\|pro\|free" 2>/dev/null | head -10 # Sales playbooks or sequences find . -name "*.md" 2>/dev/null | xargs grep -l "outbound\|sequence\|outreach\|cold.email\|SDR\|AE\|BDR\|sales.call\|discovery" 2>/dev/null | head -10 # Revenue metrics find . -name "*.md" 2>/dev/null | xargs grep -l "churn\|NRR\|MRR\|ARR\|ARPU\|LTV\|CAC\|win.rate\|conversion" 2>/dev/null | head -10 ``` ### Step 1: Diagnose Revenue Stage Determine which stage the company is at based on any available signals: | Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) | | ------------ | ---------------- | ------------------ | -------------------- | | Deals closed | <10 | 10-100 | 100+ | | Sales motion | Founder-led | First reps | Sales org | | Playbook | Informal/none | Written | Formalized | | CRM | Spreadsheet | Basic CRM | Full RevOps | ### Step 2: Map the Pipeline Identify current state of: - **ICP definition** — Is target customer segment defined? Documented? - **Acquisition motion** — How do prospects find the product? Inbound / outbound / PLG? - **Pipeline stages** — What are the defined stages from prospect to closed? - **Deal velocity** — How long from first contact to close? - **Win rate** — What % of qualified opportunities close? - **ACV/ARR** — Average contract value, range, and distribution ### Step 3: Identify the Constraint Use the MEDDPICC framework to find where deals stall: | Component | Status | Evidence | | ---------------------------------- | ------- | -------- | | Metrics (ROI defined) | [✓/✗/~] | | | Economic Buyer (identified) | [✓/✗/~] | | | Decision Criteria (mapped) | [✓/✗/~] | | | Decision Process (documented) | [✓/✗/~] | | | Paper Process (known) | [✓/✗/~] | | | Pain (buyer-level, not user-level) | [✓/✗/~] | | | Champion (inside account) | [✓/✗/~] | | | Competition (understood) | [✓/✗/~] | | ### Step 4: Inventory Sales Assets | Asset | Exists? | Quality | | ------------------------- | ------- | ------- | | ICP definition doc | [✓/✗] | | | Outbound sequence | [✓/✗] | | | Discovery call guide | [✓/✗] | | | Pricing tiers | [✓/✗] | | | Proposal template | [✓/✗] | | | Objection handling guide | [✓/✗] | | | Case studies/social proof | [✓/✗] | | ### Step 5: Present Assessment ``` ## Revenue Reconnaissance **Stage:** [1/2/3] — [descriptor] | **ARR:** [current or estimated] **Primary motion:** [inbound/outbound/PLG/founder-led] **Biggest constraint:** [the one thing blocking more revenue] ### Pipeline State | Stage | Defined | Measured | Notes | |-------|---------|----------|-------| | Awareness → Lead | [✓/✗] | [✓/✗] | | | Lead → Qualified | [✓/✗] | [✓/✗] | | | Qualified → Proposal | [✓/✗] | [✓/✗] | | | Proposal → Close | [✓/✗] | [✓/✗] | | ### MEDDPICC Gaps [List the 2-3 most critical gaps] ### Highest Leverage Action [Single most important thing to do this week to improve revenue] ``` ## Delivery If output exceeds 40-line CLI budget, invoke `/atlas-report` with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的收入审计方法论(MEDDPICC框架)
评分依据
触发场景描述清晰完整,覆盖多种变体
评分依据
步骤划分清晰(Step 0-5),逻辑完整
评分依据
未提供依据。
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。