Foundations · The Building Blocks
Claude Projects, Skills & Agents — Explained for Dealers
Three words that sound like jargon and are actually the whole game. Here's each one in dealership terms.
Projects: the office you set up once
A Claude Project is a workspace with memory. You load it once with your store's knowledge — brand voice, store facts, compliance rules, templates — and every conversation inside that Project starts already briefed.
Dealership translation: it's the difference between a new vendor who asks the same questions every visit and a longtime partner who already knows your store. Set up one Project per function to start: Marketing, BDC, Ops. Feed each with the right markdown knowledge files.
Skills: your expertise, packaged into a button
A Skill is a packaged set of instructions Claude loads on demand to do one job your way. Where a Project holds general knowledge, a Skill holds a procedure: how your store writes a vehicle description, how you structure a competitive brief, how a review response must be handled.
Dealership translation: a Skill is an SOP that executes itself. Your best copywriter's method, your GM's deal-review checklist, your compliance officer's rules — written once, run by anyone, output consistent every time. This is how expertise stops living in one person's head.
When to build one: any task you (or your team) do more than weekly, where quality varies by who does it. That variance is exactly what a Skill removes.
Agents: digital employees with a job description
An agent is Claude given a role, instructions, tools, and a deliverable — then set loose to execute multi-step work. Not a chat you babysit; a worker you brief and check.
Dealership translation: you already know how to do this — it's hiring. You write the job description (role + instructions), hand over the tools and training (Project knowledge + Skills), define the deliverable, and inspect the work. At the Intensive, attendees build a four-role team in two hours: Sales Ops, BDC/CRM, SEO, and a Competitive Analyst — each with a job, a voice, and a deliverable that passes the Monday-morning test. Full walkthrough: Build AI Agents for Your Dealership.
How they stack
| Layer | What it holds | Dealership equivalent |
|---|---|---|
| Project | Knowledge & context | The employee handbook + store facts |
| Skill | Procedures | SOPs that execute themselves |
| Agent | Role + deliverable | A digital employee |
| Workflow | Chained agents & skills | A department that runs end to end |
Most dealers stop at prompting and wonder why AI feels like a toy. The stack is what turns it into infrastructure: Project → Skills → Agents → Workflow. Each layer compounds the one below it.
Build order that works: knowledge files first (a weekend), one Skill for your most repeated task (a week), one agent with a weekly deliverable (a month) — or all of it in two days at the workshop.
Build the Whole Stack in Two Days
Projects, Skills, a four-agent team, and a working workflow — live in your own account.
Save My Seat — $500 Off by Aug 1 →