Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

commercial-outreach商业推广

Agent Skill

commercial-outreach 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

306

周安装

13

GitHub Stars

1

下载量

107
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:commercial-outreach(商业推广)
来源仓库:https://github.com/piperubio/ai-agents
仓库路径:skills/commercial-outreach
安装命令:
npx skills add https://github.com/piperubio/ai-agents --skill commercial-outreach
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/piperubio/ai-agents --skill commercial-outreach

简介

commercial-outreach 生成面向技术顾问客户的个性化多触点推广序列,定位为战略顾问而非产品推销者。

  • 适用于 B2B 销售初期接触,以诊断报告或行业基准作为钩子,引导客户主动寻求合作。
  • 强调高管语调与非侵扰式沟通,要求输入 prospect-profile.md 以定制话术与价值主张。
  • 输出内容需经人工审核,防止过度承诺或泄露未公开方法论,确保符合企业品牌与安全规范。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Commercial Outreach — B2B Consulting Sales

Purpose

Generate personalized, multi-touch outreach sequences for technology consulting prospects. Position the sender as a strategic advisor, NOT a product seller. Outreach must offer value (assessments, insights, benchmarks) rather than request demos or meetings.

Key Differentiation from SaaS Outreach

  • Lead with insight, not features.
  • Offer a diagnostic/assessment as the CTA, not a demo.
  • Position as peer advisor, not vendor.
  • Reference industry-specific challenges, not generic pain.
  • Tone: executive, consultative, non-pushy.

Inputs

  • prospect-profile.md — from commercial-prospecting skill.
  • commercial-state.md — pipeline context.
  • user_input — campaign parameters (channel, intensity, specific messaging angle).

Outputs (contract)

1. New File: outreach-sequence.md (per prospect)

Contents:

  • Sequence overview: channel, number of touches, timing, objective.
  • 5–7 touch sequence, each touch containing:

- Timing (day number) - Channel (email / LinkedIn / phone) - Subject line or hook - Full message body - CTA

  • A/B variants for emails 1 and 3.
  • Breakup email (final touch).
  • Personalization tokens highlighted — what to customize per recipient.
  • Follow-up triggers — what response warrants which next step.

2. Updated: commercial-state.md

Log outreach activity in the opportunity's entry.

Sequence Framework (7-touch default)

TouchDayChannelPurpose
10EmailValue-first — share insight relevant to their industry/challenge
23LinkedInConnection request with personalized note
37EmailDifferent angle — reference a relevant case or benchmark
410LinkedInEngage with their content or share relevant article
514EmailOffer a free mini-assessment or diagnostic
621PhoneVoicemail attempt (script provided)
728EmailBreakup — respectful close, leave door open

For full templates by service line, subject line formulas, response handling, and timing guidance, see references/sequence-templates.md.

Guardrails

  1. NEVER use aggressive or pushy sales language.
  2. NEVER mention pricing in outreach — the goal is to earn a conversation.
  3. Every email must provide standalone value (insight, data point, benchmark).
  4. Personalization must go beyond {{first_name}} — reference specific company context.
  5. All CTAs must be low-commitment (15-min call, not a "sales meeting").
  6. Breakup email must be genuinely respectful, not passive-aggressive.
  7. LinkedIn messages must be shorter than emails (max 300 chars for connection requests).

Example

Touch 1 — Value-first email (Day 0) Target: VP of Operations at a logistics company considering data platform modernization.

Subject: Observation about {Company}'s fleet data challenge Hi {First_Name}, I noticed {Company} is expanding into last-mile delivery — that usually surfaces real friction in how fleet telemetry and route-optimization data flow through legacy systems. We recently helped a mid-market logistics firm cut their data-pipeline latency by 60 % during a similar expansion. The bottleneck wasn't where they expected. Would a 15-minute call to swap notes be worth your time? Happy to share what we found — no strings attached. Best, {Sender}

Touch 7 — Breakup email (Day 28)

Subject: Closing the loop Hi {First_Name}, I've reached out a few times and haven't heard back — completely understand; timing is everything. If modernizing {Company}'s data platform becomes a priority down the road, I'd welcome the conversation. Until then, wishing you and the team the best with the last-mile expansion. Best, {Sender}

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.09%
按下载量换算41

Claude

28.8%
按下载量换算31

Cursor

20.21%
按下载量换算22

Gemini CLI

9.99%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills