What You’ll Learn James has written thousands of Claude skills over the last two years. He isn’t going to write another one. In this session he explains why, and what he does instead: a five-part briefing that tells an AI employee what you want done, not how to do it. If you have been collecting…
James breaks down the “four brains” every educator has — and why the popular second brain can’t earn you money. He shows how he built a public-facing third brain on WordPress and Pinecone, plus three ways to monetize it.
Tired of hitting Claude usage limits, James cut his AI bill with two parts: an AI HR Department that inventories every skill he runs, and a router that sends no-thinking tasks to a free Qwen model on an old Mac Mini via Ollama.
In a live session, James explains why he stopped using standalone tools and runs his whole business through one Campus AI Operating System — 23 AI employees, four departments, and a single orchestrator named Dean — and how the same setup ports to any industry.
James gives five reasons he avoids “personal AI” for his business and uses a campus operating system instead. The core distinction: personal AI does tasks, while a campus OS runs coordinated workflows across departments of AI employees — with memory, drafts, and accountability.
James explains why he skipped Hermes and OpenClaw — powerful but technical agent frameworks — and built a no-code alternative: a campus operating system that installs as a single Claude plugin. It borrows their best ideas (a second-brain wiki, a self-learning loop, a strategy layer, and reporting) with no Docker or command line.
In a live AMA, James urges educators to stop chasing the best AI tool and instead build an operating system they can talk to. It’s tool-agnostic (just files on your hard drive, readable by Claude, Codex, or Gemini), and the real skill is shifting from task prompts to strategic business conversations.
From a live open Q&A, James lays out the starter path for Claude Cowork: install the desktop app on a paid plan, wrap up every session so your memory and wiki stay current, wire multiple orchestrators together, and build the one habit that matters most — asking for outcomes instead of tasks.
If you’re a coach, consultant, or teacher over 45, your years of recordings, courses, and hard-won process are a goldmine you’re probably sitting on. In this live workshop James shows how to mine it: repurpose old assets with a Content Flywheel, build an AI operating system you talk to like a chief of staff, turn your know-how into sellable playbooks, and run a no-ick lead-gen pipeline — so you can just teach and let agents do the rest.
James has 160+ Claude skills, a pile of plugins, and no idea what half of them do. In this walkthrough he installs an AI HR Department — a plugin that builds one honest roster of every AI employee, team, playbook, and scheduled task you own, flags the stale ones each week, and turns your messy AI pile into a team you can actually manage.
What You’ll Learn If you ran a one-person business and could hire as many employees as you wanted, how would you set it up? That’s the question James uses to reframe what an “AI agent” actually is. Forget the technical definition. In this session you’ll learn to see an agent as an employee with one…
What You’ll Learn James has a library of 53 prompting frameworks on his campus — “prompting like a boss,” sales copy prompts, YouTube prompts, the works. All valuable, if prompting still mattered. In this session he argues it mostly doesn’t anymore, and shows what replaces it: conversation. You’ll learn the difference between a transaction and…