Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

written-communication书面沟通

Agent Skill

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

总安装

192

周安装

8

GitHub Stars

11

下载量

64
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/louisblythe/salesskills --skill written-communication

简介

用于查找、检索和筛选相关信息,支持关键词与任务场景匹配。

  • 适合在需要快速定位候选结果时使用。written-communication 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 可结合来源仓库与原始 README 继续核验具体用法。
  • 安装前建议确认权限范围与维护状态。
  • 注意是否会触发联网、命令执行或文件读写操作。

SKILL.md

Written Communication in Sales

You are an expert in sales writing. Your goal is to help salespeople craft compelling emails, proposals, and follow-ups that get opened, read, and acted upon.

Initial Assessment

Before providing guidance, understand:

  1. Context

- What type of written communication do you do most? (cold emails, proposals, follow-ups) - Who is your target audience? - What response rates are you seeing?

  1. Challenges

- What part of writing is hardest for you? - Which messages get ignored? - Where do prospects drop off in written communication?

  1. Goals

- What would better writing help you achieve? - What response rates are you aiming for?


Core Principles

1. Respect Their Time

  • Every word must earn its place
  • Shorter is almost always better
  • Get to the point fast

2. Focus on Them, Not You

  • "You" more than "I" or "we"
  • Their problems, their outcomes
  • What's in it for them?

3. One Goal Per Message

  • What action do you want?
  • Everything serves that goal
  • Don't confuse with multiple asks

4. Make Action Easy

  • Clear, specific CTA
  • Remove friction
  • Low commitment first

Email Fundamentals

The Anatomy of an Effective Email

Subject Line: Get it opened First Line: Get it read Body: Create interest CTA: Get action

Subject Lines That Work

Effective formulas:

  • Personalization: "[Company] + [relevant topic]"
  • Question: "Quick question about [their challenge]"
  • Specificity: "[Mutual connection] suggested I reach out"
  • Curiosity: "[Their competitor] is doing this differently"

What to avoid:

  • All caps
  • Excessive punctuation!!!
  • Clickbait that doesn't deliver
  • Generic/vague subjects
  • Spam trigger words

Length: 4-7 words typically performs best.

Opening Lines

Strong openers:

  • Relevant observation about them
  • Trigger event reference
  • Mutual connection mention
  • Direct value statement

Weak openers:

  • "I hope this email finds you well"
  • "My name is... and I work at..."
  • "I wanted to reach out because..."
  • "I know you're busy, but..."

Examples:

Weak: "Hi, my name is Alex and I'm a sales rep at XYZ Corp." Strong: "Noticed [Company] just expanded into the enterprise segment—congrats on the growth."

Weak: "I wanted to reach out to introduce our platform." Strong: "Companies like [similar company] are cutting their sales cycle by 30% with one change to their outreach."

Body Copy

Keep it:

  • Short (50-150 words for cold email)
  • Scannable (short paragraphs, bullets if needed)
  • Focused on one main point
  • Relevant to their situation

Structure:

  1. Hook (personalized connection or insight)
  2. Value (what's in it for them)
  3. Proof (quick credibility)
  4. CTA (clear next step)

Calls to Action

Effective CTAs:

  • Specific: "Are you free Tuesday at 2pm?"
  • Low commitment: "Worth a 15-minute conversation?"
  • Easy to answer: "Interested?" (they can reply yes/no)
  • Action-oriented: "Let me know and I'll send over..."

Weak CTAs:

  • "Let me know if you're interested"
  • "I'd love to connect sometime"
  • "Feel free to reach out"
  • Multiple asks in one email

Cold Email Templates

The Problem-Solution Email

Subject: [Their problem] at [Company]?

Hi [Name],

[Observation about their situation or trigger event].

[Role]s at companies like [Company] often struggle with [specific problem].
It leads to [negative consequence].

We've helped [similar companies] [achieve result] by [brief solution].

Worth a quick chat to see if we could do the same for you?

[Your name]

The Social Proof Email

Subject: How [Similar Company] [achieved result]

Hi [Name],

[Similar Company] was dealing with [problem you solve].
Within [timeframe], they [achieved specific result].

We helped them by [brief approach].

Given [Company]'s focus on [their priority], thought this might be relevant.

Interested in hearing how they did it?

[Your name]

The Insight Email

Subject: [Insight related to their business]

Hi [Name],

[Relevant insight or observation about their industry/situation].

I work with [role]s at [company type] on [related topic],
and this pattern is becoming more common.

Happy to share what's working—worth a conversation?

[Your name]

The Referral Email

Subject: [Mutual connection] suggested I reach out

Hi [Name],

[Mutual connection] mentioned you're working on [challenge/initiative].

We recently helped [similar company] with [related problem] and
[achieved result].

[Mutual connection] thought there might be a fit—any interest in a
quick conversation?

[Your name]

Follow-Up Emails

Follow-Up Principles

  • Add value, don't just "check in"
  • Vary your approach
  • Keep it short
  • Reference previous outreach

Follow-Up Sequence

Follow-up 1 (Day 3): Add a new angle or piece of value.

Subject: RE: [original subject]

Hi [Name],

Quick follow-up—wanted to share [relevant article/insight/case study]
that relates to [their situation].

Still worth connecting?

[Your name]

Follow-up 2 (Day 7): Try a different hook.

Subject: RE: [original subject]

Hi [Name],

Not sure if [problem] is top of mind right now.

If it is, [one line about how you help].
If not, no worries—happy to reconnect when timing is better.

Either way, let me know?

[Your name]

Follow-up 3 (Day 14): The breakup email.

Subject: Should I close your file?

Hi [Name],

Haven't heard back, which usually means one of three things:

1. You're swamped right now
2. This isn't a priority
3. You're not the right person

If it's 1 or 2, I'm happy to follow up later or close the loop.
If it's 3, could you point me in the right direction?

Either way, thanks for your time.

[Your name]

Proposal Writing

Proposal Structure

  1. Executive Summary

- Their challenge - Your solution - Expected outcomes - Investment overview

  1. Understanding

- Recap of their situation - Goals they've shared - Confirms you listened

  1. Approach

- How you'll solve it - Implementation plan - Timeline

  1. Outcomes

- Expected results - Success metrics - Case study evidence

  1. Investment

- Pricing - What's included - Payment terms

  1. Next Steps

- Clear action to proceed - Contact information

Proposal Best Practices

Do:

  • Customize to their specific situation
  • Use their language and terminology
  • Include specific numbers and timelines
  • Make it easy to say yes
  • Lead with value, not price

Don't:

  • Copy-paste generic proposals
  • Make it about you instead of them
  • Bury the price
  • Include irrelevant information
  • Use jargon they won't understand

Professional Communication

Email Etiquette

Formatting:

  • Short paragraphs (2-3 sentences max)
  • Use bullet points for lists
  • Bold key information sparingly
  • Mobile-friendly formatting

Tone:

  • Professional but human
  • Confident, not arrogant
  • Helpful, not pushy
  • Match their communication style

Timing:

  • Response time matters
  • Reply within same business day when possible
  • Use scheduling tools for optimal send times

Common Mistakes

The Wall of Text:

  • Break into paragraphs
  • Cut unnecessary words
  • Make it scannable

The Self-Focused Email:

  • Flip "I/we" statements to "you"
  • Focus on their outcomes
  • Show you understand them

The Weak Ask:

  • Be specific about next step
  • Make it easy to say yes
  • Don't apologize for asking

The Over-Explanation:

  • They don't need every detail
  • Tease value, deliver in conversation
  • Less is more

Editing Your Writing

The Editing Process

First pass: Cut unnecessary words Second pass: Strengthen weak language Third pass: Check the CTA is clear Fourth pass: Read aloud (does it sound natural?)

Words to Cut

  • "Just" (just following up → following up)
  • "Really" (really excited → excited)
  • "Very" (very important → important)
  • "Actually" (actually → [delete])
  • "In order to" (in order to → to)
  • "I think" / "I believe" (state directly)

Weak → Strong Language

WeakStrong
"I was wondering if maybe...""Would you..."
"We provide solutions...""We help [persona] [achieve outcome]..."
"Let me know if interested""Interested?"
"I wanted to reach out"[Just reach out]
"Don't hesitate to..."[Just ask]

Writing for Different Mediums

Email vs. LinkedIn

Email:

  • Can be slightly longer
  • More formal structure
  • Include signature

LinkedIn:

  • Keep shorter (150 words max)
  • More conversational
  • No signature block needed

Text/SMS

  • Very short (1-2 sentences)
  • Casual tone
  • Clear CTA
  • Only when relationship warrants

Proposal vs. One-Pager

Proposal:

  • Detailed, comprehensive
  • For final decision-making
  • Customized to their specific situation

One-pager:

  • High-level overview
  • For initial interest or internal sharing
  • More standard, less customized

Practice Exercises

1. The Cut Challenge

Take an email and cut 50% of the words while keeping the meaning.

2. The "You" Flip

Rewrite an email to start every paragraph with "You" or "Your."

3. The Subject Line Test

Write 10 subject lines for the same email. A/B test the best 2.

4. The Read-Aloud Test

Read your email aloud. If it sounds awkward, rewrite it.

5. The Response Review

Look at emails that got responses. What did they have in common?


Questions to Ask

If you need more context:

  1. What type of written communication do you send most?
  2. What response rates are you currently seeing?
  3. Can you share an example email you've sent?
  4. Who is your target audience?
  5. What action are you trying to drive?

Related Skills

  • email-sequence: For building automated email sequences
  • copywriting: For persuasive writing techniques
  • follow-up-discipline: For consistent follow-up cadence
  • social-selling: For LinkedIn messaging

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.62%
按下载量换算23

Claude

28.47%
按下载量换算18

Cursor

19.25%
按下载量换算12

Gemini CLI

9.58%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills