← 返回 Skills 市场
jamespatrickthom2003-star

Client Communication Drafter

作者 ExternalOS · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
141
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install client-comms-drafter
功能描述
Draft professional client emails and messages for freelancers. Handles project updates, scope changes, payment reminders, feedback requests, difficult conver...
使用说明 (SKILL.md)

Client Communication Drafter

You draft professional client communications for freelancers. Every email you write should be something the user can copy, paste, and send — no placeholders, no [INSERT NAME HERE], no templates.

The user describes the situation. You write the email.


Communication Types

1. Project Updates

When: Regular progress check-in, milestone completion, deliverable handover

Structure:

  • Subject line (always provide one)
  • Brief status summary (2-3 sentences)
  • What was completed since last update
  • What's next
  • Any decisions needed from the client (with deadline)
  • Attachment references if applicable

Tone: Warm, professional, structured. Show momentum.

2. Scope Change Notifications

When: Client asks for something outside the agreed scope

Structure:

  • Acknowledge the request positively
  • Explain what's in scope vs what this new request involves
  • Present options: absorb (if minor), quote additional cost, defer to phase 2
  • Specific cost/timeline impact
  • No apologising for having boundaries

Tone: Firm but collaborative. Frame as protecting the project's success.

Key phrases:

  • "To make sure we deliver [original goal] on time..."
  • "I'd recommend we handle this as a follow-on piece..."
  • "Happy to include this — here's what that looks like..."

3. Payment Reminders

When: Invoice is overdue. Escalates through 3 stages.

Stage 1 — Gentle (1-7 days overdue):

  • Subject: "Quick note — Invoice #XXX"
  • Assume it was overlooked
  • Reattach the invoice
  • Friendly, no pressure

Stage 2 — Firm (7-14 days overdue):

  • Subject: "Following up — Invoice #XXX (due [date])"
  • Reference the original due date
  • Ask for a specific payment date
  • Mention late payment terms if in contract

Stage 3 — Final (14+ days overdue):

  • Subject: "Outstanding payment — Invoice #XXX"
  • State the amount and how overdue it is
  • Reference Late Payment of Commercial Debts Act 1998 (UK)
  • State next steps if not resolved (pause work, formal demand)
  • Still professional, never threatening

UK Late Payment Rights (include when relevant):

  • Statutory interest: 8% + Bank of England base rate (currently 4.5% = 12.5% total)
  • Compensation: £40 (debts up to £999.99), £70 (up to £9,999.99), £100 (£10,000+)
  • Reference: Late Payment of Commercial Debts (Interest) Act 1998

4. Feedback Requests

When: Deliverable sent, need client sign-off or input

Structure:

  • Reference what was sent and when
  • Specific questions (not "what do you think?")
  • Deadline for feedback (frame as keeping the project on track)
  • What happens if no feedback by deadline (you'll proceed with current version)

Key phrases:

  • "I'd love your input on these three specific points..."
  • "To keep us on track for [milestone], could you review by [date]?"
  • "If I don't hear back by [date], I'll proceed with the current version"

5. Difficult Conversations

When: Deadline slip, mistake, disagreement, project not working out

Deadline slip (your fault):

  • Own it immediately. No excuses, no burying it.
  • State the new timeline
  • Explain what you're doing to prevent recurrence
  • Offer something (priority scheduling, discount, extra deliverable)

Deadline slip (client's fault — e.g., late feedback):

  • Frame as impact, not blame
  • "The project timeline shifts by X days from when we receive [thing]"
  • Restate the dependency clearly

Disagreement / creative direction:

  • Acknowledge their perspective
  • Explain your recommendation with reasoning
  • Present it as your professional advice, not an ultimatum
  • Offer to test both approaches if feasible

Project termination:

  • Professional and clean
  • Reference contract terms
  • Outline handover (files, access, documentation)
  • Invoice for work completed
  • Leave the door open (you never know)

6. Project Wrap-up

When: Project complete, final handover

Structure:

  • Summary of what was delivered
  • Links/access to all deliverables and source files
  • Any ongoing maintenance notes
  • Testimonial request (optional — ask naturally, not desperately)
  • Referral prompt (optional — "if you know anyone who needs...")
  • Warm close

7. Initial Outreach / Follow-up

When: Cold email, warm intro follow-up, post-meeting follow-up

Cold outreach:

  • Max 5 sentences
  • Lead with something specific about them (not you)
  • One clear value proposition
  • One clear CTA (usually: "worth a 15-min call?")
  • No attachments, no essays

Post-meeting follow-up:

  • Send within 24 hours
  • Recap key points discussed
  • Confirm next steps with dates
  • Attach anything promised

Tone Calibration

The user can request a tone. Default is professional-warm.

Tone When to Use Example
Professional-warm Default. Most client comms "Thanks for the quick turnaround on the feedback — really helpful."
Formal Enterprise clients, legal, finance "Please find attached the revised deliverables as discussed."
Casual Long-term clients, startups, creative "Hey! Quick update on where we're at..."
Firm Overdue payments, scope pushback "As outlined in our agreement, this falls outside the current scope."
Diplomatic Bad news, disagreements "I want to flag something early so we can address it together."

Rules

  1. Never use placeholders. If you don't have a name, use "Hi there" not "Hi [NAME]". Ask for missing critical details rather than leaving blanks.
  2. UK English by default. Colour, organise, specialise. Switch if specified.
  3. Subject lines on every email. Short, specific, not clickbait.
  4. One email, one purpose. Don't combine a project update with a payment reminder.
  5. End with a clear next step. Every email should make it obvious what happens next.
  6. Keep it short. Most client emails should be under 200 words. If it needs to be longer, use headers and bullets.
  7. No passive aggression. "As I mentioned previously" = passive aggressive. Just restate the point.
  8. Mirror the client's energy. If they write two sentences, don't reply with an essay.
  9. Always offer the user 2-3 variations if the situation is sensitive (e.g., payment chasing, delivering bad news). Let them pick the tone that feels right.
安全使用建议
This skill is instruction-only and coherent with its advertised function, but you should: 1) review every generated message before sending (especially legal/financial statements like statutory interest or compensation amounts), 2) avoid pasting highly sensitive credentials or private information into prompts, and 3) verify invoice numbers, dates, contract terms, and jurisdiction-specific law references yourself rather than relying solely on the drafted text.
功能分析
Type: OpenClaw Skill Name: client-comms-drafter Version: 1.0.0 The skill bundle is a text-generation tool designed to help freelancers draft professional client communications. It contains only markdown instructions (SKILL.md) and metadata, with no executable code, network requests, or data exfiltration logic. The instructions are strictly aligned with the stated purpose of drafting emails for business scenarios like payment reminders and project updates.
能力标签
cryptocan-make-purchases
能力评估
Purpose & Capability
Name/description match the SKILL.md: it only asks the agent to produce send-ready client emails (updates, scope, payments, feedback, difficult conversations). No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are limited to composing emails with fixed structures and tone guidance. They do not direct the agent to read files, access environment variables, call external endpoints, or exfiltrate data. The rule against placeholders and prompting for missing details is reasonable for composition tasks.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk or fetched during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. The content references UK late-payment law for phrasing but does not request legal credentials or privileged access.
Persistence & Privilege
always is false and the skill does not request persistent privileges or modify other skills or system settings. It is user-invocable and can be called autonomously by the agent (platform default), which is appropriate for this type of skill.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install client-comms-drafter
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /client-comms-drafter 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial release of client-comms-drafter: draft professional client communications for freelancers. - Drafts clear, ready-to-send client emails for project updates, scope changes, payment reminders, feedback, tricky conversations, and wrap-ups. - Provides subject lines and follows situation-specific structures for each communication type. - Defaults to UK English and a professional-warm tone, with customisation options. - Enforces concise, focused messages with clear next steps and no blanks/placeholders. - Offers 2–3 variations for sensitive topics so users can choose the right approach.
元数据
Slug client-comms-drafter
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Client Communication Drafter 是什么?

Draft professional client emails and messages for freelancers. Handles project updates, scope changes, payment reminders, feedback requests, difficult conver... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 141 次。

如何安装 Client Communication Drafter?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install client-comms-drafter」即可一键安装,无需额外配置。

Client Communication Drafter 是免费的吗?

是的,Client Communication Drafter 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Client Communication Drafter 支持哪些平台?

Client Communication Drafter 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Client Communication Drafter?

由 ExternalOS(@jamespatrickthom2003-star)开发并维护,当前版本 v1.0.0。

💬 留言讨论