Token导航 LogoToken导航

Agent Skill · 研究检索

bd-email(BD 电子邮件)

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

bd-email 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证为 MIT,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 51,696。

总安装 576周安装 24GitHub Stars 2下载 192核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/mattforni/dotfiles --skill bd-email

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

bd-email 专为 RYLLC 分式 CTO 业务拓展设计,用于撰写专业且自然的商务发展邮件。邮件长度控制在 130–150 字,采用完整句式,突出价值主张,避免冗长介绍。强调服务导向,不自我吹嘘,聚焦经验与客户收益,适用于初步客户触达场景。使用前请确认收件人背景与公司服务范围匹配,避免模板化表达降低转化率。

bd-email 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/bd-email

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/mattforni/dotfiles --skill bd-email;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

bd-email 怎么安装?

在终端执行 npx skills add https://github.com/mattforni/dotfiles --skill bd-email。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

bd-email 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

bd-email 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

bd-email 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

bd-email 用的人多吗?

公开数据是累计安装 576 次,近一周安装 24 次,下载 192 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

bd-email 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
bd-email

BD 电子邮件 · 本页

5762调用外部服务MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

BD Email Skill

Purpose: Draft professional, conversational Business Development emails for RYLLC fractional CTO consultancy outreach.

Core Principles

  1. Tight and conversational - Target ~130-150 words for initial outreach
  2. Complete sentences - No sentence fragments, use subjects and verbs
  3. Single version only - Don't draft multiple alternatives
  4. Natural voice - Professional but warm, not overly formal
  5. Get to the point - Lead with value, avoid long introductions
  6. No bragging - Focus on experience, not metrics or accomplishments
  7. Service orientation - What can you do for them
  8. Title Case for subject lines - Always use Title Case for email subjects

Email Flavors

1. Colleague Reconnect

Use for: Former colleagues, VCs, advisors, warm contacts Template: templates/06-colleague-reconnect.md Key elements:

  • Personal reference to last interaction
  • Brief "barbell CTO" positioning
  • Ask for perspective/insights (low pressure)
  • Scheduling link

2. Job Posting Cold Outreach

Use for: Found strong technical fit role, want to pitch fractional alternative Template: templates/07-job-posting-cold-outreach.md Key elements:

  • Reference job posting with hyperlink
  • Forward request to right person
  • Brief credentials showing technical fit
  • Specific interest in their tech/mission
  • Fractional alternative pitch
  • "Rather than (or alongside) a full-time hire" framing

3. Rejection Follow-Up

Use for: Received job rejection, want to turn into network connection Template: templates/05-rejection-follow-up.md Key elements:

  • Thank them for consideration
  • Express continued interest in company/mission
  • Pivot from role to relationship
  • Position fractional CTO services as alternative

4. Direct Introduction Request

Use for: Asking warm contact to intro you to specific company Key elements:

  • Acknowledge their offer/suggestion
  • Brief positioning relevant to target company
  • Specific ways you could add value
  • Clear ask (make the intro)
  • Offer to provide additional context

5. Custom BD Outreach

Use for: Unique situations not covered by templates Approach: Follow core principles, adapt tone to relationship warmth

The "Barbell CTO" Positioning

Standard explanation (adjust as needed):

"I'm focused on fractional CTO work and reliability staff augmentation. On the CTO side, I'm doing the deep technical work like architecture and system design on one end, and high-level strategy like roadmap and team building on the other."

Note: Keep framing positive. Avoid negative language like "skipping all the middle management nonsense" or similar. Focus on what you DO provide, not what you avoid.

Technical Credentials (Use Sparingly)

Standard positioning:

"I spent six years as CTO and co-founder of Gremlin, pioneering chaos engineering."

For energy/climate context:

"At Gremlin, we constantly wrestled with quantifying the impact of failures that didn't happen—exactly the kind of reliability challenge that's critical in [energy systems/climate infrastructure]."

What to Avoid

  • Sentence fragments or choppy writing
  • Multiple alternative versions
  • Bragging about metrics ($10M+ ARR, 100+ customers)
  • Redundant paragraphs
  • Multiple bullet lists in email body
  • Alternative contact strategy sections
  • Long explanations when brevity works

Standard Components

Scheduling link: https://app.reclaim.ai/m/forni/chat

  • Preferred phrasing: "You can grab some time here [link] if you like."
  • Alternative: "You can find some time here: [link]"
  • Always embed in conversational text, not standalone

Signature:

Matthew Fornaciari

Warm closing (for reconnect emails): "Either way, cheers and hope things are going well."

  • Use when you want to give warmth without pressure
  • Shows genuine interest beyond just the business ask

Forward request (for cold outreach): "If I'm reaching out to the wrong person, I'd appreciate you forwarding this along to whoever's leading this hire."

Process

  1. Identify email flavor - Which template/approach fits?
  2. Gather context - Relationship history, company details, technical fit

- Email history analysis: Use Gmail MCP to search and read past email threads with the contact - Look for: Last contact date, nature of relationship, how things ended, any commitments made, warm/cold signals - Key insights: Did they offer to stay in touch? Was there a previous engagement discussion? Any specific topics discussed?

  1. Enrich from LinkedIn - Current role, company stage, recent activity, mutual connections
  2. Draft email - Follow template structure, customize personal elements with specific details from email history
  3. Check length - Target ~130-150 words
  4. Review tone - Natural? Warm but professional? Service-oriented?
  5. Single version - Don't create alternatives

Example Usage

Warm reconnect to former colleague:

  • Use template 06
  • Add specific personal reference
  • Brief barbell CTO explanation
  • Low-pressure ask for perspective

Cold outreach to job posting:

  • Use template 07
  • Hyperlink to job posting
  • Show technical fit understanding
  • Pitch fractional alternative
  • Include forward request

Introduction request to warm contact:

  • Direct, conversational tone
  • Brief positioning relevant to target
  • Specific value-add examples
  • Clear ask to make intro

Resources

All templates available in:

  • /Users/forni/Craft/vocation/templates/

Contact database:

  • /Users/forni/Craft/vocation/network/contacts.md

Project guidelines:

  • /Users/forni/Craft/vocation/CLAUDE.md

Gmail Integration

For details on using Gmail MCP server to draft emails directly in Gmail, see gmail-integration.md.

Quick start: After Claude Code restart, use draft_email tool to create drafts directly in Gmail instead of copy/paste.

平台分布

Claude Code

27.11%
按下载量换算52

OpenCode

22.33%
按下载量换算43

Antigravity

19.85%
按下载量换算38

Gemini CLI

13.24%
按下载量换算25

windsurf

7.71%
按下载量换算15

Cursor

3.48%
按下载量换算7

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

可疑

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills