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.
A Project is a Claude workspace loaded once with your store's knowledge so every conversation starts briefed. A Skill is a packaged procedure Claude runs the same way every time, an SOP that executes itself. An agent is Claude given a role, instructions, tools, and a deliverable: a digital employee you brief and inspect. They stack: Project, then Skills, then agents, then workflows that chain them together.
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 agents with real jobs: 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.
Common questions
What is a Claude Project?
A workspace with memory. Load it once with your brand voice, store facts, compliance rules, and templates, and every conversation inside it starts already knowing your store. Start with one per function: Marketing, BDC, Ops.
What is a Claude Skill, in dealership terms?
An SOP that executes itself. Where a Project holds general knowledge, a Skill holds a procedure, such as how your store writes a vehicle description or handles a review response, written once and run by anyone with consistent output.
What is an AI agent?
Claude given a role, instructions, tools, and a defined deliverable, then trusted to execute multi-step work. It is hiring: you write the job description, hand over the training, define the deliverable, and inspect the work.
What order should a dealership build these in?
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 Claude for Dealers workshop.
Build the Whole Stack in Two Days
Projects, Skills, agents, and a working workflow — live in your own account.
Register Now →