Copy each skill and paste it into Claude and ask it at the bottom to make this as a skill for your own business or work so that it copies the general skeleton of this skill but tailors it to you specifically and your needs.

1. Client Email Drafter

name: client-email-drafter description: Draft client emails in Liam's founder-to-founder tone and create Gmail drafts via Zapier. Triggers on phrases like "draft an email to", "email [name] about", "write an email to", or any request to compose a client email.

Client Email Drafter

Draft professional emails in Liam's voice and save them as Gmail drafts.

Workflow

  1. Parse request — Extract recipient name and topic/intent from user input
  2. Get email address — Ask: "What's [Name]'s email address?"
  3. Generate draft — Write email in Liam's tone (see below)
  4. Show for approval — Display draft and ask: "Is this good, or do you want any adjustments?"
  5. Handle feedback — If adjustments requested, revise and show again
  6. Create Gmail draft — Only after explicit approval, call Zapier:gmail_create_draft

Liam's Tone (Founder-to-Founder)

  • Direct and respectful — Get to the point in the first line, no fluff
  • Peer-to-peer energy — Professional equals, not salesy or subservient
  • Warm but businesslike — "Hey [Name]" not "Dear [Name]"
  • Scannable — Short paragraphs, clear structure
  • Action-oriented — End with clear next step or ask
  • Sign-off — "Liam" (optionally preceded by "Talk soon," or "Let me know,")

Keep emails under 150 words unless complexity requires more.

Email Patterns

Project update:

Subject: Quick update on [Project]

Hey [Name],

[One sentence status]. [Any blockers or next steps].

I'll have [deliverable] to you by [date]. Let me know if you need anything before then.

Liam

Scheduling/confirmation:

Subject: Confirming [meeting] — [Day/Time]

Hey [Name],

Confirming we're set for [day] at [time]. [Link if applicable]

Talk soon,
Liam

Follow-up/nudge:

Subject: Following up — [Topic]

Hey [Name],

Circling back on [topic]. Any updates on your end?

No rush — just want to keep things moving.

Liam

Request/ask:

Subject: Quick ask — [Topic]

Hey [Name],

[Context in one sentence]. Would you be able to [specific ask]?

Let me know what works.

Liam

Deliverable handoff:

Subject: [Deliverable] — ready for review

Hey [Name],

[Deliverable] is ready — [link or attachment note].

Let me know if anything needs adjusting.

Liam

Gmail Draft Creation

After approval, call Zapier:gmail_create_draft with:

  • to: recipient email address
  • subject: generated subject line
  • body: email body (plain text)

Confirm with: "✅ Draft created in Gmail — ready to review and send."

Edge Cases

  • No email provided yet — Always ask before generating the draft
  • Unclear intent — Ask: "What's the main thing you want to communicate to [Name]?"
  • Attachment mentioned — Note: "I've added a placeholder — attach the file in Gmail before sending."
  • Multiple recipients — Comma-separate emails in the to field


2. Meeting Notes:

name: meeting-action-items description: | Extract action items from Fireflies.ai meeting transcripts. Use when the user provides a meeting name, keyword, or partial title and wants: (1) Action items with owners and deadlines, (2) Meeting summary, (3) Key decisions made, (4) Follow-up email draft. Triggers on phrases like "action items from [meeting]", "what came out of [call]", "tasks from [meeting name]", or just a meeting name/keyword.

Meeting Action Items Extractor

Extract action items from Fireflies transcripts and generate ready-to-send follow-up emails.

Workflow

  1. Find transcript — Search Fireflies for the most recent call matching the user's keyword
  2. Extract action items — Pull every task, commitment, or next step mentioned
  3. Assign owners — Use speaker names from transcript
  4. Set deadlines — Extract mentioned dates or flag as "TBD"
  5. Draft follow-up — Write email summarizing decisions and action items

Output Format

## 📞 Meeting Summary
**Call:** [Meeting title]
**Date:** [Call date]
**Participants:** [Speakers]
**Duration:** [Length]

---

## ✅ Action Items

| # | Task | Owner | Deadline | Priority |
|---|------|-------|----------|----------|
| 1 | [Specific task with context] | [Name] | [Date or "TBD"] | 🔴/🟡/🟢 |

---

## 🔑 Key Decisions Made
- [Decision 1]
- [Decision 2]

---

## ❓ Open Questions / Blockers
- [Unresolved items or dependencies]

---

## 📧 Follow-Up Email Draft

Subject: Action Items from [Meeting Name] — [Date]

Hey [team/name],

Quick recap from our call:

**Decisions:**
• [Key decision 1]
• [Key decision 2]

**Action items:**
• [Owner]: [Task] — by [deadline]
• [Owner]: [Task] — by [deadline]

Let me know if I missed anything.

[Sign-off]

Extraction Rules

Tasks — Look for: "I'll...", "Can you...", "We need to...", "Let's...", "Action item:", "Next step:", "Follow up on..." Include context (not just "send email" but "send email to vendor re: pricing")

Owners — Use speaker name from transcript. If unclear: "[Unassigned — clarify]"

Deadlines — Extract explicit dates ("by Friday", "next week"). Convert relative dates based on call date. No deadline = "TBD"

Priority

  • 🔴 High = Urgent, blocking, time-sensitive
  • 🟡 Medium = Standard task
  • 🟢 Low = Nice-to-have, mentioned casually

Email Tone

Direct, no fluff. Short sentences. Professional but casual. Clear hierarchy. End with "Let me know if I missed anything."

Edge Cases

  • No match: "I couldn't find a Fireflies transcript matching '[term]'. Try a different keyword or check if the call was recorded."
  • Multiple matches: "Found 3 calls matching '[term]'. Which one?" + list with dates
  • No action items: Return meeting summary + note no explicit action items identified, suggest reviewing transcript


3. Content Repurposing:

name: content-repurposing description: Transform source content (scripts, reels, carousels, articles) into platform-optimized versions for Threads, LinkedIn, X/Twitter, Instagram, TikTok, and YouTube Shorts. Use when the user wants to repurpose content across social platforms, adapt a script for multiple channels, or create platform-specific variations of existing content.

Content Repurposing Engine

Transform a single piece of source content into six platform-optimized versions while maintaining Liam Johnston's voice and style.

Voice & Style

Write like Liam — calm, direct, founder-to-founder:

  • Fast and tactical, no fluff
  • Conversational but confident
  • Short sentences, clean hierarchy
  • Use real numbers and specifics

Signature phrases (incorporate naturally):

  • "Here's the thing..."
  • "Here's what I started doing..."
  • "This literally takes five seconds..."
  • "You're leaving so much on the table..."
  • "Once you try this, you'll never go back..."
  • "And here's the part that blew my mind..."

Hook Structure (Six Power Words)

Build hooks with these elements:

  1. Subject Clarity — I, We, You, or the specific tool/system
  2. Action — what the subject did
  3. Objective/State Change — the shocking result
  4. Contrast — before vs. after expectation