How much time will I actually save with Fazm?

Most users report saving 45-90 minutes per day on repetitive tasks. The biggest time savings come from email management (drafting replies, sorting, archiving), form filling (expense reports, CRM updates, applications), research (comparing products, gathering data from multiple sites), and social media (cross-posting, scheduling, replying). For example, booking a flight that normally takes 10 minutes of clicking through airline sites takes a single voice command with Fazm. Filing an expense report that requires opening a PDF, extracting numbers, and entering them into a spreadsheet becomes one spoken sentence. The more repetitive and multi-step your daily work is, the more time you get back.

What exactly can Fazm control?

Fazm controls everything you can do manually on your Mac. That includes mouse movements and clicks, keyboard typing, browser navigation and form filling, app switching, file management in Finder, and system-level actions. It uses direct browser DOM control for web interactions - meaning it reads and manipulates the actual page structure rather than taking screenshots and guessing where to click. For native macOS apps, Fazm uses accessibility APIs to interact with buttons, menus, text fields, and other UI elements. This works across any application: Chrome, Safari, VS Code, Slack, Figma, Terminal, Mail, Calendar, and more.

How is Fazm different from ChatGPT or Claude?

Chatbots like ChatGPT and Claude give you answers in a conversation window. Fazm takes action directly on your computer. When you say 'reply to Sarah's email,' Fazm opens your email app, finds Sarah's message, writes a contextual reply, and sends it. A chatbot would tell you what to write, but you still have to do all the clicking and typing yourself. Fazm moves your mouse, types on your keyboard, clicks buttons, and navigates between apps. It is a computer agent, not a chat assistant.

How does the memory layer work?

Fazm builds a personal knowledge graph by extracting information from your files, browsing history, conversations, and daily activity. Over time, it learns your contacts (names, emails, relationships), accounts and credentials, preferences (formatting, tone, scheduling habits), and frequently used workflows. In your first week, you might say 'Reply to Sarah's email, she's my cofounder, her email is sarah@acme.com.' By week four, you just say 'Reply to Sarah' because Fazm already knows who she is. By week eight, Fazm can draft the reply before you even ask. All of this data stays locally on your Mac - your knowledge graph never leaves your machine or gets sent to any cloud service.

Is Fazm safe? Can it mess up my computer?

Safety is built into every layer of Fazm. You watch every action in real-time on your screen - Fazm moves your mouse and types visibly, so there is nothing hidden. You can stop any action at any point by pressing a keyboard shortcut. Fazm also shows you what it plans to do before executing destructive actions like deleting files or sending emails, giving you a chance to confirm or cancel. Because Fazm is open source, the code is fully auditable on GitHub. There is no hidden behavior, no background processes making changes you cannot see, and no actions that bypass your screen.

What platforms does Fazm support?

Fazm currently supports macOS, running natively on both Apple Silicon (M1, M2, M3, M4) and Intel Macs. It is built with Swift and uses macOS-specific frameworks like ScreenCaptureKit for screen analysis and Accessibility APIs for app control, which is why macOS is the primary platform. Windows and Linux support are on the roadmap but do not have release dates yet. You can also control your Mac remotely from your phone using Fazm Remote, which gives you voice access to your desktop while you are away from your computer.

How does Fazm voice input work?

One keyboard shortcut activates push-to-talk. Hold the key, speak naturally about what you need done, and release. Fazm transcribes your speech locally using on-device models, so there is no network latency for the voice recognition step. You do not need wake words like 'Hey Siri' or 'OK Google' - just press and talk. You can also type commands into the floating toolbar if you prefer text input. Fazm understands natural language, so you do not need to memorize specific commands. Say 'book me a flight to Tokyo next Thursday' or 'find the cheapest AirPods on Amazon' and Fazm figures out the steps.

Is my data sent to the cloud?

Fazm processes screen analysis and memory entirely on your machine. The personal knowledge graph, file indexing, and screen capture all run locally. The only data that leaves your Mac is the intent - a text description of what you want to accomplish, which is sent to the AI model (Claude or GPT) for action planning. Your actual screen content, file contents, browsing history, and personal knowledge graph never leave your computer. Fazm is also open source, so you can verify exactly what data is transmitted by reading the code on GitHub. For users who need complete air-gapped operation, local model support is planned.

Back to Blog

Custom Skills vs Marketplace Skills in Claude Code - Why Building Your Own Wins

Fazm Team·March 17, 2026·3 min read

claude-codeskillsdeveloper-toolsproductivityautomation

Custom Skills vs Marketplace Skills in Claude Code

After months of using Claude Code daily, we ended up with mostly custom skills written for specific recurring tasks. The official marketplace skills are hit or miss. Here is why.

The Marketplace Problem

Marketplace skills are built for general use cases. They have to work for everyone, which means they work perfectly for no one. A generic "deploy to production" skill cannot know your specific CI pipeline, your environment variable naming convention, or your team's deployment checklist.

The result is that marketplace skills either:

Do too little. They handle the happy path and leave you to deal with every edge case manually.
Do too much. They try to be comprehensive and end up adding complexity you do not need.
Make assumptions. They assume a specific stack, directory structure, or workflow that does not match yours.

Why Custom Skills Win

A custom skill is a markdown file that encodes your exact workflow. It knows:

Your project's specific file structure and naming conventions
The exact sequence of commands for your deployment pipeline
Which files to check, which tests to run, which logs to tail
Your team's code review checklist and PR template

For example, our send-fazm-email skill knows to use a specific Python script with curl-based HTTP requests (because Cloudflare blocks Python's default user agent), the correct Resend API endpoint, and our domain's verified sender address. No marketplace skill would encode that level of specificity.

The 80/20 Split

In practice, about 80% of the skills we use daily are custom-built. The remaining 20% from the marketplace are genuinely general-purpose - things like "format this code" or "explain this error."

The pattern that works:

Start with marketplace skills for common tasks.
Notice where they fall short for your specific workflow.
Fork or rewrite them as custom skills with your exact requirements.
Iterate as your workflow changes.

Building Custom Skills for Agents

The same principle applies to building Fazm. Generic automation templates are a starting point, but the real value comes when the agent learns your specific workflows and builds custom execution patterns around them.

Custom Skills vs Marketplace Skills in Claude Code - Why Building Your Own Wins

Custom Skills vs Marketplace Skills in Claude Code

The Marketplace Problem

Why Custom Skills Win

The 80/20 Split

Building Custom Skills for Agents

More on This Topic

Related Posts

The Irony of AI Automation - Debugging Skills Takes Longer Than the Original Task

Claude Code Skills Are Mini Startup Wrappers - How Playwright MCP Ties 30+ Skills Together

Skills vs MCP vs Plugins - What's the Difference?