snipe

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Snipe: Twitter 热帖截流

Snipe: Twitter Trending Post Traffic Capture

在 coding agent / AI 开发工具领域的高流量推广帖下回复 pikiclaw,截取流量拿 star。 本 skill 只生成回复草稿推送到飞书,不自动发推(避免封号)。
Reply to pikiclaw under high-traffic promotional posts in the coding agent/AI development tool field to capture traffic and gain stars. This skill only generates reply drafts and pushes them to Feishu, does NOT auto-post to Twitter (to avoid account suspension).

核心策略

Core Strategy

用户验证过的高效打法:
  • 同领域产品 的推广帖下回复(流量越大越好)
  • 一句话差异化 +
    npx pikiclaw@latest
    + GitHub 链接
  • pikiclaw 的核心差异点(按重要性):多 agent 会话并行管理(dashboard 里同时操控 Claude/Codex/Gemini)、丝滑的本地体验(一行 npx 启动,零配置)、实用的 skill/MCP 插件生态(社区沉淀的 skill 和 MCP 开箱即用)、IM 接入(Telegram/飞书/微信随时接管同一个会话)、完全开源 + 本地运行
  • IM 不是头条卖点,而是"体验"的一部分 — 头条永远是多会话管理 + 流畅度 + 插件生态
历史案例参考:
  • 某远程 agent 管理工具推广帖下回复 → 7,792 views, 31 likes(原帖 14 万)
  • 某 macOS agent 管理工具推广帖下回复 → 1,258 views(原帖 5.4 万)
  • 规律:原帖与 pikiclaw 功能越接近,回复转化率越高
User-verified effective tactics:
  • Reply under promotional posts of same-field products (the higher the traffic, the better)
  • One-sentence differentiation +
    npx pikiclaw@latest
    + GitHub link
  • Core differentiators of pikiclaw (in order of importance): multi-agent session parallel management (control Claude/Codex/Gemini simultaneously in the dashboard), smooth local experience (launch with one line of npx, zero configuration), practical skill/MCP plugin ecosystem (community-built skills and MCPs ready to use), IM integration (take over the same session anytime via Telegram/Feishu/WeChat), fully open-source + local runtime
  • IM is not the headline selling point, but part of the "experience" — the headline is always multi-session management + smoothness + plugin ecosystem
Historical case references:
  • Reply under a remote agent management tool's promotional post → 7,792 views, 31 likes (original post 140,000 views)
  • Reply under a macOS agent management tool's promotional post → 1,258 views (original post 54,000 views)
  • Rule: The closer the original post's product functions are to pikiclaw, the higher the reply conversion rate

工作流

Workflow

Step 1: 读取已回复记录

Step 1: Read Replied Records

读取
.pikiclaw/skills/snipe/sniped_posts.txt
,避免重复推荐。
Read
.pikiclaw/skills/snipe/sniped_posts.txt
to avoid duplicate recommendations.

Step 2: 搜索高流量推广帖

Step 2: Search for High-Traffic Promotional Posts

使用浏览器工具在 Twitter 搜索近期热门推广帖。
如果用户传入了关键词参数,直接用该关键词搜索。 否则,按以下策略动态搜索。不要死记某个产品名,而是用场景关键词捕获整个领域的推广帖:
搜索关键词(从通用到具体,搜 3-5 组即可):
coding agent tool
AI coding assistant 推荐
claude code 工具
coding agent 开源
remote coding agent
AI agent dashboard
vibe coding 工具
coding agent mobile
AI dev tool launch
搜索操作步骤:
对每个关键词:
  1. 导航到
    https://x.com/search?q={keyword}&src=typed_query&f=top
  2. 等待页面加载完成(确认看到推文内容)
  3. 读取
    .pikiclaw/skills/snipe/scripts/extract_tweets.js
    文件内容
  4. 通过
    browser_evaluate
    注入执行该 JS,获取返回的 JSON 字符串
  5. 解析 JSON 得到推文数组
  6. 如果结果不够多,按 End 键滚动一次,再次执行 JS 提取
  7. 合并所有关键词的结果,按
    text[:80] + url
    去重
重要:如果某个关键词搜索结果很少或没有推广帖,跳过即可,不要在无效关键词上浪费时间。
Use browser tools to search for recent trending promotional posts on Twitter.
If the user passes keyword parameters, search directly with those keywords. Otherwise, search dynamically according to the following strategy. Do not memorize a specific product name; instead, use scenario keywords to capture promotional posts across the entire field:
Search Keywords (from general to specific, search 3-5 groups):
coding agent tool
AI coding assistant 推荐
claude code 工具
coding agent 开源
remote coding agent
AI agent dashboard
vibe coding 工具
coding agent mobile
AI dev tool launch
Search Operation Steps:
For each keyword:
  1. Navigate to
    https://x.com/search?q={keyword}&src=typed_query&f=top
  2. Wait for the page to load (confirm tweet content is visible)
  3. Read the content of
    .pikiclaw/skills/snipe/scripts/extract_tweets.js
  4. Inject and execute the JS via
    browser_evaluate
    to get the returned JSON string
  5. Parse the JSON to get the tweet array
  6. If there are not enough results, scroll once by pressing the End key and execute the JS again to extract
  7. Merge results from all keywords, deduplicate by
    text[:80] + url
Important: If a keyword yields few or no promotional posts, skip it immediately; do not waste time on invalid keywords.

Step 3: 筛选候选帖

Step 3: Filter Candidate Posts

从所有提取的推文中,识别 正在推广具体产品/工具 的帖子。
识别推广帖的信号:
  • 帖子内容提到具体产品名、功能介绍、安装命令
  • has_product_signal 为 true(包含 GitHub 链接、npm/pip 安装命令、产品域名)
  • 外部链接指向产品官网或 GitHub
  • 语气是介绍/推荐/发布(而非纯讨论或提问)
必须满足:
  • views > 5,000(流量池太小不值得)
  • 最近 48 小时内发布
  • 推广的产品/工具与 pikiclaw 有功能交集(coding agent 管理、远程控制、多 agent 切换、IM 接入等)
  • 不在
    sniped_posts.txt
优先级排序(高到低):
  1. 功能与 pikiclaw 高度重叠的产品推广帖(截流效果最好)
  2. 同赛道但切入点不同的产品推广帖(可以打差异化)
  3. 泛 AI 工具推广帖(曝光有但转化低)
排除:
  • 自己 (@sthnavy) 的帖子
  • 纯新闻/资讯/讨论帖(没有推广具体产品)
  • 已经是 pikiclaw 用户/转发者的帖子
  • 政治/争议/无关话题
选出 Top 3-5 条候选帖。对每条候选帖,简要分析它推广的产品与 pikiclaw 的功能交集和差异点。
From all extracted tweets, identify posts that are promoting specific products/tools.
Signals to identify promotional posts:
  • The post mentions specific product names, feature introductions, or installation commands
  • has_product_signal is true (contains GitHub links, npm/pip installation commands, or product domains)
  • External links point to product official websites or GitHub
  • Tone is introductory/recommendatory/announcement-based (not pure discussion or question)
Must meet:
  • views > 5,000 (too small a traffic pool is not worth it)
  • Published within the last 48 hours
  • The promoted product/tool has functional overlap with pikiclaw (coding agent management, remote control, multi-agent switching, IM integration, etc.)
  • Not in
    sniped_posts.txt
Priority Order (high to low):
  1. Promotional posts of products with highly overlapping functions with pikiclaw (best traffic capture effect)
  2. Promotional posts of products in the same track but with different entry points (can play up differentiation)
  3. General AI tool promotional posts (exposure exists but conversion is low)
Exclude:
  • Own posts (@sthnavy)
  • Pure news/information/discussion posts (no specific product promotion)
  • Posts from existing pikiclaw users/retweeters
  • Political/controversial/irrelevant topics
Select Top 3-5 candidate posts. For each candidate post, briefly analyze the functional overlap and differences between the promoted product and pikiclaw.

Step 4: 生成回复草稿

Step 4: Generate Reply Drafts

对每条候选帖,生成回复草稿。
核心原则:读懂原帖在推什么,找到 pikiclaw 相比它最锋利的一个差异点,用最短的文字打穿。
回复格式(极简优先):
{一句差异化,直击原帖产品的短板或 pikiclaw 的独特优势}
npx pikiclaw@latest

GitHub: https://github.com/xiaotonng/pikiclaw
差异化切入角度(从上到下是推荐优先级,挑与原帖产品最对得上的一个):
  • 对方只管单 agent / 单会话 → "Dashboard 里并行管理 Claude/Codex/Gemini 多会话,随时切换"
  • 对方体验粗糙 / 配置复杂 → "一行 npx 启动,dashboard 开箱即用,零配置"
  • 对方生态封闭 / 没有插件 → "开放的 skill/MCP 插件体系,社区沉淀的实用工具开箱即用"
  • 对方是闭源 / SaaS → "完全开源,会话和代码全部留在本机"
  • 对方只有 CLI → "自带 web dashboard,浏览器里完整控制多会话"
  • 对方只能在桌前使用 → "Telegram/飞书/微信直连,手机随时接管同一个会话"
  • 对方只支持英文 / 单平台 → "中英双语,macOS 桌面自动化 + Playwright 浏览器控制"
回复规则:
  • 语言跟随原帖(中文帖用中文,英文帖用英文)
  • 保持极简,1-2 句话最佳,绝不超过 3 句
  • 必须包含
    npx pikiclaw@latest
    和 GitHub 链接
  • 用建设者/开发者的语气,不用"推荐""安利"等推销词
  • 不要贬低原帖产品,只强调 pikiclaw 的不同
Generate a reply draft for each candidate post.
Core Principle: Understand what the original post is promoting, find the sharpest differentiator of pikiclaw compared to it, and break through with the shortest text.
Reply Format (minimalism first):
{One-sentence differentiation that directly targets the original product's weakness or pikiclaw's unique advantage}
npx pikiclaw@latest

GitHub: https://github.com/xiaotonng/pikiclaw
Differentiation Entry Angles (recommended priority from top to bottom, pick the one that best matches the original post's product):
  • The other party only manages single agent / single session → "Manage Claude/Codex/Gemini multi-sessions in parallel in the dashboard, switch anytime"
  • The other party has rough experience / complex configuration → "Launch with one line of npx, dashboard ready to use, zero configuration"
  • The other party has a closed ecosystem / no plugins → "Open skill/MCP plugin system, practical community-built tools ready to use"
  • The other party is closed-source / SaaS → "Fully open-source, all sessions and code stay local"
  • The other party only has CLI → "Built-in web dashboard, full control of multi-sessions in the browser"
  • The other party can only be used at the desk → "Direct connection via Telegram/Feishu/WeChat, take over the same session anytime on mobile"
  • The other party only supports English / single platform → "Bilingual (Chinese/English), macOS desktop automation + Playwright browser control"
Reply Rules:
  • Follow the language of the original post (use Chinese for Chinese posts, English for English posts)
  • Keep it minimal, 1-2 sentences are best, never more than 3
  • Must include
    npx pikiclaw@latest
    and the GitHub link
  • Use a builder/developer tone, avoid promotional words like "recommend" or "endorse"
  • Do not belittle the original post's product, only emphasize pikiclaw's differences

Step 5: 生成报告 Markdown

Step 5: Generate Report Markdown

将候选帖和回复草稿整理为 Markdown 报告:
markdown
undefined
Organize candidate posts and reply drafts into a Markdown report:
markdown
undefined

Snipe 候选 — {YYYY-MM-DD}

Snipe Candidates — {YYYY-MM-DD}

共发现 {n} 条高流量推广帖,以下按推荐优先级排列。

A total of {n} high-traffic promotional posts were found, arranged below by recommendation priority.

候选 1: {原帖内容摘要,不超过 20 字}

Candidate 1: {Original post content summary, no more than 20 characters}

  • 作者: @{handle}({name})
  • 链接: {tweet_url}
  • 数据: {views} views / {likes} likes / {retweets} RT
  • 推广产品: {product_name} — {一句话描述这个产品做什么}
  • 与 pikiclaw 的交集: {功能重叠点}
  • pikiclaw 的差异优势: {最锋利的差异点}
  • Author: @{handle} ({name})
  • Link: {tweet_url}
  • Data: {views} views / {likes} likes / {retweets} RT
  • Promoted Product: {product_name} — {One-sentence description of what this product does}
  • Overlap with pikiclaw: {Functional overlap points}
  • Differentiated Advantage of pikiclaw: {The sharpest differentiator}

推荐回复

Recommended Reply

{draft}

{draft}

候选 2: ...

Candidate 2: ...

...

...

操作指南

Operation Guide

  1. 优先回复候选 1(流量最大 / 功能最近),依次往下
  2. 在 Twitter 发回复时粘贴 GitHub 链接,Twitter 会自动生成卡片
  3. 发完后将推文 URL 追加到
    .pikiclaw/skills/snipe/sniped_posts.txt
undefined
  1. Prioritize replying to Candidate 1 (highest traffic / closest functions), then proceed in order
  2. Paste the GitHub link when posting the reply on Twitter, Twitter will automatically generate a card
  3. After posting, append the tweet URL to
    .pikiclaw/skills/snipe/sniped_posts.txt
undefined

Step 6: 推送到飞书

Step 6: Push to Feishu

  1. 将 Step 5 生成的 Markdown 报告写入
    /tmp/snipe_report.md
  2. 执行飞书推送脚本:
bash
cd /Users/admin/Desktop/project/pikiclaw && python3 .pikiclaw/skills/snipe/scripts/push_feishu.py --report-file /tmp/snipe_report.md
  1. 检查脚本输出:
    • OK:
      开头 → 成功,报告文档 URL 和通知都已发送
    • PARTIAL:
      → 文档创建成功但通知未发(缺 FEISHU_RECEIVE_ID)
    • ERROR:
      → 失败,在对话中直接展示报告内容作为兜底
  1. Write the Markdown report generated in Step 5 to
    /tmp/snipe_report.md
  2. Execute the Feishu push script:
bash
cd /Users/admin/Desktop/project/pikiclaw && python3 .pikiclaw/skills/snipe/scripts/push_feishu.py --report-file /tmp/snipe_report.md
  1. Check the script output:
    • Starts with
      OK:
      → Success, both the report document URL and notification have been sent
    • Starts with
      PARTIAL:
      → Document created successfully but notification not sent (missing FEISHU_RECEIVE_ID)
    • Starts with
      ERROR:
      → Failed, directly display the report content in the conversation as a fallback

Step 7: 更新记录

Step 7: Update Records

将本次所有候选帖 URL 追加到
.pikiclaw/skills/snipe/sniped_posts.txt
Append the URLs of all candidate posts from this round to
.pikiclaw/skills/snipe/sniped_posts.txt
.

注意事项

Notes

  • 绝不自动发推 — 所有回复草稿仅推送到飞书供人工审核
  • 质量 > 数量 — 每次 3-5 条候选即可
  • 不要固定搜某个产品名 — 用场景关键词动态发现,这个领域每天都有新工具出现
  • 飞书凭证从项目根目录
    .env
    读取(需要
    FEISHU_APP_ID
    FEISHU_APP_SECRET
    FEISHU_CHAT_ID
  • Never auto-post to Twitter — All reply drafts are only pushed to Feishu for manual review
  • Quality > Quantity — 3-5 candidates per round are sufficient
  • Do not fixate on searching for a specific product name — Use scenario keywords to discover dynamically; new tools emerge in this field every day
  • Feishu credentials are read from the project root directory
    .env
    (requires
    FEISHU_APP_ID
    ,
    FEISHU_APP_SECRET
    ,
    FEISHU_CHAT_ID
    )