upwork-client-messenger
Draft mid-contract messages to a freelance client on Upwork or similar platforms. Use when the user needs to deliver delay news, push back on scope creep, raise their rate, end a contract gracefully, or ask for a review. Triggers include "reply to my client", "tell the client it's delayed", "client keeps adding scope", "raise my rate", "end this contract", "ask for a review", "client is ghosting". Input is the situation plus the relevant thread context, pasted. Drafts in the voice of a working professional peer, never a permission-seeker.
Profile →npx skills add abullaisi/upwork-skills --skill upwork-client-messenger --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Upwork Client Messenger Mid-contract messages decide whether a contract ends in a review and a referral or in silence. Method extracted from a Top Rated Plus freelancer's real client threads across long and short engagements, plus published guidance. The through-line: state facts plainly, never litigate, and let structure do the negotiating. ## Inputs 1. **The situation** (which of the five below). 2. **Thread context**, pasted: what was agreed, what changed, the client's last few messages. 3. **Engagement type: long-term relationship or short transactional contract.** Several moves below fork on this; ask if unclear. If it isn't stated and can't be inferred, ask once and draft both closings so the user isn't blocked on your question. Profile shortcut: if a stored profile file exists (`upwork-profile.md` in the working directory or `~/.claude/`), read identity and rate context from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask). ## Voice (hard, applies to all five) Professional peer, warm and short. Contractions, plain words, no em dashes. **Banned: permission-seeking and apology stacking.** "Can I possibly ask if maybe" is
- Inputs
- Voice (hard, applies to all five)
- 1. Delay news
- 2. Scope creep (the fork that matters most)
- 3. Rate increase
- 4. Ending a contract
- 5. Review ask
- Privacy rule (hard)
- Sources and provenance
What does the upwork-client-messenger skill do?
Draft mid-contract messages to a freelance client on Upwork or similar platforms. Use when the user needs to deliver delay news, push back on scope creep, raise their rate, end a contract gracefully, or ask for a review. Triggers include "reply to my client", "tell the client it's delayed", "client keeps adding scope", "raise my rate", "end this contract", "ask for a review", "client is ghosting". Input is the situation plus the relevant thread context, pasted. Drafts in the voice of a working professional peer, never a permission-seeker.
How do I install it?
Run `npx skills add abullaisi/upwork-skills --skill upwork-client-messenger --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From abullaisi/upwork-skills, a repository with 86 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.