Claude Skills & Projects: Build and Manage Your Own Workflows
Skills are reusable instructions that give Claude new capabilities. Projects bundle knowledge, files and instructions in one place.
Orcha Team
March 6, 2026
What Are Skills?
A Skill is a saved instruction that teaches Claude how to handle a specific task your way. Instead of explaining every time how you want a monthly report structured, you save the instruction once as a Skill – and Claude applies it automatically whenever the topic comes up.
The key advantage: you often don’t even need to invoke Skills explicitly. Claude checks on its own with every task whether a matching Skill is available – and uses it automatically. Of course, you can also say something specific like “Use the Invoice Review Skill” or “Check if you have a relevant Skill for this.”
Think of Skills as SOPs (Standard Operating Procedures) for your AI. Once created, Claude delivers consistent results – no matter who on the team initiates the task.
When Do You Need a Skill?
- You repeat the same workflow at least weekly.
- Colleagues should get the same result as you do.
- Claude needs to follow specific formats, sources or review steps.
- You want to launch a workflow with a single slash command (e.g. /report).
Creating a Skill – Two Approaches
Both approaches work directly inside Claude – no code, no command line.
Approach 1: Let Claude Build the Skill for You
The easiest way: describe what you need in a new chat. Claude will ask clarifying questions and create the Skill directly in Cowork.
Example: Have Claude Create a Skill Automatically
Claude creates the Skill and activates it right away. You can find it afterwards under Customize → Skills.
Approach 2: Write the Skill Yourself
If you know exactly what you want, you can write the Skill yourself. A Skill is a simple text file in Markdown format. More on that below.
Here’s how:
- Write your instructions as a text file – with a name, description and step-by-step instructions (see examples below).
- Save the file as SKILL.md and package it in a ZIP file.
- Open Customize → Skills and click “+” → Upload Skill.
- Activate the Skill with the toggle.
Which Approach to Choose?
Approach 1 (let Claude build it) is ideal when you know your process but don’t want to deal with file formats. Approach 2 (write it yourself) pays off when you want full control over every detail. Both produce the same result – a Skill file that Claude can read.
Test and Improve
Your first draft is rarely perfect. Here’s how to refine your Skill quickly:
- Test: Start a new chat and assign a task that should trigger the Skill. In the thinking view you’ll see “Using [Skill Name]” – that confirms it was loaded.
- Sharpen the description: Claude decides based on the description when to load a Skill. “Creates quarterly reports with P&L, balance sheet and EBITDA bridge” is better than “Helps with reporting.”
- Give feedback: If the result is off, tell Claude directly what’s missing – and let it update the Skill accordingly.
Tips for Writing Good Skills
- •One Skill = one workflow. Three focused Skills beat one catch-all Skill.
- •Use imperative language: “Create a table with…” instead of “You could create a table…”
- •Include examples: A concrete input/output example shows Claude what success looks like.
- •No secrets: Never store passwords or API keys in Skills.
Four Skills You Can Copy
You can copy the following Skills directly, save them as files and upload them. Or hand the description to Claude and let it create the Skill for you.
1. Invoice Review
Checks incoming invoices for formal completeness against standard requirements.
Skill: Invoice Review
2. Budget Variance Analysis
Compares actuals against plan and explains the largest variances.
Skill: Budget Variance
3. Meeting Minutes
Turns notes or transcripts into structured minutes with action items.
Skill: Meeting Minutes
4. Contract Summary
Condenses contracts to a single page – highlighting key clauses and risks.
Skill: Contract Summary
Primer: Markdown – the Language of Skills
Skills are written in Markdown – a simple text format that is easy to read and write, even without technical expertise. Here are the most important elements:
Markdown Quick Reference
What you write:
# Heading
## Subheading
### Section
What it means:
# = Main title (like a heading in Word)
## = Section (like “Heading 2”)
### = Sub-section
What you write:
- Item one
- Item two
1. First step
2. Second step
What it means:
- = Bullet list
1. = Numbered list
Numbering tells Claude that the order matters.
What you write:
**bold text**
---
| Column A | Column B |
What it means:
**...** = Bold (emphasis)
--- = Horizontal rule (at the start of a file: metadata block)
| ... | = Table
The block at the very top of the Skill examples – between the --- lines – is called the frontmatter. It contains the Skill’s name and description. Claude reads this block to decide when to load the Skill.
Frontmatter Explained
name: Short name for the Skill (max. 64 characters). description: Describes when Claude should load the Skill (max. 200 characters). The more precise the description, the more reliably Claude recognizes the right moment.
Projects: Bundling Knowledge in One Place
While Skills are individual capabilities, Projects bundle everything for a work area: instructions, uploaded documents and chat history. Claude automatically uses this context in every conversation within the project.
Setting Up a Project
- Open the Claude Desktop App (Projects also work on claude.ai) and click “New Project.”
- Give the project a descriptive name (e.g. “Controlling Q1 2026”).
- Under “Project instructions,” add how Claude should behave – e.g. industry context, tone of voice, preferred formats.
- Upload relevant files: charts of accounts, templates, policies, prior-year reports.
Claude then automatically uses the right files as context – without you having to specify them every time.
Projects + Skills = Your AI Toolkit
The combination is particularly powerful:
- One project per work area: e.g. “Treasury,” “Controlling,” “Month-End Close.”
- Skills per recurring task: In the “Controlling” project, for example, Skills for budget variance, monthly report and forecast.
- Documents as a knowledge pool: Upload your chart of accounts, booking policies, year-over-year comparisons.
This way you open Claude, type your question – and Claude already knows who you are, what you need and in which format.
Sharing Projects (Team & Enterprise)
On Team and Enterprise plans, you can share projects with colleagues:
- Can use: View content and chat, but cannot edit.
- Can edit: Modify instructions, manage files, invite members.
Conclusion
Skills and Projects are the fastest way to tailor Claude to your workflow – no programming required. Start with a Skill for a task you perform every week. Once you’ve accumulated several Skills, organize them in a Project. The effort pays off quickly: fewer repetitions, more consistent results and more time for actual analysis.
Get more guides like this?
Subscribe to our newsletter for new resources straight to your inbox.