More in Cowork + Power Stack
The Power Stack Tour
A guided tour of what Claude can be wired up to do. Six concepts, one 60-second exercise each.
What we cover
- Skills -- what a /command is, why naming a workflow makes it reusable
- Agents -- when Claude makes its own next-step decisions
- Plugins -- pre-built bundles you can install
- MCP Connectors -- how Claude reads + writes Slack, HubSpot, OneNote, DealCloud
- Scheduled Tasks -- Claude that runs on a clock
- CLAUDE.md & Memory -- the file you set up once that shapes every conversation after
Why it matters
This is the shape of the road -- the six things that turn Claude from a chat box into a firm capability. You don't need to drive every car. You do need to know the shape so you can spot when one of them solves your problem.
Hands-on moment
Each sub-section has its own 60-second copy-paste exercise. Mike narrates; the room runs them on their laptops. By the end, every learner has touched all six concepts at least once.
Tour stops
- 01
Skills (the /command system)
A skill is a workflow you've named so you can run it again. Inside Cowork it shows up as a /command -- type a slash, pick the skill, fill in the blanks. The act of naming is what turns one good output into a repeatable capability.
Try this RIGHT NOW (60 sec)
Open Cowork. Type "/" and look at the dropdown. Pick any skill, run it on a small task you'd otherwise hand-write. 60 seconds.
- 02
Agents
An agent makes its own decisions about which step to take next. Where a skill is one defined workflow, an agent decides whether to call one skill, then another, then maybe a third, based on what it sees. The Meeting Prep Agent (we'll see it in M6) is the worked example.
Try this RIGHT NOW (60 sec)
In Cowork, ask Claude: "Look at my next meeting and tell me three things I should know before I walk in." Notice how it decides what to fetch.
- 03
Plugins
A plugin is a pre-built bundle of skills + commands + connectors -- one install, lots of capability. Mike's /ggp-sourcing-brief plugin is the kind of thing GGP could ship to the firm so every analyst has the same intake on their laptop.
Try this RIGHT NOW (60 sec)
Look at the plugins panel in Cowork. Spot one you'd install for your role. Don't install it now -- just notice what's available.
- 04
MCP Connectors
MCP is the protocol that lets Claude reach into other tools -- read your Slack, write to HubSpot, pull a file from OneNote, query DealCloud. Pre-built connectors exist for the tools you use today; custom builds are Phase 2 territory.
Try this RIGHT NOW (60 sec)
Pick the tool you'd most want Claude to read. Write one sentence: "If Claude could see my [tool], the first skill I'd build is...". Save the sentence -- it's a Phase 2 candidate.
- 05
Scheduled Tasks
Claude that runs on a clock. Daily news pull at 7am. Weekly portco summary every Monday. Compliance gates apply -- whatever can't go to Claude live, can't go on a schedule either.
Try this RIGHT NOW (60 sec)
Imagine a task you do every Monday morning at the same time. Could a scheduled Claude do the first 70%? Write yes or no in one line, and the reason why.
- 06
CLAUDE.md & Memory
The file Claude reads at the start of every conversation. Put your firm's rules, your conventions, your no-go list in here once -- and Claude knows them every time. The memory/ folder is where skills that learn from past runs keep what they've learned.
Try this RIGHT NOW (60 sec)
Write one rule you wish Claude knew about your work, every time, without you saying it. That's a CLAUDE.md candidate. The next topic page goes deep on this.
Related artifacts
- deckM4 Deck (Power Stack section)../../course-content/module-4-cowork/m4-cowork-master.pptx
- pre-readM4 Pre-read../../course-content/module-4-cowork/pre-read.md
Source files live alongside this site under clients/greenridge-growth/; paths above are relative to the syllabus-site root.