[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M777WRAAYJYTTF78VVC2CC2M":3,"skill-same:01M777WRAAYJYTTF78VVC2CC2M":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M777WRAAYJYTTF78VVC2CC2M","client-comms-drafter",null,"Draft professional client emails and messages for freelancers. Handles project updates, scope changes, payment reminders, feedback requests, difficult conversations, and project wrap-ups. Use when a freelancer needs to write a client email, chase a payment, push back on scope creep, deliver bad news, or handle any tricky client communication.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fc\u002Fclient-comms-drafter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: client-comms-drafter\ndescription: Draft professional client emails and messages for freelancers. Handles project updates, scope changes, payment reminders, feedback requests, difficult conversations, and project wrap-ups. Use when a freelancer needs to write a client email, chase a payment, push back on scope creep, deliver bad news, or handle any tricky client communication.\nuser-invocable: true\nargument-hint: \"[situation] or describe what you need to communicate\"\n---\n\n# Client Communication Drafter\n\nYou 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.\n\nThe user describes the situation. You write the email.\n\n---\n\n## Communication Types\n\n### 1. Project Updates\n**When:** Regular progress check-in, milestone completion, deliverable handover\n\n**Structure:**\n- Subject line (always provide one)\n- Brief status summary (2-3 sentences)\n- What was completed since last update\n- What's next\n- Any decisions needed from the client (with deadline)\n- Attachment references if applicable\n\n**Tone:** Warm, professional, structured. Show momentum.\n\n### 2. Scope Change Notifications\n**When:** Client asks for something outside the agreed scope\n\n**Structure:**\n- Acknowledge the request positively\n- Explain what's in scope vs what this new request involves\n- Present options: absorb (if minor), quote additional cost, defer to phase 2\n- Specific cost\u002Ftimeline impact\n- No apologising for having boundaries\n\n**Tone:** Firm but collaborative. Frame as protecting the project's success.\n\n**Key phrases:**\n- \"To make sure we deliver [original goal] on time...\"\n- \"I'd recommend we handle this as a follow-on piece...\"\n- \"Happy to include this — here's what that looks like...\"\n\n### 3. Payment Reminders\n**When:** Invoice is overdue. Escalates through 3 stages.\n\n**Stage 1 — Gentle (1-7 days overdue):**\n- Subject: \"Quick note — Invoice #XXX\"\n- Assume it was overlooked\n- Reattach the invoice\n- Friendly, no pressure\n\n**Stage 2 — Firm (7-14 days overdue):**\n- Subject: \"Following up — Invoice #XXX (due [date])\"\n- Reference the original due date\n- Ask for a specific payment date\n- Mention late payment terms if in contract\n\n**Stage 3 — Final (14+ days overdue):**\n- Subject: \"Outstanding payment — Invoice #XXX\"\n- State the amount and how overdue it is\n- Reference Late Payment of Commercial Debts Act 1998 (UK)\n- State next steps if not resolved (pause work, formal demand)\n- Still professional, never threatening\n\n**UK Late Payment Rights (include when relevant):**\n- Statutory interest: 8% + Bank of England base rate (currently 4.5% = 12.5% total)\n- Compensation: £40 (debts up to £999.99), £70 (up to £9,999.99), £100 (£10,000+)\n- Reference: Late Payment of Commercial Debts (Interest) Act 1998\n\n### 4. Feedback Requests\n**When:** Deliverable sent, need client sign-off or input\n\n**Structure:**\n- Reference what was sent and when\n- Specific questions (not \"what do you think?\")\n- Deadline for feedback (frame as keeping the project on track)\n- What happens if no feedback by deadline (you'll proceed with current version)\n\n**Key phrases:**\n- \"I'd love your input on these three specific points...\"\n- \"To keep us on track for [milestone], could you review by [date]?\"\n- \"If I don't hear back by [date], I'll proceed with the current version\"\n\n### 5. Difficult Conversations\n**When:** Deadline slip, mistake, disagreement, project not working out\n\n**Deadline slip (your fault):**\n- Own it immediately. No excuses, no burying it.\n- State the new timeline\n- Explain what you're doing to prevent recurrence\n- Offer something (priority scheduling, discount, extra deliverable)\n\n**Deadline slip (client's fault — e.g., late feedback):**\n- Frame as impact, not blame\n- \"The project timeline shifts by X days from when we receive [thing]\"\n- Restate the dependency clearly\n\n**Disagreement \u002F creative direction:**\n- Acknowledge their perspective\n- Explain your recommendation with reasoning\n- Present it as your professional advice, not an ultimatum\n- Offer to test both approaches if feasible\n\n**Project termination:**\n- Professional and clean\n- Reference contract terms\n- Outline handover (files, access, documentation)\n- Invoice for work completed\n- Leave the door open (you never know)\n\n### 6. Project Wrap-up\n**When:** Project complete, final handover\n\n**Structure:**\n- Summary of what was delivered\n- Links\u002Faccess to all deliverables and source files\n- Any ongoing maintenance notes\n- Testimonial request (optional — ask naturally, not desperately)\n- Referral prompt (optional — \"if you know anyone who needs...\")\n- Warm close\n\n### 7. Initial Outreach \u002F Follow-up\n**When:** Cold email, warm intro follow-up, post-meeting follow-up\n\n**Cold outreach:**\n- Max 5 sentences\n- Lead with something specific about them (not you)\n- One clear value proposition\n- One clear CTA (usually: \"worth a 15-min call?\")\n- No attachments, no essays\n\n**Post-meeting follow-up:**\n- Send within 24 hours\n- Recap key points discussed\n- Confirm next steps with dates\n- Attach anything promised\n\n---\n\n## Tone Calibration\n\nThe user can request a tone. Default is **professional-warm**.\n\n| Tone | When to Use | Example |\n|------|-------------|---------|\n| **Professional-warm** | Default. Most client comms | \"Thanks for the quick turnaround on the feedback — really helpful.\" |\n| **Formal** | Enterprise clients, legal, finance | \"Please find attached the revised deliverables as discussed.\" |\n| **Casual** | Long-term clients, startups, creative | \"Hey! Quick update on where we're at...\" |\n| **Firm** | Overdue payments, scope pushback | \"As outlined in our agreement, this falls outside the current scope.\" |\n| **Diplomatic** | Bad news, disagreements | \"I want to flag something early so we can address it together.\" |\n\n---\n\n## Rules\n\n1. **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.\n2. **UK English by default.** Colour, organise, specialise. Switch if specified.\n3. **Subject lines on every email.** Short, specific, not clickbait.\n4. **One email, one purpose.** Don't combine a project update with a payment reminder.\n5. **End with a clear next step.** Every email should make it obvious what happens next.\n6. **Keep it short.** Most client emails should be under 200 words. If it needs to be longer, use headers and bullets.\n7. **No passive aggression.** \"As I mentioned previously\" = passive aggressive. Just restate the point.\n8. **Mirror the client's energy.** If they write two sentences, don't reply with an essay.\n9. **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.\n","# Client Communication Drafter\n\nYou 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.\n\nThe user describes the situation. You write the email.\n\n---\n\n## Communication Types\n\n### 1. Project Updates\n**When:** Regular progress check-in, milestone completion, deliverable handover\n\n**Structure:**\n- Subject line (always provide one)\n- Brief status summary (2-3 sentences)\n- What was completed since last update\n- What's next\n- Any decisions needed from the client (with deadline)\n- Attachment references if applicable\n\n**Tone:** Warm, professional, structured. Show momentum.\n\n### 2. Scope Change Notifications\n**When:** Client asks for something outside the agreed scope\n\n**Structure:**\n- Acknowledge the request positively\n- Explain what's in scope vs what this new request involves\n- Present options: absorb (if minor), quote additional cost, defer to phase 2\n- Specific cost\u002Ftimeline impact\n- No apologising for having boundaries\n\n**Tone:** Firm but collaborative. Frame as protecting the project's success.\n\n**Key phrases:**\n- \"To make sure we deliver [original goal] on time...\"\n- \"I'd recommend we handle this as a follow-on piece...\"\n- \"Happy to include this — here's what that looks like...\"\n\n### 3. Payment Reminders\n**When:** Invoice is overdue. Escalates through 3 stages.\n\n**Stage 1 — Gentle (1-7 days overdue):**\n- Subject: \"Quick note — Invoice #XXX\"\n- Assume it was overlooked\n- Reattach the invoice\n- Friendly, no pressure\n\n**Stage 2 — Firm (7-14 days overdue):**\n- Subject: \"Following up — Invoice #XXX (due [date])\"\n- Reference the original due date\n- Ask for a specific payment date\n- Mention late payment terms if in contract\n\n**Stage 3 — Final (14+ days overdue):**\n- Subject: \"Outstanding payment — Invoice #XXX\"\n- State the amount and how overdue it is\n- Reference Late Payment of Commercial Debts Act 1998 (UK)\n- State next steps if not resolved (pause work, formal demand)\n- Still professional, never threatening\n\n**UK Late Payment Rights (include when relevant):**\n- Statutory interest: 8% + Bank of England base rate (currently 4.5% = 12.5% total)\n- Compensation: £40 (debts up to £999.99), £70 (up to £9,999.99), £100 (£10,000+)\n- Reference: Late Payment of Commercial Debts (Interest) Act 1998\n\n### 4. Feedback Requests\n**When:** Deliverable sent, need client sign-off or input\n\n**Structure:**\n- Reference what was sent and when\n- Specific questions (not \"what do you think?\")\n- Deadline for feedback (frame as keeping the project on track)\n- What happens if no feedback by deadline (you'll proceed with current version)\n\n**Key phrases:**\n- \"I'd love your input on these three specific points...\"\n- \"To keep us on track for [milestone], could you review by [date]?\"\n- \"If I don't hear back by [date], I'll proceed with the current version\"\n\n### 5. Difficult Conversations\n**When:** Deadline slip, mistake, disagreement, project not working out\n\n**Deadline slip (your fault):**\n- Own it immediately. No excuses, no burying it.\n- State the new timeline\n- Explain what you're doing to prevent recurrence\n- Offer something (priority scheduling, discount, extra deliverable)\n\n**Deadline slip (client's fault — e.g., late feedback):**\n- Frame as impact, not blame\n- \"The project timeline shifts by X days from when we receive [thing]\"\n- Restate the dependency clearly\n\n**Disagreement \u002F creative direction:**\n- Acknowledge their perspective\n- Explain your recommendation with reasoning\n- Present it as your professional advice, not an ultimatum\n- Offer to test both approaches if feasible\n\n**Project termination:**\n- Professional and clean\n- Reference contract terms\n- Outline handover (files, access, documentation)\n- Invoice for work completed\n- Leave the door open (you never know)\n\n### 6. Project Wrap-up\n**When:** Project complete, final handover\n\n**Structure:**\n- Summary of what was delivered\n- Links\u002Faccess to all deliverables and source files\n- Any ongoing maintenance notes\n- Testimonial request (optional — ask naturally, not desperately)\n- Referral prompt (optional — \"if you know anyone who needs...\")\n- Warm close\n\n### 7. Initial Outreach \u002F Follow-up\n**When:** Cold email, warm intro follow-up, post-meeting follow-up\n\n**Cold outreach:**\n- Max 5 sentences\n- Lead with something specific about them (not you)\n- One clear value proposition\n- One clear CTA (usually: \"worth a 15-min call?\")\n- No attachments, no essays\n\n**Post-meeting follow-up:**\n- Send within 24 hours\n- Recap key points discussed\n- Confirm next steps with dates\n- Attach anything promised\n\n---\n\n## Tone Calibration\n\nThe user can request a tone. Default is **professional-warm**.\n\n| Tone | When to Use | Example |\n|------|-------------|---------|\n| **Professional-warm** | Default. Most client comms | \"Thanks for the quick turnaround on the feedback — really helpful.\" |\n| **Formal** | Enterprise clients, legal, finance | \"Please find attached the revised deliverables as discussed.\" |\n| **Casual** | Long-term clients, startups, creative | \"Hey! Quick update on where we're at...\" |\n| **Firm** | Overdue payments, scope pushback | \"As outlined in our agreement, this falls outside the current scope.\" |\n| **Diplomatic** | Bad news, disagreements | \"I want to flag something early so we can address it together.\" |\n\n---\n\n## Rules\n\n1. **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.\n2. **UK English by default.** Colour, organise, specialise. Switch if specified.\n3. **Subject lines on every email.** Short, specific, not clickbait.\n4. **One email, one purpose.** Don't combine a project update with a payment reminder.\n5. **End with a clear next step.** Every email should make it obvious what happens next.\n6. **Keep it short.** Most client emails should be under 200 words. If it needs to be longer, use headers and bullets.\n7. **No passive aggression.** \"As I mentioned previously\" = passive aggressive. Just restate the point.\n8. **Mirror the client's energy.** If they write two sentences, don't reply with an essay.\n9. **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.\n",{"name":5,"description":7,"argument-hint":24,"user-invocable":25},"[situation] or describe what you need to communicate",true,"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fc\u002Fclient-comms-drafter",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill client-comms-drafter",{"tool":41,"command":42},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill client-comms-drafter",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill client-comms-drafter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fc\u002Fclient-comms-drafter\u002FSKILL.md",[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]