What Are Claude Skills? I Tested 5 of Them for 30 Days as an Engineer

What are Claude skills? The short answer is they are reusable instruction files that teach Claude how to work exactly the way you want it to, loaded automatically when you need them. The longer answer is that after 30 days of using five specific skills as a civil engineer who also runs a blog and tracks stocks, they changed my workflow in ways I did not fully expect.

This post contains affiliate links. If you sign up through my links I may earn a commission at no extra cost to you.

I want to cover two things in this article. First, exactly what Claude skills are and how they work, because most explanations I have found online are either written for developers or buried in technical documentation. Second, the five specific skills I tested and what each one actually did for my day-to-day work. If you have a Claude Pro subscription and you are not using skills yet you are leaving a significant chunk of the tool’s value on the table.

What Are Claude Skills: The Plain English Explanation

A Claude skill is a SKILL.md file. That is it at the technical level. It is a markdown document that contains standing instructions telling Claude how to behave for a specific type of task. When you install a skill and start a relevant conversation, Claude reads those instructions automatically before doing anything else.

Think about what normally happens when you start a new Claude session. You spend the first few messages re-explaining your context, your preferences, your standards, and what you want the output to look like. If you write for a blog you re-explain your voice rules. If you do stock research you re-explain your sourcing requirements. If you generate reports you re-explain your formatting. Skills eliminate all of that setup completely.

The way skills work in practice is straightforward. You install a skill once through claude.ai or by placing the SKILL.md file in your Claude environment. From that point on, whenever you start a conversation that matches what the skill is designed for, Claude loads those instructions automatically. You do not have to tell it to. You do not have to remind it. The behavior is just there.

Skills exist as both community-built options in the Claude marketplace and custom files you build yourself for your exact workflow. The community skills are built by developers and researchers who have open-sourced their instruction sets. The custom skills are where things get genuinely powerful because you can encode your specific standards, your specific voice, your specific requirements into a file that runs permanently.

One practical note before we get into the five skills: Claude skills require a Claude Pro subscription at $20 per month. If you are already paying for any AI subscription and you are not on Claude Pro, the skills alone make the switch worth considering. If you are already on Pro and not using skills, the rest of this article is for you.

Why Claude Skills Actually Matter for Working Professionals

Most AI content online treats these tools as novelties. Here is a cool thing you can do with Claude. Here is a fun prompt. What skills actually represent is a systematic approach to making AI consistent rather than just capable.

Capable is easy. Claude can write, analyze, code, and research without any skills at all. The problem is capability without consistency. Every session you start from scratch. Every output reflects slightly different defaults. Every article, every report, every analysis has a slightly different character depending on how the conversation happened to unfold.

For someone doing one thing with AI occasionally, that inconsistency does not matter much. For a working professional who uses Claude daily across multiple domains simultaneously, it costs real time. I context-switch between engineering work, stock research, and blog writing in the same day. Before skills, every switch meant re-explaining my context. After skills, the context is just there.

The time savings I estimated after 30 days came out to roughly 45 minutes per week in setup time recovered. That is not a dramatic number but it compounds. Over a year that is 39 hours. More importantly, removing setup friction means I actually use the tool more consistently rather than deciding the setup cost is not worth it for a quick task.

The 5 Claude Skills I Tested and What Each One Actually Does

I want to be clear that I am describing my actual experience using these skills in real work, not a feature summary from a product page. Some performed exactly as expected. One surprised me in a way I did not anticipate. One I use less than I thought I would.

Skill 1: The Humanizer

The Humanizer is the skill I use on every single piece of writing that goes anywhere public. It has over 7,000 GitHub stars and is one of the most widely used Claude skills in the community right now. The reason is simple: it solves the most visible problem with AI-assisted writing.

What it does is run your draft through a 29-point checklist drawn from Wikipedia’s guide on identifying AI-generated writing. It targets the specific patterns that make AI writing feel flat: overly balanced sentence structure, passive constructions, inflated language, and what the writing community calls slop vocabulary. Words like delve, tapestry, realm, and embark that language models reach for disproportionately. After reading this you will probably never use the word delve again.

The skill runs two passes. The first rewrites against the 29 rules. The second is a self-audit where Claude asks itself what still sounds AI-generated and fixes the remaining tells. The result is writing that varies sentence length naturally, uses concrete details instead of vague claims, and reads like a person with opinions rather than a content generator.

My experience: I started noticing the difference immediately. The most obvious change was shorter sentences appearing naturally after longer analytical ones. The second was that the output stopped hedging everything. AI writing tends to qualify every claim. The Humanizer strips most of that out and replaces it with direct statements.

The honest caveat: the two-pass audit uses more tokens than a single rewrite. For a 1,500-word article this adds a noticeable amount to your session cost. I consider it worth it every time for public writing but I skip it for internal drafts and notes.

Skill 2: The Prompt Master

Before I understood prompt structure I treated Claude like a search engine. I described what I wanted in plain language and got back something in the general neighborhood of what I asked for. Sometimes great, usually okay, occasionally useless.

The Prompt Master skill fixes this by restructuring your requests before Claude ever sees them. You describe what you are trying to accomplish and the skill converts that into an optimized prompt with proper role assignment, task structure, constraints, and output format specification. The difference in output quality is real and consistent.

My experience: the biggest change was in first-pass accuracy. Before Prompt Master I typically needed two or three exchanges before getting something usable for complex tasks. After, most complex requests land right on the first try. The skill is basically encoding the knowledge of what makes a good prompt so you do not have to remember it every time.

The use case where I lean on this most is when switching contexts. Moving from an engineering report in the morning to a stock research task in the afternoon requires a completely different prompt structure. The Prompt Master handles the structural requirements of each context automatically, which means I am not rebuilding the wheel every time I switch.

Skill 3: The Fact Checker

This one is non-negotiable for anyone writing about finance, investing, or anything requiring factual accuracy. Claude hallucinates. It will confidently state a number, a date, or a claim that is simply wrong. Not often, but regularly enough that publishing without verification is a genuine risk. If you put wrong financial information on the internet with your name on it you lose reader trust and potentially your legal standing.

The Fact Checker skill cross-references claims in your content against external sources and categorizes each one as confirmed, unverifiable, or false. It applies what researchers call lateral reading, the most effective verification technique according to Stanford’s Computational Online Research Lab, to AI-generated drafts.

My experience: I run this before the Humanizer on every article that contains statistics, named figures, dates, or financial data. Fix accuracy first, then fix voice. I have caught three factual errors in my own drafts over 30 days using this skill. Two were wrong numbers, one was an incorrectly attributed quote. Any one of those published would have been a problem.

Where it falls short: it cannot verify very recent information or proprietary data. For SEC filings and earnings data I still check primary sources manually. The skill handles the bulk verification efficiently but it is not a replacement for checking the things that matter most.

Skill 4: The Skill Creator

This is the meta-skill and the one that surprised me most. The Skill Creator builds new Claude skills based on your description of a workflow, standards, or task type. You do not need to know how SKILL.md files are structured. You describe what you want and it generates the file.

I used the Skill Creator to build two custom skills that do not exist anywhere publicly. My blog writing skill encodes my no-dashes rule, my affiliate disclosure placement requirements, my SEO three-kings structure, my financial disclaimer standards, and my voice guidelines. My stock research skill knows to always cite primary sources, never project returns, and frame everything for a time-limited professional reader rather than a day trader.

Before these custom skills existed I spent the first several messages of every writing or research session re-explaining the same rules to Claude. Now those rules load automatically. The Skill Creator made it possible to encode my specific workflow without knowing anything about file structure or prompt engineering.

If you only install one skill from this list, install the Skill Creator first and use it to build a custom skill for your most repeated task. That is the highest leverage move available here.

Skill 5: The Document Skills Suite

The Document Skills Suite covers PDF, Word, and Excel file generation with consistent formatting and formula accuracy. As a civil engineer I deal with project reports, submittal logs, RFI tracking sheets, and status update documents constantly. Before document skills I would generate a draft in Claude and spend time manually cleaning up formatting, formula references, and table structures in the final file.

The Excel component is where this skill earns its keep most clearly for me. It handles formula recalculation, REF and DIV0 error checking, and column width formatting automatically. Anyone who has had a spreadsheet break when a colleague opens it on a different version of Excel knows exactly why this matters.

For the blog side of my work this skill powers the budget templates, stock trackers, and credit card comparison spreadsheets I release as free downloads. Being able to generate a clean, functional Excel file with live formulas directly from Claude without manual cleanup saves probably an hour per tool I build.

The skill I use least in this suite is the PDF generator, not because it does not work but because my workflow rarely requires standalone PDFs. The Word and Excel components get used weekly.

How to Get Started With Claude Skills Today

Go to claude.ai and open your settings. The skills section is in the left sidebar of your Claude interface. From there you can browse the marketplace or install skills directly from GitHub repositories using the SKILL.md file approach.

The order I recommend installing:

1. Skill Creator first. Use it to build a custom skill for your most repeated task before installing anything else.
2. Humanizer second. It applies to everything you write immediately and you will see the difference on the first use.
3. Fact Checker third. Install before publishing anything that contains data, statistics, or financial information.
4. Prompt Master fourth. Install once you have a clear sense of your recurring task types.
5. Document Suite last. Install when you need to generate Excel, Word, or PDF files directly.

I put together a free PDF with the exact setup steps, the install links, and the copy-paste prompts I use with each skill. Drop your email below and I will send it over.

[EMAIL CAPTURE: Get the free Claude Skills Setup Guide and Prompt Templates]

Claude is a product made by Anthropic. Skill availability, features, and pricing are subject to change. This article reflects my personal 30-day experience using Claude skills in my own workflow. Always verify current terms at claude.ai before subscribing.

Related (COMING SOON): [LINK: ChatGPT vs Claude vs Gemini: Which AI Is Best for Young Professionals in 2026] | [LINK: How to Set Up Claude Projects Without Wasting Tokens]