It's not a skill issue. It's a skill.md issue.
An AI workshop for the team. Four demos. One idea: stop prompting harder, start shipping skills.
~ 20-25 min, four live runs
Claude is the team we never hired.
Four demos. Each one unlocks a different workflow you can reuse tomorrow.
Why these four?
Pick one today and you're already faster.
Four demos. Four primitives.
Each demo is a live run. Watch the workflow, steal the pattern, repeat.
CSV to XLSX in Claude Cowork
Messy files to clean workbook in one prompt.
Creating a Skill
Ship once, run forever.
Claude Inside Excel
Prompt in-app. No copy/paste.
Fireflies + Claude
Every call, searchable.
CSV → XLSX, done in one prompt.
A skill is just SOP plus script.
SKILL.md is the brain. The script does the work. Claude orchestrates.
--- name: generic-email-finder description: Find info@ / contact@ / sales@ emails for a list of domains using Serper + LLM. --- # When to use Run this after Apollo enrichment when any row still has a blank email column. # Command python3 .claude/skills/generic-email-finder/\ find_emails.py --input leads.csv \ --output leads_enriched.csv
Claude Inside Excel.
Install the Claude add-in. Open the workbook. Claude is right there in the sidebar, reading the sheet with you.
- → Claude runs inside Excel as an add-in
- → Same workbook from Demo 1, edited in place
- → No exporting, no copy/paste, no context switching
"Create a new tab with just the generic emails — no rows that have a first name."
Fireflies + Claude.
• CONCEPT · NOT DEMOED TODAYWhat you could build next.
Connect Fireflies to Claude
One-time setup via connector.
Ask natural questions
"What did we discuss with <email>?"
Pulls across months
Meetings, transcripts, decisions.
Use cases
Prospect prep, pre-call context, recall.
Four moves to steal tomorrow.
Feed Claude the files.
Raw CSVs in, workbook out.
3rd repeat? Ship a skill.
SKILL.md plus a script.
Work where the file lives.
Claude add-in, inside Excel.
Ask your calls questions.
Always-on meeting memory.
Everyone gets Claude. Starts soon.
Right now the team doesn't have access. That changes: we'll begin rolling out seats across the team so everyone can do this work themselves.
Combining files, every week.
GMB scrape, decision makers, Clay output, XLOOKUP merges. The Demo 1 pipeline runs once a week. Claude does it in minutes.
SmartLead data gymnastics.
Pull SmartLead export, merge with contacts, push into the company file, rename outreach → outreach initiated, dedupe, relabel. Every day.
Repeat transforms by hand.
If you're doing the same column renaming, filtering, or file merging more than once, Claude can take it off your plate.
Treat Claude like a new teammate.
Tell Claude what you want the way you'd brief a person. If you hit a wall, bring the problem to me and I'll build a skill for it.
- 1Open Claude Cowork. Point it at your folder.
- 2Describe the job in plain English. All the changes, exactly how you'd brief a human.
- 3Let it run. A couple of minutes, not a couple of hours.
- 4Happy with the result? Ask Claude to save it as a skill.
- 5Run the skill next time in one line, instead of re-prompting.
Monthly team session.
Bring your file-wrangling problems. We'll solve them live and ship skills.
Or flag it sooner.
Hit a snag? Send me the problem any time. I'll build a skill and share it back, no need to wait for the monthly.
Share skills across the team.
Skill files are portable. Someone builds it once, anyone can drop it into their system.
No one starts from scratch.
Your teammate's skill is your shortcut. Reuse, don't rebuild.
Once you're comfortable, stack it.
Three moves that compound as you get more reps in.
One skill feeds the next.
Skill 1 cleans, skill 2 enriches, skill 3 uploads. Run the chain manually, schedule it on a cron, or have Claude pause between steps so you can review before it continues.
When in doubt, describe the problem.
"I have X and Y, I need Z. Can you do this?" If it's in scope, Claude tells you how. If it's not, Claude tells you that too. Stop guessing what's possible.
most of the time, the answer is yes
Same engine, different canvases.
Features overlap on purpose. Pick the surface that fits the job: Chat for quick answers, Cowork for files and folders, Code for deep work in your repo, Design for visual output.