Skills

A skill is a transcription of a process. You tell Claude: “Here’s a guide on copywriting, do it this way.” Claude reads it and then uses it. It’s not software, it’s not a plugin. It’s just text with a pattern.

I have 113 skills on disk. That sounds like a lot, but I actually use about 20 to 30 that have proven useful. The rest are experiments or old versions I keep just in case. In any given month I actively use about 10 to 15: session-bootstrap comes along at the start of each conversation (it takes notes on where I left off), deep-research for finding new things online, copywriting, content structure. Then I use design skills — like euphronic-design-system, which watches over color, typography, and the feel of the web.

It’s about quality, not quantity. If I had 200 skills and only five percent worked, I’d rather delete them all. I’ll take these 113 and pick ten that I trust and have tested. What doesn’t work, I throw away or rewrite. There’s no sentiment in it.

MCP servers

MCP is like a USB cable. An agent is the brain, but by itself it can’t look anywhere outside the text chat. I connect an MCP — and suddenly it can ask Notion questions, read from Supabase, peek at GitHub, open the browser’s devtools. It touches real tools that it needs.

I use eight MCP servers. Notion for notes and decisions. Supabase for website data — forum, accounts, posts. Vercel for deploying websites. Cloudflare for domain and DNS. Sentry for production errors. context7 for current library documentation. chrome-devtools for a look at the live page. Obsidian for a vault of notes with search. Each one does one thing well. I don’t plug everything in at once — just what I need right now. Otherwise I just add unnecessary complexity.

What does it give me: Claude is no longer just a chat window. It’s a bridge to every tool I use every day. I don’t have to manually copy anything between windows. The details are in the My stack section.

Plugins

A plugin is a small app that runs in Claude Code. A skill is a guide in text. A plugin is code that does something. If a skill were a recipe written down, a plugin would be the cook.

I use them sparingly. From the Marketplace I pick specialists in things I do often. Every plugin uses resources and attention. It’s not about having everything — it’s about what I have working without mistakes. The rest just slows things down and distracts.

I don’t add things just because they exist. Each plugin has to actually save time or do something that’s otherwise hard. Otherwise I’ll pick it up for one task and remove it again.

Agents

An agent is an assistant with a specialty. It’s like a team of mechanics. You don’t send them all at once. Electricians on electricity, carpenters on wood, welders on metal. I do the same — I pick a specialist based on the job.

I pick the specialist best suited to the problem at hand. Write content? content-marketer. SEO? SEO specialist. Security audit? security-reviewer. A general assistant is just a backup. A specialist knows more and doesn’t need long explanations.

I tell Claude what I want, and Claude picks the right agent. Sometimes I choose one myself when I know what I need. The nice thing is that agents work in parallel — one gets the groundwork ready, another processes it, or they work independently and I assemble the results afterward.

How we’ve wired it all into one workflow, you can read in the How I work section.