Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计提醒

pitch-follow-up-tracker音调跟踪跟踪器

Agent Skill

pitch-follow-up-tracker 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,376

周安装

129

GitHub Stars

公开资料未说明

下载量

832
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pitch-follow-up-tracker(音调跟踪跟踪器)
来源仓库:https://github.com/alexa853/pitch-follow-up-tracker
安装命令:
openclaw skills install pitch-follow-up-tracker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install pitch-follow-up-tracker

简介

pitch-follow-up-tracker 监控外展活动并起草上下文后续邮件。

  • 自动检查 Gmail 回复状态,标记停滞联系人提醒跟进。
  • 集成 Google Sheet 或 Markdown 作为追踪数据源。
  • 需授权访问邮箱与表格权限,注意隐私数据保护。
  • 建议设置合理跟进间隔,避免过度打扰潜在客户。

SKILL.md

name
pitch-follow-up-tracker
description
Track outreach pitches and draft contextual follow-up emails. Monitors a pitch tracker (Google Sheet or local markdown), checks Gmail for replies, flags stale pitches, and drafts tiered follow-ups (Day 3, Day 7, Day 14) that reference the original pitch content. Use when you need to check on pitch follow-ups, draft follow-up emails, review outreach status, find pitches without replies, or manage an outreach pipeline. Triggers on: 'check follow-ups,' 'who hasn't replied,' 'draft follow-ups,' 'outreach status,' 'pitch tracker,' 'stale pitches,' or any request to manage pitch/outreach follow-up.

Pitch Follow-Up Tracker

Monitor outreach pitches, detect non-replies, and draft contextual, tiered follow-up emails.

Prerequisites

  • gog CLI (required) — for Gmail access
  which gog
  • Google account configured with gog (gog gmail --account <email>)
  • Pitch tracker — one of:

- Google Sheet with outreach data - Local markdown file with pitch records

Workflow

1. Collect Configuration

Ask the user (or detect from context):

ParameterRequiredDescription
gmail_accountyesEmail account to check (e.g., you@company.com)
tracker_typeyes"sheet" or "markdown"
tracker_idif sheetGoogle Sheet ID
tracker_pathif markdownPath to local .md file
sender_nameyesName to use in follow-ups
sender_roleoptionalRole/title for email signature context
follow_up_styleoptional"warm" (default), "direct", or "casual"

2. Load Pitch Data

From Google Sheet:

gog sheets get <SHEET_ID> "<TAB_NAME>!A1:Z500" --json --account <gmail_account>

Expected columns (flexible — adapt to whatever columns exist):

  • Contact name / email
  • Brand / company
  • Date sent
  • Subject or pitch summary
  • Status (if tracked)

From Markdown file: Read the file. Expected format (flexible):

## [Brand Name]
- **Contact:** Name <email>
- **Sent:** YYYY-MM-DD
- **Subject:** [pitch subject]
- **Summary:** [what was pitched]
- **Status:** Sent / Replied / Closed

Adapt to whatever format the user actually uses. Extract: contact email, brand, date sent, pitch content/subject, current status.

3. Verify Reply Status (CRITICAL — Do Not Skip Steps)

Before flagging ANY pitch as "needs follow-up," you MUST complete ALL of these checks. Do not skim. Do not skip. A false positive wastes the user's time and erodes trust.

Check 1: Search for direct replies

gog gmail search "from:<contact_email>" --max 10 --account <gmail_account>

Look for any reply from the contact after the pitch send date, even in a different thread.

Check 2: Search by domain (catches new threads)

gog gmail search "from:@<contact_domain>" --max 10 --account <gmail_account>

Brands often respond from a different person at the same company. Check for ANY email from that domain since the pitch date.

Check 3: Search sent folder for user follow-ups

gog gmail search "to:<contact_email> OR to:@<contact_domain>" --max 10 --account <gmail_account>

Check if the user already sent a response, follow-up, or forwarded the thread.

Check 4: Search drafts for unsent responses

gog gmail search "in:drafts <contact_name> OR <brand_name>" --max 5 --account <gmail_account>

A draft response means the user is working on it. Do NOT flag as needing follow-up.

Check 5: Check if forwarded

gog gmail search "subject:Fwd: <original_subject>" --max 5 --account <gmail_account>

If the original email was forwarded to a colleague, talent, or team member, it may be in progress.

Check 6: Read full email threads For any matching threads, read the FULL thread content — not just the latest message. Context changes mid-thread.

gog gmail get <message_id> --account <gmail_account>

Check 7: Check recent memory/context If available, check conversation history, daily memory files, or any tracker for recent context about this deal. The user may have mentioned handling it verbally or via another channel (text, WhatsApp, call).

Classification (only after ALL checks):

  • Replied — contact responded (in same or different thread)
  • Already followed up — user sent a follow-up but no reply yet
  • Draft in progress — user has an unsent draft
  • Forwarded/delegated — user forwarded to someone else
  • Needs follow-up — ALL checks came back empty. No activity since original send.
  • Too fresh — sent less than 3 days ago

4. Calculate Follow-Up Tier

For pitches needing follow-up, determine tier based on days since last outreach:

Days Since Last ContactTierTone
3-6 daysDay 3: Gentle NudgeLight, brief, bumping to top of inbox
7-13 daysDay 7: Add ValueShare something useful — article, idea, new angle
14+ daysDay 14: Final Check-InDirect, low-pressure, leave door open

If user already sent one follow-up, advance to next tier.

5. Draft Follow-Up Emails

Each draft MUST reference the original pitch content. No generic "just checking in" emails.

Day 3 — Gentle Nudge:

Subject: Re: [Original Subject]

Hi [Name],

Wanted to bump this to the top of your inbox — [one sentence referencing the specific pitch content, e.g., "the proposal for a summer campaign series featuring outdoor content"].

Happy to jump on a quick call or send more details if helpful.

[Sender Name]

Day 7 — Add Value:

Subject: Re: [Original Subject]

Hi [Name],

Following up on my note about [specific pitch reference]. Since I sent that over, [add relevant value: a new idea, a relevant trend, a recent success story, a new content example].

Would love to explore how this could work for [Brand]. Open to a quick chat this week?

[Sender Name]

For the "add value" component, search the web for a recent relevant tidbit:

web_search "[brand name] [niche] news 2026"

Incorporate a genuine, relevant insight — not filler.

Day 14 — Final Check-In:

Subject: Re: [Original Subject]

Hi [Name],

Circling back one last time on [specific pitch reference]. Totally understand if the timing isn't right — just wanted to make sure this didn't get buried.

If [Brand] is exploring [relevant type of partnership] down the line, I'd love to be on your radar. Always happy to connect.

[Sender Name]

Adjust tone based on follow_up_style:

  • warm (default): Friendly, relationship-focused
  • direct: Shorter, business-focused, clear ask
  • casual: Conversational, emoji-OK, lighter

6. Output Summary

# Outreach Follow-Up Report

**Date:** [today]
**Account:** [gmail_account]
**Pitches Reviewed:** [total count]

## ✅ Replies Received ([count])
| Brand | Contact | Replied On | Action Needed |
|-------|---------|------------|---------------|
| [Brand] | [Name] | [date] | [Review reply / Schedule call / Send deck] |

## 🔥 Needs Follow-Up ([count])

### Day 3 — Gentle Nudge
**[Brand Name]** → [Contact Name] <[email]>
- Original pitch: [summary]
- Sent: [date] ([X] days ago)
- Draft:
> [Full draft email]

### Day 7 — Add Value
**[Brand Name]** → [Contact Name] <[email]>
- Original pitch: [summary]
- Sent: [date] ([X] days ago)
- Draft:
> [Full draft email]

### Day 14 — Final Check-In
**[Brand Name]** → [Contact Name] <[email]>
- Original pitch: [summary]
- Sent: [date] ([X] days ago)
- Draft:
> [Full draft email]

## ⏳ Too Fresh to Follow Up ([count])
| Brand | Contact | Sent | Follow-Up Date |
|-------|---------|------|----------------|
| [Brand] | [Name] | [date] | [date when Day 3 hits] |

## 📊 Pipeline Summary
- Total active pitches: [X]
- Awaiting reply: [X]
- Replied: [X]
- Follow-ups needed today: [X]

7. Create Gmail Drafts (if requested)

If the user approves the follow-up drafts:

gog gmail draft create --to "<email>" --subject "Re: [subject]" --body "<draft body>" --account <gmail_account>

Always ask before creating drafts. Never send emails without explicit approval.

Error Handling

IssueAction
gog not installedStop and instruct: npm i -g gog or equivalent
Gmail auth expiredPrompt: gog gmail auth --account <email>
Sheet not accessibleVerify Sheet ID and sharing permissions
No pitches found in trackerReport empty tracker, suggest format
Contact email missingFlag the pitch, skip Gmail check for it
Rate limited on GmailSpace queries with 1-2s delays, process in batches
Markdown format unexpectedAdapt parsing to whatever structure exists, ask user if ambiguous

Tips

  • Run this daily or every 2-3 days for best results
  • Keep your pitch tracker updated — the skill is only as good as your data
  • Review and personalize drafts before sending — they're starting points, not final copy
  • The "add value" follow-up works best when you have genuine news or insights to share

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

70.57%
按下载量换算587

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills