Skip to content
Claude for Operators

Building Custom Skills Without Writing Code

Last verified: 21 April 2026 | Applies to: All plans including Free

In 30 seconds

Section titled “In 30 seconds”

Skills are saved instructions that change how Claude behaves for specific tasks. You do not need to be a developer to build them. A skill is a folder with a markdown file. This guide walks you through creating your first skill in under 10 minutes, with templates for common operator use cases.

What a skill actually is

Section titled “What a skill actually is”

A skill is a folder on your computer that contains a file called SKILL.md. That file holds plain-text instructions telling Claude how to handle a specific type of task. When you activate a skill, Claude reads those instructions and follows them for the duration of your session.

That is it. No code. No configuration files. No deployment. Just a folder and a markdown file.

Think of skills as reusable SOPs for Claude. The same way you might write a checklist for a team member (“when processing expense reports, always categorise by department, flag anything over $500, and use the standard template”), a skill gives Claude the same kind of standing instructions.

Skills work in both Chat and Cowork, across all plans including Free.

Your first skill in five steps

Section titled “Your first skill in five steps”

Step 1: Create the folder

Section titled “Step 1: Create the folder”

On your computer, create a new folder. The name should describe what the skill does:

~/Documents/claude-skills/weekly-ops-report/

Step 2: Create the SKILL.md file

Section titled “Step 2: Create the SKILL.md file”

Inside that folder, create a file called SKILL.md. Open it in any text editor (TextEdit, Notepad, VS Code, anything).

Step 3: Write the instructions

Section titled “Step 3: Write the instructions”

Paste in clear, specific instructions for Claude. Here is a simple example:

# Weekly Ops Report Generator


## What this skill does
Generates a weekly operations report from provided data and notes.


## Format
- Start with a 3-sentence executive summary
- Follow with sections: Wins, Blockers, Metrics, Next Week Priorities
- Use bullet points, not paragraphs
- Keep the total report under 500 words


## Tone
- Direct and factual
- No filler phrases ("I'm pleased to report", "as we discussed")
- Flag problems clearly, do not soften bad news


## Metrics to always include
- Revenue vs target (percentage)
- Customer count change (net new)
- Support ticket volume and resolution rate
- Team capacity (who is overloaded, who has bandwidth)

Step 4: Activate the skill

Section titled “Step 4: Activate the skill”

In Claude Desktop, go to Settings → Skills and point to your skills folder (~/Documents/claude-skills/). Claude scans the folder and makes all skills inside it available.

Alternatively, in Cowork, you can reference a skill directly:

Use my weekly-ops-report skill to create this week's report. Here are my notes: [paste notes]

Step 5: Test it

Section titled “Step 5: Test it”

Give Claude a task that the skill covers. Check whether the output follows your instructions. Refine the SKILL.md if needed. Most skills need two or three rounds of refinement before they consistently produce the output you want.

Skill creation flow

Section titled “Skill creation flow”
graph LR
    A[Identify repetitive task] --> B[Write instructions in SKILL.md]
    B --> C[Save to skills folder]
    C --> D[Test with real task]
    D --> E{Output correct?}
    E -->|Yes| F[Skill is ready]
    E -->|No| B

Start with a task you do at least weekly. Write instructions the way you would brief a capable new hire. Test, refine, repeat.

Five starter skill templates

Section titled “Five starter skill templates”

Copy any of these into a SKILL.md file. Customise the details for your business.

1. Weekly ops report generator

Section titled “1. Weekly ops report generator”

Folder: ~/Documents/claude-skills/weekly-ops-report/

# Weekly Ops Report


## Purpose
Generate a structured weekly operations report from my notes and data.


## Structure
1. Executive summary (3 sentences max)
2. Key metrics table (revenue, customers, tickets, team utilisation)
3. Wins this week (bullet points)
4. Blockers and risks (bullet points, flag severity: low/medium/high)
5. Priorities for next week (numbered list, max 5 items)


## Rules
- Total length: 400-600 words
- Use Australian English
- No jargon without explanation
- If data is missing, note what is missing rather than guessing
- Always compare metrics to the previous week and to target
- End with one clear "biggest risk" callout

2. Client onboarding checklist

Section titled “2. Client onboarding checklist”

Folder: ~/Documents/claude-skills/client-onboarding/

# Client Onboarding Checklist


## Purpose
Generate a customised onboarding checklist for a new client based on their details.


## Required inputs
- Client name and company
- Service tier (Starter, Growth, Enterprise)
- Start date
- Primary contact name and email


## Checklist structure
1. Pre-kickoff (before start date)
   - Send welcome email with login credentials
   - Schedule kickoff call
   - Prepare onboarding deck customised to their tier
   - Set up project folder in shared drive
2. Week 1: Kickoff and setup
   - Run kickoff call (45 min)
   - Configure their account
   - Send first training resource
   - Assign internal team member as point of contact
3. Week 2: First milestone
   - Check in call (30 min)
   - Review first deliverable
   - Collect initial feedback
4. Week 4: Handoff to ongoing
   - Transition from onboarding to regular cadence
   - Send feedback survey
   - Update CRM status to Active


## Rules
- Personalise every checklist with the client's name and details
- Include specific dates calculated from the start date
- For Enterprise tier, add: security review, custom SLA, executive sponsor introduction
- Output as a markdown checklist with checkboxes

3. Email voice and tone guide

Section titled “3. Email voice and tone guide”

Folder: ~/Documents/claude-skills/email-voice/

# Email Voice Guide


## Purpose
Apply our company's communication style to all email drafts.


## Voice characteristics
- Professional but warm, not corporate
- First-person plural ("we") for company communications
- First-person singular ("I") for individual emails
- Short sentences. Short paragraphs. One idea per paragraph.
- Active voice always. Never passive.


## Structure rules
- Subject line: specific and action-oriented (not "Update" or "FYI")
- Opening: get to the point in the first sentence. No "I hope this finds you well."
- Body: lead with the most important information
- Closing: clear next step or call to action
- Sign-off: "Cheers," for informal, "Best regards," for formal


## Words we use
- "Update" not "communication"
- "Issue" not "challenge" or "opportunity"
- "Fix" not "remediate"
- "Deadline" not "target date"


## Words we avoid
- "Just" (as in "just checking in")
- "Synergy", "leverage", "circle back", "touch base"
- "Please do not hesitate to" (say "feel free to" or just ask directly)
- "As per my last email" (just restate what you need)

4. Meeting prep format

Section titled “4. Meeting prep format”

Folder: ~/Documents/claude-skills/meeting-prep/

# Meeting Prep Brief


## Purpose
Create a one-page meeting preparation brief.


## Required inputs
- Meeting title and purpose
- Attendees (names and roles)
- Duration
- Any background materials or context


## Brief structure
1. **Objective** (one sentence: what decision or outcome do we need?)
2. **Attendees** (name, role, what they care about in this meeting)
3. **Context** (3-5 bullet points: what happened since last meeting, any open items)
4. **Discussion points** (numbered, with time allocation for each)
5. **Pre-read** (links or summaries of any materials to review beforehand)
6. **Desired outcome** (what does "success" look like for this meeting?)


## Rules
- Keep the entire brief to one page (roughly 400 words)
- Allocate specific minutes to each discussion point
- Flag any attendee who may have concerns or objections
- If background materials are provided, summarise key points rather than linking to full docs
- Always include a "parking lot" section for topics to defer

5. Expense categorisation rules

Section titled “5. Expense categorisation rules”

Folder: ~/Documents/claude-skills/expense-categorisation/

# Expense Categorisation


## Purpose
Categorise business expenses consistently using our chart of accounts.


## Categories
- **Software & SaaS**: any recurring software subscription
- **Professional Services**: legal, accounting, consulting fees
- **Marketing**: advertising, events, sponsorships, content production
- **Travel**: flights, accommodation, transport, meals while travelling
- **Office**: supplies, equipment under $500, furniture
- **Equipment**: purchases over $500 (capitalise, do not expense)
- **Meals & Entertainment**: client meals, team meals (not travel meals)
- **Training**: courses, certifications, conference tickets
- **Telecommunications**: phone, internet, mobile plans
- **Insurance**: all insurance premiums
- **Miscellaneous**: anything that does not fit above (flag for review)


## Rules
- If an expense could fit two categories, use the more specific one
- Always flag expenses over $1,000 for review
- Split expenses that cover multiple categories (e.g., a conference ticket that includes accommodation)
- Use the vendor name as it appears on the receipt, not a shortened version
- For recurring expenses, note the billing frequency (monthly, annual)
- Output as a table: Date, Vendor, Amount, Category, Notes, Flag (if applicable)
- Australian dollar amounts unless otherwise specified

Testing and refining your skill

Section titled “Testing and refining your skill”

After creating a skill, test it with real inputs, not hypothetical ones. Use actual data from your last week.

What to check:

  • Does the output follow the structure you specified?
  • Is the tone right?
  • Are there edge cases your instructions did not cover?
  • Is Claude making assumptions you did not intend?

Common refinements after the first test:

  • Adding explicit “do not” instructions (Claude tends to be verbose; you may need to say “do not add introductory paragraphs”)
  • Specifying output format more precisely (markdown table vs bullet list vs numbered list)
  • Adding examples of good and bad output
  • Clarifying what to do when inputs are incomplete

Most skills stabilise after two or three rounds of testing and refinement.

Sharing skills with your team

Section titled “Sharing skills with your team”

Skills are just folders with markdown files. Sharing them is straightforward:

  • Shared drive. Put your skills folder on Google Drive, Dropbox, or a shared network folder. Team members point their Claude skills directory to the shared location.
  • Git repository. For teams comfortable with Git, store skills in a repo. Version control means you can track changes and roll back if a skill update makes things worse.
  • Copy and paste. For a small team, simply send the SKILL.md file and let each person save it to their own skills folder.

On Team and Enterprise plans, admins can manage skills centrally. See Team Rollout for the full process.

What to watch out for

Section titled “What to watch out for”
Section titled “Related”

Something wrong or outdated? Let us know →

Get weekly workflows. Subscribe to the newsletter.