Anthropic Just Dropped Claude for Small Businesses (31 Skills)
This video walks through Anthropic's 31-skill small business plugin inside Claude Co-work, demoing three skills (Business Pulse, Invoice Chase, Job Post Builder) and showing how connectors and Zapier MCP let Claude act across apps like QuickBooks, Stripe, Gmail, and HubSpot.
Brock Mesarich | AI for Non Techies18 minTranscript found
Quick learning frame
Read this before watching.
AI-native interfaces are control surfaces for intent, artifacts, context, preview, inspection, and iteration.
New playlist item from Brock Mesarich | AI for Non Techies; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: Installing and operating the Claude small business plugin in Co-work mode, and wiring app connectors (including Zapier MCP fallback) so skills can pull data and take actions across your real business tools.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Intent
02Canvas
03Artifact
04Preview
05Feedback
06Iteration
Deep lesson
Turn this video into working knowledge.
4,166 cleaned transcript words reviewed across 1,162 timed caption segments.
Thesis
Anthropic Just Dropped Claude for Small Businesses (31 Skills) teaches a practical interfaces + open design move: This video walks through Anthropic's 31-skill small business plugin inside Claude Co-work, demoing three skills (Business Pulse, Invoice Chase, Job Post Builder) and showing how connectors and Zapier MCP let Claude act across apps like QuickBooks, Stripe, Gmail, and HubSpot.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:36
Plugin as skill bundle
βinside of this small business plugin, we have 31 different skills across tons of different applications we could begin using inside of Claude Co-work and we could access all of them directly inside of the Claude desktop app.β
A plugin is simply a bundle of skills, where each skill is a named, described set of workflow instructions you trigger by keyword; the small business plugin packs 31 such skills spanning apps like Slack, Gmail, Stripe, and QuickBooks. In Claude desktop, switch from chat to Co-work via the checklist icon, open Customize, browse plugins, and install the small business plugin so its 31 skills appear under personal plugins.
5:17
Business Pulse pattern
βup that specific set of instructions, which is a very detailed prompt and will do that task for us. Here is just an example of a couple of different skills that we have directly inside of our system...β
The Business Pulse skill does a parallel pull from all connected apps at once, computes specified metrics, flags risks like overdue clients, and outputs a one-page TLDR with the day's number-one priority. Run the Business Pulse skill, then inspect its markdown file to see the connector list, steps, and output style, and note which connectors (e.g. Slack, HubSpot) still show as unconnected in the source status.
14:38
Connectors and Zapier fallback
βto be signed on docuign and even send them the email. And that is the power of this job post builder skill. All right. So, probably the overarching theme of this video is that Claude is incredibly powerful...β
Skills only become useful once you grant connectors access to your apps; when Claude has no native connector, a Zapier MCP server (zapier.com/mcp, select Claude Co-work) bridges to 8,000+ apps like Skool. Open Customize > Connectors, add the native connectors your business uses, then set up a Zapier MCP server for one app Claude lacks and confirm its tools appear in your connector list.
01
Intent
Start with this video's job: This video walks through Anthropic's 31-skill small business plugin inside Claude Co-work, demoing three skills (Business Pulse, Invoice Chase, Job Post Builder) and showing how connectors and Zapier MCP let Claude act across apps like QuickBooks, Stripe, Gmail, and HubSpot. Treat "Intent" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:36, where the video says: βinside of this small business plugin, we have 31 different skills across tons of different applications we could begin using inside of Claude Co-work and we could access all of them directly inside of the Claude desktop app.β
02
Canvas
Use "Canvas" to locate the part of the interfaces + open design workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 5:17, where the video says: βup that specific set of instructions, which is a very detailed prompt and will do that task for us. Here is just an example of a couple of different skills that we have directly inside of our system...β
03
Artifact
Turn "Artifact" into the reusable artifact for this lesson: A UI critique sheet for judging whether an AI interface improves control. This is where watching becomes something you can inspect and reuse.
04
Preview
Use "Preview" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Feedback
Use "Feedback" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Iteration
Use "Iteration" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a ui critique sheet for judging whether an ai interface improves control..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video walks through Anthropic's 31-skill small business plugin inside Claude Co-work, demoing three skills (Business Pulse, Invoice Chase, Job Post Builder) and showing how connectors and Zapier MCP let Claude act across apps like QuickBooks, Stripe, Gmail, and HubSpot.
02
Explain the practical stakes without hype: New playlist item from Brock Mesarich | AI for Non Techies; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A UI critique sheet for judging whether an AI interface improves control.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: Anthropic Just Dropped Claude for Small Businesses (31 Skills)
- URL: https://www.youtube.com/watch?v=zzo33HUOfxI
- Topic: Interfaces + Open Design
- My current learning frame: Install the small business plugin, connect at least QuickBooks/Stripe and Gmail, then run Business Pulse and Invoice Chase to produce a real daily pulse and a tone-matched overdue-invoice draft for your own accounts.
- Why this matters: New playlist item from Brock Mesarich | AI for Non Techies; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:36 / Evidence 1: "inside of this small business plugin, we have 31 different skills across tons of different applications we could begin using inside of Claude Co-work and we could access all of them directly inside of the Claude desktop app."
- 3:03 / Evidence 2: "different applications and companies that are, you know, bigger are partnering with Claude in order to give you certain skills to perform different actions across those different apps. If you've never used plugins before, they are super helpful."
- 5:17 / Evidence 3: "up that specific set of instructions, which is a very detailed prompt and will do that task for us. Here is just an example of a couple of different skills that we have directly inside of our system..."
- 9:15 / Evidence 4: "Claude co-work operating system template that I use every single day to help me run my business. breaks down my different goals. It shows all my different emails across my inboxes and even shows basically all the different..."
- 11:57 / Evidence 5: "little bit of our business context. And then from there, it's going to create a brief for us. It's going to draft the job post. It's going to build the interview guide and rubric for our team to..."
- 14:38 / Evidence 6: "to be signed on docuign and even send them the email. And that is the power of this job post builder skill. All right. So, probably the overarching theme of this video is that Claude is incredibly powerful..."
- 16:31 / Evidence 7: "natively integrate with. Next, what you could do is just click on new MCP server. and you're going to select Claude Co-work. And you can see I personally have a couple of these different tools configured. Some of..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A UI critique sheet for judging whether an AI interface improves control.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "Anthropic Just Dropped Claude for Small Businesses (31 Skills)", not a generic Interfaces + Open Design essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
A beautiful page is automatically a good learning tool.
Learning requires sequence, active recall, feedback, and application.
Generated UI should be accepted as-is.
Generated UI needs critique, revision, and browser verification.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a ui critique sheet for judging whether an ai interface improves control..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal β without rewatching.
In this video's terms, what exactly is a 'plugin' versus a 'skill', and what does a skill consist of?
What does the Business Pulse skill do mechanically, and what does it produce as its final output?
Skills only work once apps are connected. What does the video say to do when Claude has no native connector for an app, and roughly how many apps does that path reach?
Source shelf
Use the video as a doorway, then verify with primary sources.