Video summary

How I Turned Claude Into My Personal Assistant (Beginner Guide)

Main summary

Key takeaways

Technology

Summary (technological concepts, features, and tutorial takeaways)

Core thesis / productivity angle

  • The speaker argues AI won’t replace everyone—jobs will shift toward people who use AI in practical, automated ways.
  • Many users “chat” with Claude but fail to set up persistent automation because they lose context/memory when they close the app.

Target outcome

  • Turn Claude Desktop + Claude Code into a personal assistant that can actually do work, such as:
    • Email
    • Calendar
    • Task tracking
    • Outbound campaigns

Beginner guide: “Claude as a personal assistant” setup (claimed ~10 minutes)

1) Install and start from the right environment

  • Use the Claude desktop app (install from the first search result).
  • Instead of starting in regular chat, launch directly into Claude Code for automation workflows.

2) Connect existing tools via “connectors” (MCP)

  • In Claude desktop app: Settings → Connectors → Add → pre-built connectors
  • The tutorial describes connectors as MCPs (you don’t need to remember the term).
  • Example pre-built connections:
    • Gmail (via Google account connection)
    • Google Calendar
    • ClickUp (project/task tracking)
  • Recommendation: connect all daily tools to automate more tasks.

3) Restart Claude to load connectors

  • After installing connectors, do a quick restart.

4) Run automation locally with Claude Code using a project folder

  • Create desktop folders:
    • “Claude projects”
    • inside it: “personal assistant”
  • In Claude Code, run the assistant locally and point it to the created folder.

What the assistant can do (with connected Gmail/Calendar/etc.)

  • Calendar lookup: ask Claude, e.g., “What appointments do I have today?”
  • Email review: ask Claude to check Gmail for emails received today.
  • Email drafting and sending (via Gmail connector):
    • Prompt to draft an email to a partner
    • Workflow includes: generate draft → user review → send
  • Planned automation: a “morning” workflow to respond to emails repeatedly (implemented later via skills).

Extending beyond built-in connectors: custom MCP connectors

  • If a tool isn’t available in the pre-built list, use custom connectors.
  • Example shown: Higgsfield.ai
    • Get the remote MCP server URL
    • In Claude: Add custom connector
    • Configure the URL
  • Option: set “always allow” to avoid repeated approvals (with implied caution).

“Skills” as the mechanism for reliable automation (repeatable behavior)

  • The guide claims the main beginner mistake is giving too-broad instructions in chat.
  • Skills are introduced to enforce structured, repeatable actions.
  • Key idea:
    • Skills help Claude run the same procedure every time (less variance than free-form prompts)
    • Skills can be updated/iterated if outcomes aren’t desired

Installing prebuilt Claude Skills (with security audit)

  • Download a folder of “Claude skills” from a shared source (Google Drive in the tutorial).
  • Installation method:
    1. Download ZIP
    2. Drag the skills folder into Claude Code
    3. Restart Claude completely (not just close/reopen)
  • Security guidance:
    • When installing skills from the internet, check for prompt injection / malicious code
    • Claude is shown performing an audit and reporting: “clean, no malicious code or prompt injection found.”
  • Recommendation: use project-specific skills rather than global installation.

Example skill behavior: “morning brief”

  • The tutorial builds a skill called /morning brief that generates an HTML file each morning containing:
    1. Email triage + draft replies for emails requiring human response (from the past couple of days)
    2. Calendar check for upcoming events today
    3. ClickUp board items for what to work on today
  • The tutorial also demonstrates updating behavior:
    • If the assistant makes an undesirable choice (e.g., accepting a cold email), you can update the skill so it automatically declines similar cold-email offers in the future.

Advanced integrations and automation examples

Call coaching using call transcript data (Fathom)

  • Connect Fathom via a connector.
  • Claude can retrieve and summarize meeting/transcript content.
  • Use cases:
    • Summarize what the last sales call was about
    • Provide sales/consulting coaching: what went well, what to improve, and suggested follow-ups

Cold email campaign automation using “Instantly” + MCP

  • Connect Instantly via custom MCP:
    • Create an API key in Instantly
    • Paste the MCP URL (with the API key) into Claude’s custom connector configuration
  • Example command: /Instantly campaign
  • Claude can generate an end-to-end cold email campaign sequence:
    • Create campaign
    • Generate copy
    • Present campaign sequences for review
    • “Yes” to add into the campaign

Claimed pattern: skills as a reusable automation template

  • General rule from the tutorial:
    • Take a tool-specific skill (e.g., cold email, morning brief)
    • Claude can orchestrate it with connected services to automate larger workflows

Main speakers / sources

Main speaker

  • Albert (also referenced as the creator of “No Banned Technical,” presenting the tutorial and his community)

Tools / sources mentioned

  • Claude
    • Claude Desktop
    • Claude Code
    • Skills
  • MCP connectors
  • Gmail / Google Calendar / ClickUp
  • Glider (dictation tool mentioned for faster voice input)
  • Higgsfield.ai (example for custom MCP connector)
  • Fathom (call transcript integration)
  • Instantly.ai (cold email campaign integration)
  • “Claude skills” downloaded from the tutorial’s shared link/community (creator’s skill pack)

Original video