Claude Code Business Skills Library

What It Does

Automatically respond to incoming sales inquiries with qualified, professional responses that move prospects through your sales pipeline.

The workflow:

1. Reads the incoming sales email (from Gmail, forwarded text, or screenshot)
2. Analyzes the inquiry for prospect intent and qualification
3. Pulls context from your business memory (Obsidian)
4. Matches relevant case studies from your portfolio
5. Drafts a personalized response in your tone
6. Suggests next steps and qualification notes

Requirements

• Obsidian MCP (required) - To read Sales.md and Business Profile.md
• Gmail MCP (optional) - For direct email reading

How to Use

Method 1: From Gmail (if Gmail MCP connected)

/sales-email from:prospect@company.com subject:"interested in automation"

Method 2: Paste Email Content

/sales-email

[Paste the email here]

From: John Doe <john@company.com>
Subject: Question about AI agents

Hi, I saw your post about invoice automation...

Method 3: From Screenshot

/sales-email

Then attach a screenshot of the email.

You are a sales response assistant for [Your Company Name].

**Your task:** Draft a professional, conversational response to the incoming
sales email that qualifies the prospect and moves them toward a discovery call.

### Steps:
1. **Read context** from your knowledge base:
   - Sales process document for tone, ICP, and process
   - Business profile document for relevant solutions and metrics

2. **Analyze the email:**
   - What is the prospect asking about?
   - Do they fit the ICP (10+ employees, automation needs)?
   - What pain point are they expressing?
   - What's their level of intent (high/medium/low)?

3. **Match to portfolio:**
   - Which solution(s) from your product/service catalog are most relevant?
   - What metrics/results would resonate?

4. **Draft response:**
   - Open with acknowledgment of their specific question
   - Share 1-2 relevant case studies with concrete numbers
   - Address their pain point directly
   - Suggest next step (usually: brief call to understand their needs)
   - Keep it short (150-200 words max)
   - Use direct, conversational tone (no corporate fluff)
   - End with clear CTA

5. **Qualify quietly:**
   - If under-qualified, be helpful but suggest resources instead of a call
   - If well-qualified, push for meeting

### Tone Guidelines:
- Direct and practical
- Conversational (like talking to a colleague)
- Confident but not pushy
- Focus on outcomes, not features
- Use "I" not "we" when appropriate

Tips

• Always personalize - Reference something specific from their email
• Lead with value - Start with a relevant result, not a pitch
• Keep it short - Respect their time
• Clear CTA - Make the next step obvious
• Internal notes - Track qualification for CRM later

What It Does

Conduct deep research on potential clients using web search and scraping. Discover company info, decision makers, pain points, and automation opportunities.

The workflow:

1. Searches the web for company information
2. Analyzes company website, LinkedIn, news, and social media
3. Identifies decision makers and their contact info
4. Discovers pain points and automation opportunities
5. Generates a research report with actionable insights
6. Suggests outreach angles and talking points

Requirements

• WebSearch (built into Claude Code) - For web searches
• WebFetch (built into Claude Code) - For reading web pages
• No external MCP servers required!

How to Use

/prospect-research Acme Corp

/prospect-research https://www.acmecorp.com

/prospect-research TechCo - focus on finance automation opportunities

Where to Look for Research

What It Does

Generate custom sales proposals from discovery call notes. Automatically matches relevant case studies, calculates ROI, and creates a professional proposal in minutes.

The workflow:

1. Reads your discovery call notes (from Obsidian, text file, or pasted)
2. Pulls relevant case studies from your Business Profile
3. Calculates ROI and time savings based on similar projects
4. Structures a professional proposal with your format
5. Outputs ready-to-send proposal (Markdown → Word/PDF)

How to Use

/create-proposal Client: Acme Corp

Or paste notes directly:

/create-proposal

Discovery Call - Acme Corp
- 50 employees
- Processing 200 invoices/month manually
- Uses Xero
- 15h/week spent on AP
- Budget: $30k

Pricing Guidelines

ROI Calculation Formulas

Time Savings ROI:
Current hours/week × hourly labor cost × 52 weeks = Annual labor cost
Annual labor cost - Solution cost = Net savings Year 1
Solution cost ÷ Net savings per year = Payback period (months)

Efficiency ROI:
Current cost per unit / New cost per unit = Efficiency gain
Efficiency gain × Annual volume = Total savings

What It Does

Automatically generate weekly reports by pulling data from Trello, Google Calendar, and Gmail. Creates structured overview of your accomplishments, meetings, and activities.

The workflow:

1. Pulls data from your connected tools (Trello, Calendar, Gmail)
2. Analyzes your week for patterns and highlights
3. Generates structured report with metrics and accomplishments
4. Formats for your use case (standup, team update, personal review)

Requirements

• Trello MCP (required) - To read cards and activity
• Google Calendar MCP (required) - To read meetings
• Gmail MCP (optional) - To read email activity
• Obsidian MCP (optional) - To save reports to your vault

How to Use

/weekly-report

/weekly-report from:2026-02-24 to:2026-03-02

/weekly-report --format standup

Report Formats

Tips for Better Reports

• Use consistent Trello labels (e.g., "High Priority", "Client Work")
• Complete calendar entries (add attendees and descriptions)
• Archive completed cards regularly
• Run weekly at same time (e.g., Friday 4pm)

What It Does

Transform one blog article into 10+ social media posts, email content, and threads. Maintains your brand voice while optimizing for each platform.

The workflow:

1. Reads your source content (blog article, video transcript, podcast notes)
2. Extracts key insights, quotes, and takeaways
3. Analyzes your tone of voice from existing content
4. Generates platform-specific content (5-7 LinkedIn posts, 3-5 Twitter threads, 2-3 Email sections)
5. Formats each piece for maximum engagement

How to Use

/content-repurpose https://yourblog.com/your-article

/content-repurpose note:"Content/Blog Articles/Invoice Automation ROI"

/content-repurpose [source] --platforms linkedin,twitter

LinkedIn Post Structure

1. Hook (first line, grabs attention)
2. Body (2-4 short paragraphs, one line each)
3. Takeaway (key insight or action)
4. CTA (question or engagement prompt)

Content Angles to Cover

• Main thesis post (introduce the concept)
• Data/metrics post (share impressive numbers)
• Story/case study post (real example)
• Framework/how-to post (actionable steps)
• Controversial take post (challenge assumptions)
• Behind-the-scenes post (process/learnings)
• Question/poll post (engage audience)

What It Does

Automatically research meeting attendees, pull context from past interactions, and generate talking points — so you walk into every meeting prepared.

The workflow:

1. Reads your upcoming calendar events (Google Calendar)
2. Identifies attendees and their companies
3. Researches each person via web search and LinkedIn
4. Checks history — past emails, Trello cards, or notes about them
5. Generates a prep brief with talking points, context, and goals

Requirements

• Google Calendar MCP (required) — To read meeting details and attendees
• WebSearch (built-in) — To research attendees and companies
• Gmail MCP (optional) — To check past email threads
• Trello MCP (optional) — To find related tasks or projects
• Obsidian MCP (optional) — To check your notes about the person/company

How to Use

/meeting-prep

Prepares for your next upcoming meeting.

/meeting-prep tomorrow

Prepares for all meetings tomorrow.

/meeting-prep "Discovery Call with TechFlow"

Prepares for a specific meeting by title.

You are a meeting preparation assistant.

**Your task:** Research the attendees and context for an upcoming meeting,
then generate a concise prep brief.

### Steps:
1. **Read calendar** — Find the meeting from Google Calendar.
   Get: title, time, attendees (names + emails), description.

2. **Research attendees:**
   - Search their name + company on the web
   - Find their LinkedIn profile, role, recent posts
   - Check for any past emails with them (Gmail)
   - Check for any related Trello cards or Obsidian notes

3. **Build context:**
   - What does their company do?
   - What's their role and likely priorities?
   - Any past interactions or open deals?
   - What's the likely purpose of this meeting?

4. **Generate prep brief:**
   - Meeting: [title, time, duration]
   - Attendees: [name, role, company — 1 line each]
   - Context: [what you know about them]
   - Talking Points: [3-5 suggested topics]
   - Questions to Ask: [2-3 smart questions]
   - Goal: [what outcome to aim for]

Keep it concise. One page max. Focus on what's actionable.

Example Output

MEETING: Discovery Call — DataFlow Inc
TIME: Tuesday 10:00 AM (30 min)

ATTENDEES:
• Sarah Martinez — VP Operations, DataFlow Inc
  - 8 years at DataFlow, promoted from Ops Manager in 2024
  - Posted about "scaling challenges" on LinkedIn last week
  - No prior emails or interactions found

COMPANY:
• B2B SaaS, 50 employees, Series A ($8M in 2025)
• Hiring Finance Ops Manager (indeed.com — posted 2 weeks ago)
• Tech stack: Xero, HubSpot, Slack, Notion

CONTEXT:
• Likely pain: manual finance processes (hence the hire)
• Our relevant solution: Invoice Processor Agent
• Similar win: TechFlow Solutions — saved 12+ hrs/week

TALKING POINTS:
1. Ask about the Finance Ops Manager role — what's driving it?
2. Explore invoice volume and current manual processes
3. Share TechFlow case study (similar size, Xero, 129% ROI)

QUESTIONS TO ASK:
• "What made you start looking at this now?"
• "How many invoices are you processing per month?"
• "What does the approval workflow look like today?"

GOAL: Qualify for proposal. If 100+ invoices/month → schedule
technical deep-dive next week.

What It Does

Check overdue invoices and draft professional follow-up emails. Gets the tone right — firm enough to get paid, friendly enough to keep the relationship.

The workflow:

1. Reads your outstanding invoices (from Obsidian notes, pasted list, or accounting data)
2. Identifies which are overdue and by how long
3. Checks context — past emails, relationship history, payment patterns
4. Drafts follow-up emails with escalating tone based on how overdue
5. Suggests next steps if payment doesn't come

Requirements

• Obsidian MCP (optional) — To read invoice records and client notes
• Gmail MCP (optional) — To check past payment correspondence
• Works with pasted invoice data too — no MCP required

How to Use

/invoice-followup

Paste your overdue invoice list and it drafts follow-ups for each.

/invoice-followup

Overdue invoices:
- INV-2024-087: TechFlow Solutions, $18,500, due March 15 (14 days overdue)
- INV-2024-091: DataCorp, $5,200, due March 22 (7 days overdue)
- INV-2024-095: StartupXYZ, $3,800, due March 28 (1 day overdue)

You are an invoice follow-up assistant.

**Your task:** Review overdue invoices and draft professional follow-up
emails with the right tone for each situation.

### Steps:
1. **Review invoices** — Read the overdue invoice data provided.
   Note: amount, client, days overdue, any past follow-ups.

2. **Determine tone** based on how overdue:
   - 1-7 days: Friendly reminder. "Just checking in" tone.
   - 8-14 days: Professional nudge. Direct but warm.
   - 15-30 days: Firm follow-up. Clear expectation of payment.
   - 30+ days: Escalation. Mention payment terms, next steps.

3. **Check context** (if available):
   - Past emails about this invoice
   - Client relationship and payment history
   - Any known issues or disputes

4. **Draft email for each invoice:**
   - Subject line that's clear but not aggressive
   - Reference invoice number and amount
   - Acknowledge the relationship positively
   - State the request clearly
   - Make payment easy (include payment details if available)
   - End with clear next step and timeline

5. **Suggest next actions** if no response:
   - Second follow-up timing
   - Phone call suggestion
   - Payment plan option for large amounts
   - When to involve legal/collections

### Tone Guidelines:
- Professional, never passive-aggressive
- Assume good intent (they forgot, it's in a queue)
- Be specific about amounts and dates
- Make the ask clear and easy to act on

Example Output

Subject: Invoice INV-2024-087 — Quick follow-up

Hi Sarah,

Hope you're doing well. I wanted to follow up on invoice INV-2024-087
for $18,500, which was due on March 15.

I understand things can get busy — just want to make sure this didn't
slip through the cracks on your end.

If there are any questions about the invoice or if you need me to
resend it, happy to help. Payment can be made via bank transfer
to the details on the invoice.

Could you let me know the expected payment date?

Thanks,
[Your Name]

---
Internal Notes:
- Days overdue: 14
- Tone: Professional nudge
- Next step: If no response by Friday → phone call
- Escalation: If 30+ days → formal payment reminder letter

What It Does

Run a quick competitive analysis using web research. Get pricing, positioning, strengths, weaknesses, and opportunities — in minutes instead of hours.

The workflow:

1. Takes a competitor name, URL, or industry as input
2. Researches their website, pricing, features, and positioning
3. Analyzes reviews, social presence, job postings, and news
4. Compares against your business profile (from Obsidian)
5. Generates a competitive brief with actionable insights

Requirements

• WebSearch (built-in) — For web research
• WebFetch (built-in) — For reading competitor websites
• Obsidian MCP (optional) — To compare against your own positioning
• No external MCP servers required

How to Use

/competitor-scan https://www.competitor.com

/competitor-scan "AI automation agencies in Netherlands"

/competitor-scan CompetitorName — focus on pricing and positioning

You are a competitive intelligence analyst.

**Your task:** Research a competitor or competitive landscape and
generate an actionable competitive brief.

### Steps:
1. **Research the competitor:**
   - Visit their website (about, pricing, services pages)
   - Search for recent news, funding, partnerships
   - Check their LinkedIn company page and employee count
   - Look at job postings (reveals priorities and pain points)
   - Find reviews on G2, Capterra, Trustpilot if applicable

2. **Analyze their positioning:**
   - What's their tagline/value proposition?
   - Who are they targeting? (company size, industry)
   - What's their pricing model? (if public)
   - What technology/approach do they use?
   - What do customers say? (reviews, testimonials)

3. **Identify strengths and weaknesses:**
   - Where are they strong? (features, brand, market share)
   - Where are they weak? (missing features, complaints, gaps)
   - What are they investing in? (job postings, recent launches)

4. **Compare to your business** (read Business Profile from Obsidian):
   - Where do you win against this competitor?
   - Where do they have an advantage?
   - What's your differentiation?

5. **Generate competitive brief:**
   - Company overview (1 paragraph)
   - Positioning & target market
   - Pricing (if found)
   - Strengths (3-5 bullet points)
   - Weaknesses / gaps (3-5 bullet points)
   - Your competitive advantage
   - Recommended talking points when selling against them

Example Output

COMPETITOR: AutomateIQ
WEBSITE: automateiq.com

OVERVIEW:
AI automation agency, 25 employees, based in London. Focus on
enterprise clients. Founded 2023, seed-funded ($2M).

POSITIONING:
"Enterprise AI automation for Fortune 500"
Target: Large enterprises (500+ employees)
Approach: Custom-built solutions, long implementation cycles

PRICING:
Not public. Job postings suggest $100k+ projects.
Enterprise sales cycle (3-6 months).

STRENGTHS:
• Strong enterprise credibility (3 Fortune 500 case studies)
• Deep technical team (hiring ML engineers)
• SOC 2 compliant
• Strong LinkedIn presence (CEO has 15k followers)

WEAKNESSES:
• No SMB offering — too expensive for smaller companies
• Long implementation (8-12 weeks minimum)
• No self-serve or productized offerings
• 2 negative Glassdoor reviews mention "over-promising"

YOUR ADVANTAGE:
• You serve 10-50 employee companies (they don't)
• Faster implementation (2-4 weeks vs 8-12)
• More affordable ($5k-30k vs $100k+)
• Practical, outcome-focused vs. enterprise complexity

TALKING POINTS (when prospect mentions them):
• "They're great for enterprise. We built our approach for
  companies that need results in weeks, not quarters."
• "Our solutions start at $5k. You get the same AI capabilities
  without the enterprise overhead."