[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F5DCKM1MN2PRN6VNGJPYR":3,"skill-same:01M75F5DCKM1MN2PRN6VNGJPYR":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M75F5DCKM1MN2PRN6VNGJPYR","sales-rhythm-tracker",null,"B2B sales pipeline manager powered by the Alibaba Iron Army (阿里铁军) methodology. Use this skill for daily sales briefings, lead management, pipeline health checks, weekly sprint planning, customer follow-up prioritization, and closing strategy. Triggered by phrases like: \"morning sales brief\", \"add lead\", \"pipeline review\", \"who should I call today\", \"weekly sales plan\", \"sales update\", \"close rate\", \"follow up\", \"deal stuck\", \"customer type\", \"sales sprint\".","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeepseekcmo\u002Fsales-rhythm-tracker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: sales-rhythm-tracker\nversion: 1.0.0\nauthor: yinguofeng007\ndescription: >\n  B2B sales pipeline manager powered by the Alibaba Iron Army (阿里铁军) methodology.\n  Use this skill for daily sales briefings, lead management, pipeline health checks,\n  weekly sprint planning, customer follow-up prioritization, and closing strategy.\n  Triggered by phrases like: \"morning sales brief\", \"add lead\", \"pipeline review\",\n  \"who should I call today\", \"weekly sales plan\", \"sales update\", \"close rate\",\n  \"follow up\", \"deal stuck\", \"customer type\", \"sales sprint\".\ntags: [sales, crm, pipeline, b2b, productivity, business, revenue]\ncategory: business\n---\n\n# Sales Rhythm Tracker\n### Powered by the Alibaba Iron Army Methodology (阿里铁军方法论)\n\n> \"Let 80% of your people achieve 80% of the top performer's results — through system, not talent.\"\n> — Alibaba Iron Army Core Principle\n\n---\n\n## What This Skill Does\n\nThis skill transforms your OpenClaw agent into a personal B2B sales coach and pipeline manager. It applies the same methodology that built Alibaba's legendary direct sales force — the \"Iron Army\" that grew Alibaba.com from zero to market dominance across China's SMB sector.\n\nUnlike generic CRM tools, this skill encodes *sales thinking*, not just data storage. Your agent will tell you **who to call, when, why, and how** — based on proven rhythms, not gut feel.\n\n**Data lives locally.** No SaaS subscription. No API keys. Your pipeline in plain markdown files.\n\n---\n\n## The Methodology: Alibaba Iron Army Framework\n\nBefore using this skill, understand the philosophy your agent now operates on:\n\n### Principle 1: The Boiling Water Theory (烧水理论)\nEvery customer relationship is like water heating toward boiling (closing). A first visit gets the water to 70°C. Consistent follow-up brings it to 100°C (close). **A gap that's too long lets the water cool back to cold** — and you restart from scratch. Your agent tracks the \"temperature\" of every lead and alerts you before deals go cold.\n\n### Principle 2: Three-Step Sprint Cycle (三步一杀)\nEvery 4-week cycle follows this rhythm:\n- **Week 1 — Seed (播种)**: Maximum outreach. Volume is the foundation. Target 40+ touches.\n- **Week 2 — Flip (翻牌)**: Filter ruthlessly. Identify the top 30% worth pursuing. Walk away from the rest.\n- **Week 3 — Harvest (采果)**: Close sprint. Push every qualified lead to YES or NO. No gray zones.\n- **Week 4 — Reset (机动)**: Handle onboarding, collect payment, start seeding next cycle.\n\n### Principle 3: The 8-Visit Daily Structure (每日八访)\nA productive sales day consists of:\n- 4 × New customer visits\u002Fcalls (seed phase)\n- 2 × Follow-up visits (nurture phase, 2nd or 3rd contact)\n- 2 × Closing visits (harvest phase, move to YES\u002FNO)\n\n### Principle 4: Four Customer Personality Types (四型客户)\nEvery customer has a dominant style. Matching your approach to their type is the single highest-leverage sales skill:\n\n| Type | Chinese | Traits | What They Need | Your Approach |\n|------|---------|--------|---------------|---------------|\n| **Tiger** | 老虎型 | Direct, decisive, impatient, results-driven | Bottom line, ROI, fast answers | Lead with outcomes. Be brief. Skip small talk. Use data. |\n| **Peacock** | 孔雀型 | Enthusiastic, social, optimistic, status-conscious | Recognition, relationships, exciting vision | Build rapport first. Tell success stories. Be energetic. |\n| **Koala** | 无尾熊型 | Patient, loyal, risk-averse, team-oriented | Safety, proof, support, consensus | Build trust slowly. Provide case studies. Never rush. |\n| **Owl** | 猫头鹰型 | Analytical, precise, systematic, skeptical | Data, accuracy, process, completeness | Prepare detailed answers. Be precise. Address every concern. |\n\n### Principle 5: The Traffic Light System (红黄绿)\nEvery lead gets a status color at each review:\n- 🟢 **Green**: Momentum is healthy. Follow-up on schedule. Keep heating.\n- 🟡 **Yellow**: Stalled. Something slowed down. Needs diagnosis and intervention.\n- 🔴 **Red**: Relationship cooling. Urgent action required or acknowledge as lost.\n\n### Principle 6: Four-Step Sales Conversation (四步销售法)\nEvery customer interaction follows this sequence:\n1. **挖需求 (Uncover)**: Ask questions to understand their real pain. 70% listening, 30% talking.\n2. **抛产品 (Present)**: Match your solution to their specific pain. Not features — outcomes.\n3. **解问题 (Address)**: Handle objections. Every objection is a buying signal in disguise.\n4. **提成交 (Close)**: Ask for the commitment. Silence after asking is your best tool.\n\n### Principle 7: Phone Call Protocol (电话拜访规则)\n- Optimal call length: **3–5 minutes** (maximum 6 minutes)\n- Before every call: Write down your ONE objective for this call\n- Best use cases: Follow-up confirmation, closing push, payment collection\n- After every call: Log the result within 10 minutes while memory is fresh\n\n### Principle 8: ASK Growth System\nEvery sales improvement requires development in three dimensions:\n- **A — Attitude (心态)**: Belief in the product, resilience, ownership mindset\n- **S — Skill (技能)**: Prospecting, questioning, objection handling, closing\n- **K — Knowledge (知识)**: Industry, product, competition, customer context\n\n---\n\n## Pipeline Stages\n\nLeads move through 8 stages. Your agent tracks stage and days-in-stage:\n\n| Stage | Label | Description | Healthy Duration |\n|-------|-------|-------------|-----------------|\n| 1 | `prospect` | Identified, not yet contacted | — |\n| 2 | `connected` | First contact made, initial interest | 1–3 days |\n| 3 | `qualified` | Pain confirmed, budget exists | 3–7 days |\n| 4 | `presented` | Solution presented | 3–7 days |\n| 5 | `proposal` | Formal proposal submitted | 3–10 days |\n| 6 | `negotiation` | Active negotiation on terms | 3–14 days |\n| 7 | `closing` | Final push — YES or NO this week | 1–5 days |\n| 8 | `won` | Closed. Onboarding. Collect payment. | — |\n| 9 | `lost` | Lost. Record reason. Learn. | — |\n\n**Alert rule**: Any lead stuck in the same stage for more than double the healthy duration = 🔴 Red status.\n\n---\n\n## Lead Scoring (0–100)\n\nYour agent automatically scores each lead to prioritize your daily actions:\n\n| Factor | Max Points | How It's Calculated |\n|--------|-----------|---------------------|\n| Stage progression | 25 | Higher stage = more points |\n| Recency of contact | 20 | Last contact \u003C 3 days = 20pts; \u003C 7 days = 10pts; > 14 days = 0pts |\n| Engagement level | 20 | Customer-initiated contact = high; passive = low |\n| Deal size | 15 | Relative to your average deal size |\n| Time pressure | 20 | Customer deadline approaching = high score |\n\n**Score interpretation**:\n- 80–100: 🔥 Hot — close this week\n- 60–79: ✅ Warm — maintain rhythm, don't let cool\n- 40–59: 🟡 Lukewarm — needs intervention or deprioritize\n- Below 40: 🔴 Cold — decide: revive or move on\n\n---\n\n## Commands & Usage\n\n### Daily Commands\n\n**Morning Brief** (run every morning before 9am):\n> \"Morning sales brief\" \u002F \"Who should I call today?\" \u002F \"Sales priorities today\"\n\nAgent will: Scan pipeline → Score all leads → Generate top 3–5 priority actions → Suggest approach for each based on customer type.\n\n**Log Activity** (after every call\u002Fmeeting):\n> \"Log: [customer name] — [what happened] — [next step]\"\n> Example: \"Log: Sarah Chen at TechBridge — she's interested but wants to loop in her CEO — next step: send exec summary by Thursday\"\n\nAgent will: Record activity → Update lead status → Recalculate score → Flag if rhythm is at risk.\n\n**Add New Lead**:\n> \"New lead: [Name] at [Company] — [context]\"\n> Example: \"New lead: David Park at Sunrise Manufacturing — met at trade show, interested in reducing procurement costs\"\n\nAgent will: Create lead profile → Classify personality type from context → Set stage to connected → Add to next morning brief.\n\n**Check Deal Status**:\n> \"How is [customer name] doing?\" \u002F \"Update on [company]\"\n\nAgent will: Pull customer profile → Show stage, score, last contact, temperature → Recommend next action.\n\n### Weekly Commands\n\n**Weekly Sprint Plan** (every Monday morning):\n> \"Weekly sprint plan\" \u002F \"Monday sales planning\"\n\nAgent will: Apply Three-Step Sprint logic to current week in the cycle → Categorize all leads by this week's priority tier → Generate a concrete 5-day action plan → Identify leads that need a YES\u002FNO decision this week.\n\n**Pipeline Health Review** (every Friday):\n> \"Pipeline review\" \u002F \"End of week sales check\" \u002F \"Pipeline health\"\n\nAgent will: Calculate overall pipeline velocity → Flag stalled deals → Identify temperature-cooling risks → Suggest which leads to cut (翻牌) → Project next 2-week revenue likelihood.\n\n**Stuck Deal Diagnosis**:\n> \"Deal stuck: [customer name]\" \u002F \"[Customer] hasn't responded, what do I do?\"\n\nAgent will: Diagnose cause of stall using Iron Army framework → Suggest intervention based on customer type → Provide exact language\u002Fscript for next outreach.\n\n---\n\n## File Structure\n\nThis skill uses local files in your workspace:\n\n```\n~\u002F.openclaw\u002Fworkspace\u002Fsales\u002F\n├── pipeline.md          ← Your CRM: all active leads\n├── activity-log.md      ← Every interaction logged\n├── weekly-sprint.md     ← Current week's plan\n└── closed-deals.md      ← Won\u002Flost deals (for learning)\n```\n\nTo initialize: run `scripts\u002Finit-pipeline.sh` once.\n\n---\n\n## Morning Brief Format\n\nEvery morning brief follows this structure:\n\n```\n📊 SALES MORNING BRIEF — [Date]\nCycle: Week [1\u002F2\u002F3\u002F4] of [Month] Sprint\n\n🔥 TOP PRIORITY TODAY (must-do):\n1. [Customer] — [Stage] — Score: [X] — [Why urgent] — [Recommended action]\n2. [Customer] — [Stage] — Score: [X] — [Why urgent] — [Recommended action]\n\n✅ MAINTAIN RHYTHM (important):\n3. [Customer] — [Stage] — Last contact: [X days ago] — [Action]\n4. [Customer] — [Stage] — Last contact: [X days ago] — [Action]\n\n⚡ SEED TODAY (new outreach):\n- [Target sector\u002Ftype for today's cold outreach]\n\n📈 PIPELINE SNAPSHOT:\n- Active leads: [N]\n- This week's close targets: [N]\n- Deals cooling (>7 days no contact): [N]\n- 🔴 Red alerts: [N]\n```\n\n---\n\n## Weekly Sprint Plan Format\n\n```\n🗓 WEEKLY SPRINT — Week [N] of [Month] — [3-Step Phase]\nPhase: [SEED \u002F FLIP \u002F HARVEST \u002F RESET]\n\nPHASE OBJECTIVE:\n[What this week is about based on the 3-step cycle]\n\nMONDAY — Launch:\nTUESDAY — Deepen:\nWEDNESDAY — Accelerate:\nTHURSDAY — Push:\nFRIDAY — Review & Reset:\n\nTHIS WEEK'S CLOSE TARGETS (need YES or NO):\n1. [Customer] — [Stage] — Closing script: [approach]\n2. [Customer] — [Stage] — Closing script: [approach]\n\nLEADS TO FLIP (qualify or drop):\n- [Customer] — [Reason to decide]\n\nSEED TARGETS (new outreach, 4+ per day):\n- [Target profile for this week]\n\nFRIDAY SUCCESS CRITERIA:\n□ [N] deals moved forward at least one stage\n□ [N] YES or NO decisions obtained\n□ [N] new leads added to pipeline\n```\n\n---\n\n## Stuck Deal Scripts (by Customer Type)\n\n### Tiger (老虎型) — deal stalled:\n> \"I know you're busy, so I'll be direct: the question on the table is X. If we move forward by [date], you get [specific benefit]. If not, I completely understand. Which is it?\"\n\n### Peacock (孔雀型) — deal stalled:\n> \"Hey [name], I was just showing your situation to a colleague and they immediately said this reminded them of [success story]. Made me think — let's get the team together for a quick 20-min call this week. When works for you?\"\n\n### Koala (无尾熊型) — deal stalled:\n> \"I wanted to check in and share something that might help ease the decision. Three other companies in your industry have been through exactly this situation — here's what they found. No rush at all — just want to make sure you have everything you need to feel confident.\"\n\n### Owl (猫头鹰型) — deal stalled:\n> \"I realized I hadn't sent over the complete technical spec and the full pricing breakdown with all variables. Sending that now. Let me know if any number looks different from what you expected — I'd rather address it directly than have any ambiguity.\"\n\n---\n\n## Integration Notes\n\n- Works with any messaging channel (Telegram, WhatsApp, Slack, Discord)\n- No external API required — all data stored locally\n- Pairs well with: `gog` skill (Google Calendar integration for scheduling follow-ups)\n- Compatible with: `memo` (brew) for quick voice-to-text lead logging\n- Daily cron suggested: `0 8 * * 1-5` for automatic morning brief delivery\n\n---\n\n## Quick Start\n\n```bash\n# 1. Install skill\ncp -r sales-rhythm-tracker ~\u002F.openclaw\u002Fskills\u002F\n\n# 2. Initialize your pipeline workspace\n~\u002F.openclaw\u002Fskills\u002Fsales-rhythm-tracker\u002Fscripts\u002Finit-pipeline.sh\n\n# 3. Add your first lead (via your messaging app):\n# \"New lead: [Name] at [Company] — [context of how you met]\"\n\n# 4. Get your first morning brief:\n# \"Morning sales brief\"\n```\n\n---\n\n*Built on the Alibaba Iron Army (阿里铁军) methodology — the sales system that trained 10,000+ B2B salespeople and generated billions in SMB revenue across China.*\n","# Sales Rhythm Tracker\n### Powered by the Alibaba Iron Army Methodology (阿里铁军方法论)\n\n> \"Let 80% of your people achieve 80% of the top performer's results — through system, not talent.\"\n> — Alibaba Iron Army Core Principle\n\n---\n\n## What This Skill Does\n\nThis skill transforms your OpenClaw agent into a personal B2B sales coach and pipeline manager. It applies the same methodology that built Alibaba's legendary direct sales force — the \"Iron Army\" that grew Alibaba.com from zero to market dominance across China's SMB sector.\n\nUnlike generic CRM tools, this skill encodes *sales thinking*, not just data storage. Your agent will tell you **who to call, when, why, and how** — based on proven rhythms, not gut feel.\n\n**Data lives locally.** No SaaS subscription. No API keys. Your pipeline in plain markdown files.\n\n---\n\n## The Methodology: Alibaba Iron Army Framework\n\nBefore using this skill, understand the philosophy your agent now operates on:\n\n### Principle 1: The Boiling Water Theory (烧水理论)\nEvery customer relationship is like water heating toward boiling (closing). A first visit gets the water to 70°C. Consistent follow-up brings it to 100°C (close). **A gap that's too long lets the water cool back to cold** — and you restart from scratch. Your agent tracks the \"temperature\" of every lead and alerts you before deals go cold.\n\n### Principle 2: Three-Step Sprint Cycle (三步一杀)\nEvery 4-week cycle follows this rhythm:\n- **Week 1 — Seed (播种)**: Maximum outreach. Volume is the foundation. Target 40+ touches.\n- **Week 2 — Flip (翻牌)**: Filter ruthlessly. Identify the top 30% worth pursuing. Walk away from the rest.\n- **Week 3 — Harvest (采果)**: Close sprint. Push every qualified lead to YES or NO. No gray zones.\n- **Week 4 — Reset (机动)**: Handle onboarding, collect payment, start seeding next cycle.\n\n### Principle 3: The 8-Visit Daily Structure (每日八访)\nA productive sales day consists of:\n- 4 × New customer visits\u002Fcalls (seed phase)\n- 2 × Follow-up visits (nurture phase, 2nd or 3rd contact)\n- 2 × Closing visits (harvest phase, move to YES\u002FNO)\n\n### Principle 4: Four Customer Personality Types (四型客户)\nEvery customer has a dominant style. Matching your approach to their type is the single highest-leverage sales skill:\n\n| Type | Chinese | Traits | What They Need | Your Approach |\n|------|---------|--------|---------------|---------------|\n| **Tiger** | 老虎型 | Direct, decisive, impatient, results-driven | Bottom line, ROI, fast answers | Lead with outcomes. Be brief. Skip small talk. Use data. |\n| **Peacock** | 孔雀型 | Enthusiastic, social, optimistic, status-conscious | Recognition, relationships, exciting vision | Build rapport first. Tell success stories. Be energetic. |\n| **Koala** | 无尾熊型 | Patient, loyal, risk-averse, team-oriented | Safety, proof, support, consensus | Build trust slowly. Provide case studies. Never rush. |\n| **Owl** | 猫头鹰型 | Analytical, precise, systematic, skeptical | Data, accuracy, process, completeness | Prepare detailed answers. Be precise. Address every concern. |\n\n### Principle 5: The Traffic Light System (红黄绿)\nEvery lead gets a status color at each review:\n- 🟢 **Green**: Momentum is healthy. Follow-up on schedule. Keep heating.\n- 🟡 **Yellow**: Stalled. Something slowed down. Needs diagnosis and intervention.\n- 🔴 **Red**: Relationship cooling. Urgent action required or acknowledge as lost.\n\n### Principle 6: Four-Step Sales Conversation (四步销售法)\nEvery customer interaction follows this sequence:\n1. **挖需求 (Uncover)**: Ask questions to understand their real pain. 70% listening, 30% talking.\n2. **抛产品 (Present)**: Match your solution to their specific pain. Not features — outcomes.\n3. **解问题 (Address)**: Handle objections. Every objection is a buying signal in disguise.\n4. **提成交 (Close)**: Ask for the commitment. Silence after asking is your best tool.\n\n### Principle 7: Phone Call Protocol (电话拜访规则)\n- Optimal call length: **3–5 minutes** (maximum 6 minutes)\n- Before every call: Write down your ONE objective for this call\n- Best use cases: Follow-up confirmation, closing push, payment collection\n- After every call: Log the result within 10 minutes while memory is fresh\n\n### Principle 8: ASK Growth System\nEvery sales improvement requires development in three dimensions:\n- **A — Attitude (心态)**: Belief in the product, resilience, ownership mindset\n- **S — Skill (技能)**: Prospecting, questioning, objection handling, closing\n- **K — Knowledge (知识)**: Industry, product, competition, customer context\n\n---\n\n## Pipeline Stages\n\nLeads move through 8 stages. Your agent tracks stage and days-in-stage:\n\n| Stage | Label | Description | Healthy Duration |\n|-------|-------|-------------|-----------------|\n| 1 | `prospect` | Identified, not yet contacted | — |\n| 2 | `connected` | First contact made, initial interest | 1–3 days |\n| 3 | `qualified` | Pain confirmed, budget exists | 3–7 days |\n| 4 | `presented` | Solution presented | 3–7 days |\n| 5 | `proposal` | Formal proposal submitted | 3–10 days |\n| 6 | `negotiation` | Active negotiation on terms | 3–14 days |\n| 7 | `closing` | Final push — YES or NO this week | 1–5 days |\n| 8 | `won` | Closed. Onboarding. Collect payment. | — |\n| 9 | `lost` | Lost. Record reason. Learn. | — |\n\n**Alert rule**: Any lead stuck in the same stage for more than double the healthy duration = 🔴 Red status.\n\n---\n\n## Lead Scoring (0–100)\n\nYour agent automatically scores each lead to prioritize your daily actions:\n\n| Factor | Max Points | How It's Calculated |\n|--------|-----------|---------------------|\n| Stage progression | 25 | Higher stage = more points |\n| Recency of contact | 20 | Last contact \u003C 3 days = 20pts; \u003C 7 days = 10pts; > 14 days = 0pts |\n| Engagement level | 20 | Customer-initiated contact = high; passive = low |\n| Deal size | 15 | Relative to your average deal size |\n| Time pressure | 20 | Customer deadline approaching = high score |\n\n**Score interpretation**:\n- 80–100: 🔥 Hot — close this week\n- 60–79: ✅ Warm — maintain rhythm, don't let cool\n- 40–59: 🟡 Lukewarm — needs intervention or deprioritize\n- Below 40: 🔴 Cold — decide: revive or move on\n\n---\n\n## Commands & Usage\n\n### Daily Commands\n\n**Morning Brief** (run every morning before 9am):\n> \"Morning sales brief\" \u002F \"Who should I call today?\" \u002F \"Sales priorities today\"\n\nAgent will: Scan pipeline → Score all leads → Generate top 3–5 priority actions → Suggest approach for each based on customer type.\n\n**Log Activity** (after every call\u002Fmeeting):\n> \"Log: [customer name] — [what happened] — [next step]\"\n> Example: \"Log: Sarah Chen at TechBridge — she's interested but wants to loop in her CEO — next step: send exec summary by Thursday\"\n\nAgent will: Record activity → Update lead status → Recalculate score → Flag if rhythm is at risk.\n\n**Add New Lead**:\n> \"New lead: [Name] at [Company] — [context]\"\n> Example: \"New lead: David Park at Sunrise Manufacturing — met at trade show, interested in reducing procurement costs\"\n\nAgent will: Create lead profile → Classify personality type from context → Set stage to connected → Add to next morning brief.\n\n**Check Deal Status**:\n> \"How is [customer name] doing?\" \u002F \"Update on [company]\"\n\nAgent will: Pull customer profile → Show stage, score, last contact, temperature → Recommend next action.\n\n### Weekly Commands\n\n**Weekly Sprint Plan** (every Monday morning):\n> \"Weekly sprint plan\" \u002F \"Monday sales planning\"\n\nAgent will: Apply Three-Step Sprint logic to current week in the cycle → Categorize all leads by this week's priority tier → Generate a concrete 5-day action plan → Identify leads that need a YES\u002FNO decision this week.\n\n**Pipeline Health Review** (every Friday):\n> \"Pipeline review\" \u002F \"End of week sales check\" \u002F \"Pipeline health\"\n\nAgent will: Calculate overall pipeline velocity → Flag stalled deals → Identify temperature-cooling risks → Suggest which leads to cut (翻牌) → Project next 2-week revenue likelihood.\n\n**Stuck Deal Diagnosis**:\n> \"Deal stuck: [customer name]\" \u002F \"[Customer] hasn't responded, what do I do?\"\n\nAgent will: Diagnose cause of stall using Iron Army framework → Suggest intervention based on customer type → Provide exact language\u002Fscript for next outreach.\n\n---\n\n## File Structure\n\nThis skill uses local files in your workspace:\n\n```\n~\u002F.openclaw\u002Fworkspace\u002Fsales\u002F\n├── pipeline.md          ← Your CRM: all active leads\n├── activity-log.md      ← Every interaction logged\n├── weekly-sprint.md     ← Current week's plan\n└── closed-deals.md      ← Won\u002Flost deals (for learning)\n```\n\nTo initialize: run `scripts\u002Finit-pipeline.sh` once.\n\n---\n\n## Morning Brief Format\n\nEvery morning brief follows this structure:\n\n```\n📊 SALES MORNING BRIEF — [Date]\nCycle: Week [1\u002F2\u002F3\u002F4] of [Month] Sprint\n\n🔥 TOP PRIORITY TODAY (must-do):\n1. [Customer] — [Stage] — Score: [X] — [Why urgent] — [Recommended action]\n2. [Customer] — [Stage] — Score: [X] — [Why urgent] — [Recommended action]\n\n✅ MAINTAIN RHYTHM (important):\n3. [Customer] — [Stage] — Last contact: [X days ago] — [Action]\n4. [Customer] — [Stage] — Last contact: [X days ago] — [Action]\n\n⚡ SEED TODAY (new outreach):\n- [Target sector\u002Ftype for today's cold outreach]\n\n📈 PIPELINE SNAPSHOT:\n- Active leads: [N]\n- This week's close targets: [N]\n- Deals cooling (>7 days no contact): [N]\n- 🔴 Red alerts: [N]\n```\n\n---\n\n## Weekly Sprint Plan Format\n\n```\n🗓 WEEKLY SPRINT — Week [N] of [Month] — [3-Step Phase]\nPhase: [SEED \u002F FLIP \u002F HARVEST \u002F RESET]\n\nPHASE OBJECTIVE:\n[What this week is about based on the 3-step cycle]\n\nMONDAY — Launch:\nTUESDAY — Deepen:\nWEDNESDAY — Accelerate:\nTHURSDAY — Push:\nFRIDAY — Review & Reset:\n\nTHIS WEEK'S CLOSE TARGETS (need YES or NO):\n1. [Customer] — [Stage] — Closing script: [approach]\n2. [Customer] — [Stage] — Closing script: [approach]\n\nLEADS TO FLIP (qualify or drop):\n- [Customer] — [Reason to decide]\n\nSEED TARGETS (new outreach, 4+ per day):\n- [Target profile for this week]\n\nFRIDAY SUCCESS CRITERIA:\n□ [N] deals moved forward at least one stage\n□ [N] YES or NO decisions obtained\n□ [N] new leads added to pipeline\n```\n\n---\n\n## Stuck Deal Scripts (by Customer Type)\n\n### Tiger (老虎型) — deal stalled:\n> \"I know you're busy, so I'll be direct: the question on the table is X. If we move forward by [date], you get [specific benefit]. If not, I completely understand. Which is it?\"\n\n### Peacock (孔雀型) — deal stalled:\n> \"Hey [name], I was just showing your situation to a colleague and they immediately said this reminded them of [success story]. Made me think — let's get the team together for a quick 20-min call this week. When works for you?\"\n\n### Koala (无尾熊型) — deal stalled:\n> \"I wanted to check in and share something that might help ease the decision. Three other companies in your industry have been through exactly this situation — here's what they found. No rush at all — just want to make sure you have everything you need to feel confident.\"\n\n### Owl (猫头鹰型) — deal stalled:\n> \"I realized I hadn't sent over the complete technical spec and the full pricing breakdown with all variables. Sending that now. Let me know if any number looks different from what you expected — I'd rather address it directly than have any ambiguity.\"\n\n---\n\n## Integration Notes\n\n- Works with any messaging channel (Telegram, WhatsApp, Slack, Discord)\n- No external API required — all data stored locally\n- Pairs well with: `gog` skill (Google Calendar integration for scheduling follow-ups)\n- Compatible with: `memo` (brew) for quick voice-to-text lead logging\n- Daily cron suggested: `0 8 * * 1-5` for automatic morning brief delivery\n\n---\n\n## Quick Start\n\n```bash\n# 1. Install skill\ncp -r sales-rhythm-tracker ~\u002F.openclaw\u002Fskills\u002F\n\n# 2. Initialize your pipeline workspace\n~\u002F.openclaw\u002Fskills\u002Fsales-rhythm-tracker\u002Fscripts\u002Finit-pipeline.sh\n\n# 3. Add your first lead (via your messaging app):\n# \"New lead: [Name] at [Company] — [context of how you met]\"\n\n# 4. Get your first morning brief:\n# \"Morning sales brief\"\n```\n\n---\n\n*Built on the Alibaba Iron Army (阿里铁军) methodology — the sales system that trained 10,000+ B2B salespeople and generated billions in SMB revenue across China.*\n",{"name":5,"tags":24,"author":32,"version":33,"category":30,"description":34},[25,26,27,28,29,30,31],"sales","crm","pipeline","b2b","productivity","business","revenue","yinguofeng007","1.0.0","B2B sales pipeline manager powered by the Alibaba Iron Army (阿里铁军) methodology. Use this skill for daily sales briefings, lead management, pipeline health checks, weekly sprint planning, customer follow-up prioritization, and closing strategy. Triggered by phrases like: \"morning sales brief\", \"add lead\", \"pipeline review\", \"who should I call today\", \"weekly sales plan\", \"sales update\", \"close rate\", \"follow up\", \"deal stuck\", \"customer type\", \"sales sprint\".\n","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fdeepseekcmo\u002Fsales-rhythm-tracker",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill sales-rhythm-tracker",{"tool":50,"command":51},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill sales-rhythm-tracker",{"tool":53,"command":54},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill sales-rhythm-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeepseekcmo\u002Fsales-rhythm-tracker\u002FSKILL.md",true,[],[59,67,74,81,88,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":66},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":66},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":66},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":66},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":66},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":66},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]