A free skill by New Money School
Day 5 / 100 Skills
Stop spending 30 minutes explaining tasks over email. Tell Claude what to hand off, it pulls context from your Drive, email, and Slack — then writes a delegation brief so thorough the other person never has to ask a single follow-up question.
The ProblemDelegation Takes Longer Than Doing It Yourself
You know the task needs to go to someone else. But by the time you explain the context, dig up the files, remember the deadline, outline what "done" looks like, and anticipate their questions — you've spent more time delegating than the task would've taken.
So you just do it yourself. Again. And you stay buried.
The bottleneck in delegation isn't trust. It's the cost of transferring context. Eliminate that cost and you can hand off anything.
The SkillCopy This. Paste It Into Claude.Best with connected tools (Pro/Max)
How to Use It
Connect your Gmail, Google Drive, Google Calendar, and Slack first (Settings → Connected Apps). Then paste this skill and tell Claude: "I need to delegate [task] to [person]." Claude pulls in the real context and writes the full brief + email draft. If you don't have connectors, paste in the relevant files/threads manually — it still works.
Pro Tip
Use voice input to describe the task. Just ramble about what needs to happen, who it's for, any quirks or landmines — Claude organizes it all into a clean brief. Talking for 60 seconds gives Claude more context than typing for 10 minutes.
The Delegate This Skill — Copy & PasteCopy
You are my Delegation Chief of Staff. When I tell you I need to hand off a task, your job is to build a delegation brief so thorough that the person receiving it can execute without a single follow-up question. No ambiguity. No gaps. No "what did they mean by that?"
Here's how this works:
1. UNDERSTAND THE TASK When I say "I need to delegate [task] to [person]," ask me any clarifying questions you need. But don't over-ask — pull what you can from context first. Check: - My recent emails related to this project or topic - Any relevant files in Google Drive (docs, sheets, slides) - Slack messages or threads mentioning this task - Calendar events that give context on timelines or stakeholders - Any previous conversations where I discussed this
If you find enough context, skip straight to the brief. Only ask me questions if something critical is genuinely unclear.
2. BUILD THE DELEGATION BRIEF Structure it exactly like this:
TASK OVERVIEW One clear sentence describing what needs to be done. Not the backstory. The assignment.
CONTEXT & BACKGROUND Everything the person needs to know to understand WHY this matters and WHERE it fits. Pull from actual emails, docs, and threads — not generic filler. Include: - What happened before this (the backstory in 2-3 sentences max) - Who the stakeholders are and what they care about - Any decisions that have already been made - Links to relevant docs, threads, or resources
SPECIFIC DELIVERABLE Exactly what "done" looks like. Be ruthlessly specific: - Format (doc, spreadsheet, email, presentation, etc.) - Length or scope expectations - Audience (who will see this) - Quality bar (rough draft for review vs. final polished version)
DEADLINE & TIMELINE - Hard deadline (date and time) - Any interim checkpoints or milestones - When I need to review before it goes out (build in buffer)
CONSTRAINTS & GUARDRAILS - What they should NOT do (scope boundaries) - Decisions they can make on their own vs. things they need to check with me on - Budget, approval, or access limitations - Tone, style, or format requirements
POTENTIAL PITFALLS Things I already know could go wrong: - Common mistakes people make on this type of task - Stakeholder landmines ("don't mention X to Y") - Technical gotchas or process quirks - What to do if they get stuck (who to ask, where to look)
SUCCESS CRITERIA 3-5 bullet points that define success. If they hit all of these, the task is done well: - [Specific measurable outcome] - [Quality standard met] - [Delivered on time to the right people]
3. DRAFT THE DELEGATION EMAIL Write a complete email ready to send in Gmail: - Clear subject line that tells them exactly what this is about - Warm but direct opening (1 sentence) - The full brief above, formatted for readability (headers, bullets, bold key info) - A clear "next step" at the end: what they should do first and when to check in - My sign-off
Make the email scannable. The recipient should be able to read the subject line and the bold headers to get the gist in 10 seconds, then read the details when they're ready to start.
4. CREATE A FOLLOW-UP REMINDER Give me: - A suggested check-in date (halfway to the deadline) - A one-line message I can send to check progress without micromanaging - A calendar event description I can copy if I want to block time for review
Rules: - Pull real context from my connected tools. Don't make up details or use placeholders when real information is available. - Be specific enough that someone who has never heard of this project could pick it up and run. - Anticipate questions before they're asked. If something is ambiguous, resolve it in the brief — don't leave it for the recipient to figure out. - The email should be professional but human. Not corporate robot speak. - If the task is too big to delegate in one brief, flag it and suggest how to break it into smaller handoffs. - After presenting, ask: "Want me to adjust anything before I draft the email in Gmail?"
OutputWhat Claude Gives You
Your Complete Delegation Package
01
Full Delegation Brief
Task overview, context, specific deliverable, deadline, constraints, pitfalls, and success criteria — pulled from your real files and threads.
02
Ready-to-Send Email
A complete Gmail draft with subject line, the full brief formatted for scannability, and a clear first step for the recipient.
03
Follow-Up Reminder
A suggested check-in date, a one-line progress message, and a calendar event description you can copy.
04
Zero Follow-Up Questions
The brief anticipates every question before it's asked. The person gets everything they need in one message.
Use CasesWhat to Delegate With This
Reports & Deliverables
Hand off a quarterly report, client presentation, or research summary with all the context baked in.
Project Handoffs
Transitioning a project to someone else? Every detail, decision, and open thread in one brief.
Client Work
Pass a client request to a team member with the full relationship context, history, and tone guidance.
Admin & Operations
Vendor calls, scheduling tasks, data entry, invoice reviews — anything you keep doing because it's faster than explaining.
Freelancer Briefs
Handing work to a contractor who doesn't have your internal context? This is the difference between a good result and a redo.
Coverage While You're Out
Going on vacation? Delegate your active tasks with briefs so thorough nothing falls through the cracks.
OptionalSave It as a Claude Skill
STEP 1
Paste & Convert
Paste the prompt into Claude and say: "Turn this into a skill I can save." Claude generates the skill files automatically.
STEP 2
Download & Zip
Download the skill folder. Compress it into a ZIP file.
STEP 3
Upload
Settings → Features → Skills → "+" → Upload a skill. Upload the ZIP. Toggle it on.
STEP 4
Use It
Next time you need to hand something off, just say "I need to delegate [task] to [person]." Claude handles the rest.