
Quick poll: Have you tried building a custom workflow with AI before?
Okay here's the thing we need to talk about:
Creating monthly expense reports are a 2-3 hour nightmare.
Every single month.
You're hunting down receipts from Uber, Amazon, that one coffee shop that only does message receipts.
Exporting bank statements.
Categorizing everything.
Fighting with your company's god-awful template in Excel.
And your options?
Either waste those 3 hours, pay $19/month for some half-broken expense app, or drop $200 on a freelancer who'll take a week to respond.
Claude Skills changes this to 5 minutes.
I tested it last week.
DIDN'T OPEN EXCEL ONCE.
What are Claude Skills?
Instruction manuals that teach Claude to be an expert at specific tasks. You're basically giving Claude a crash course in exactly how to do what you need.
Think of it like handing someone a playbook instead of making them figure it out from scratch.
But first, here’s what happened this week:
AI Tools That Made Me Question Everything This Week
1. Manus 1.5: Build full‑stack AI apps
A general‑purpose AI agent that builds and runs end‑to‑end projects for you. Think full‑stack web apps with auth, databases, embedded AI, custom domains, and built‑in analytics, directly through a chat. It also handles research, data analysis, slides, and more, with a big context window and faster execution to keep multi‑step workflows coherent
2. Director 2.0: Automate web tasks with a single prompt.
A prompt‑to‑automation app: describe a web task, and it generates a Stagehand script that runs on Browserbase to reliably control the browser. It’s built for non‑developers and developers alike: preview actions, iterate quickly, and ship repeatable workflows without writing boilerplate automation code
3. Faith: 100% free AI Bible app
An AI Bible companion on iOS that lets you chat about Scripture across multiple translations, get answers to common topics, and study on the go. It’s positioned as a free, ad‑free experience, offering a simple interface for devotional reading and AI‑guided exploration of verses and themes.
Okay, back to Claude Skills.
Let me break down what's actually happening here:
Skills are structured instructions that tell Claude exactly how to use tools the right way.
Think about it: You can tell a junior employee "make a presentation" and they'll eventually figure it out after three rounds of feedback and a lot of wasted time.
Or you give them templates, brand guidelines, and examples of what good looks like and they nail it the first time.
That's Skills. Claude isn't guessing anymore. It has expert documentation that says "here's exactly how to build a PDF, format an Excel sheet, or structure a PowerPoint the professional way, not the 'I hope this works' way."
Less trial and error. Actual consistency. Way faster execution.
Let me show you what this looks like in practice:
The Old Way (Pre-Skills):
You: "Claude, analyze this spreadsheet and create a PDF report."
Claude: "I can help you understand the data and suggest what to include in your report..."
Then YOU have to:
Export your data from wherever it lives
Open Excel/Sheets and manually organize it
Copy paste into a document
Try to make it look professional
Fight with formatting for 20 minutes
Export to PDF and hope it doesn't look broken
Total time: 1-3 hours (or you procrastinate for a week)
The New Way (With Skills):
Skills are specialized instruction files that live in the Claude system. When you're using Claude through the desktop app or API, you can:
Use built-in Skills: Anthropic has created expert guides for common tasks like creating Word docs, Excel spreadsheets, PowerPoint presentations, and PDFs
Upload custom Skills: You can write your own instruction manual (or use tools to generate one) that teaches Claude YOUR specific workflow
Combine Skills: Chain multiple skills together for complex automation
When you activate a Skill, Claude reads the instructions and applies them to your task. It's like hiring a specialist who already knows exactly how your tools work.
Here's a real example I built yesterday:
The Task: Generate weekly content reports from my newsletter analytics (opens, clicks, top links) and format them into a branded PDF.
Before Skills:
Log into my newsletter platform
Filter by date, and export the analytics data
Open a spreadsheet and manually filter for the metrics I care about
Copy the numbers into a doc
Go to Canva and update the data on the template design we use every week
Export as PDF
Total time: 30-45 minutes
With Claude Skills:
First time setup: Created a custom skill for my newsletter reports (~20 minutes, one time only)
Every week after that: Upload CSV, tell Claude "use newsletter-analytics-reporter"
Recurring time per report: 3 minutes
Time saved monthly: ~2.5 hours (that I was spending on this boring task)
The 20-minute upfront investment pays for itself after the second use.
The PDF it generated matched our brand style without me specifying any of it beyond "use our brand style."
I've been doing this report manually for 6 months.
The first time I saw Claude do it in under 3 minutes, I just sat there thinking "why the hell was I doing this myself?"
But wait, you can also create CUSTOM skills!
This is the part most people will get lazy about, even I did at first. Don't be like me.
Anthropic built something called the Skill Creator (skill.md) - basically a meta-skill that helps you write instruction manuals for Claude.
You can:
Teach Claude how to use YOUR company's specific tools
Automate workflows that are unique to your job
Build Skills for niche software that doesn't have official support
And someone built a Skill generator that walks you through creating custom Skills without writing a single line of code.
My take: This is Black Mirror disguised as productivity tech. In a good way. You're literally teaching AI to automate your grunt work while everyone else is stuck in the same "let's circle back on this" meeting for the third week in a row.
How to actually setup Claude skills
Prerequisite:
Subscription: Skills are available to Pro, Max, Team, and Enterprise users of Claude apps.
You can start a new claude chat directly, Anthropic provides a tool to guide you through skill creation without manual file editing.
Step 1: Enable Skills in Settings
Navigate to your Claude Settings > Capabilities, and scroll down.
Ensure that Skills are enabled.
Step 2: Access the Skill Creator
Locate the "skill-creator" skill.
Click on "try and chat" to open a new chat window.
Step 3: Define the Workflow
Claude will provide a template to start with. You can edit the prompt based on your requirements.
Claude may ask for more details about the specific workflow you want to automate or specialize.
The skill-creator will then generate the necessary folder structure, format the core
SKILL.mdfile, and bundle any resources you need.
You can then reference these custom skills in your chats, and Claude will automatically invoke the relevant skill based on your task, no manual selection is needed.
Step 4: Test Your Skill Before Relying on It
The first version won't be perfect. Run it with:
Real data from your actual workflow (not test data)
Edge cases like missing information or unusual formatting
Different scenarios if your workflow varies (weekly vs monthly reports, different data sources)
When something breaks or looks wrong, describe the issue to Claude in the same chat. It'll update the skill instructions automatically.
I had to do 3 rounds of "actually, can you adjust the header spacing" before my newsletter report skill was dialed in. That's normal.
Step 5: Name It Like You'll Actually Remember It
Use clear, descriptive names:
"expense-report-generator"
"weekly-newsletter-analytics"
"client-invoice-formatter"
Don't use:
"my-skill"
"skill-1"
"new-workflow"
Future you (and your coworkers if you share skills) will appreciate the clarity when you have 10+ custom skills in your library.
Best practices - straight from the anthropic cookbook.
1. Make Skills focused and specific
Don't create one mega-skill that does everything
Better to have multiple specialized Skills than one general one
Example: Separate "Generate Invoice" and "Track Expenses" Skills instead of one "Finance Management" Skill
2. Include clear examples in your Skill instructions
Vague instructions = inconsistent results. Be specific about what you want.
Bad example: "Format the report to look professional"
Good example: "Use Helvetica 12pt for body text, 18pt bold for section headers, 1.5 line spacing. Include our logo (logo.png) in the top right corner at 150px width. Use #003366 for headers and #666666 for body text."
The second version gives Claude zero room for interpretation. That's what you want.
When I was building my newsletter analytics skill, I included a screenshot of my ideal report layout in the instructions. Now every report looks identical, which is exactly the point.
3. Test your Skills with edge cases
What happens if data is missing?
What if the file format is slightly different?
Build error handling into your Skill instructions
4. Version control your Skills
When you update a Skill, save the old version
Document what changed and why
Makes it easy to roll back if something breaks
5. Start simple, then expand
Build a basic version that works
Add complexity gradually
Don't try to automate everything on day one
In reality
"Skill issue" just got a new meaning, and you can now actually use it at work.
For the last 2 years, AI productivity has had a massive gap:
What AI can theoretically do ≠ What regular people can actually make it do
You read about AI automating everything, but when YOU try it:
Too technical
Requires coding
Breaks constantly
Takes longer than doing it manually
Claude Skills closes that gap.
This won't dominate headlines like "AGI achieved" or "Haiku 4.5 beats GPT-5."
But it's a shift from: "AI could help me if I spent 10 hours learning how to make it work"
to: "AI just did my work in 10 minutes, and I have no idea how the tech works"
That's the point.
The best technology disappears. You shouldn't need a CS degree to generate a report or know Figma to make a presentation.
You just need the result.
And here's the crazier part: Skills aren't just personal productivity hacks. They're the foundation for agent-based automation.
When AI agents go mainstream (and they will), they'll need Skills to interact with YOUR specific tools, APIs, and processes. The companies building Skills libraries right now? They're building the operating system for AI agents.
Most of the world hasn't caught on yet. You just did.
Now the question is: what are you going to build with it? What's the first workflow you're going to automate with Claude Skills?
Hit reply and tell me. I'm genuinely curious if people use this for work tasks, personal projects, or something completely unexpected.
Until next time,
Vaibhav 🤝
If you read till here, you might find this interesting
#AD 1
Founders need better information
Get a single daily brief that filters the noise and delivers the signals founders actually use.
All the best stories — curated by a founder who reads everything so you don't have to.
#AD 2
How to pick the right global payroll mode
Find your fit: Deel’s free guide breaks down 3 global payroll models with key benefits and tradeoffs for HR and finance teams.












