# Module 12: Skills, Schedules, and Automation
## Demo: A Real SKILL.md File

This is a working example of a Claude skill. Show it on screen. Walk through each section. Then have participants build their own.

---

## Example: Weekly Sales Report Skill

```markdown
# Weekly Sales Report Generator

Generate a formatted weekly sales report from CRM export data.

## What this skill does

When activated, this skill:
1. Reads the most recent CSV export from the sales CRM
2. Calculates key metrics: total revenue, deals closed, pipeline movement, rep performance
3. Compares to the same week last year and to target
4. Produces a formatted report ready to send to the VP of Sales

## Activation

Use this skill when the user says anything like:
- "Generate the weekly sales report"
- "Run the sales numbers for this week"
- "Prep the Friday sales update"

## Required inputs

- A CSV file with columns: date, rep, customer, product, amount, stage
- The file should be in the user's selected folder
- If no file is found, ask the user to export from the CRM first

## Output format

Produce a markdown report with these sections:

### 1. Week at a Glance
- Total revenue closed this week
- Number of deals closed
- Average deal size
- Comparison to same week last year (if prior year data available)

### 2. Rep Performance
- Table: Rep | Deals | Revenue | % of Target
- Flag any rep below 80% of weekly target
- Flag any rep above 120% (call out the win)

### 3. Pipeline Movement
- New opportunities added this week
- Opportunities that advanced stage
- Opportunities that went cold (no activity in 14+ days)

### 4. Notable Deals
- Largest deal closed this week
- Largest deal lost this week
- Any deal over $50K that changed stage

### 5. Forecast Impact
- How this week's closes affect the monthly forecast
- Remaining gap to monthly target

## Constraints

- Do not fabricate data. If a metric can't be calculated from the available data, say so.
- Round currency to the nearest dollar. Round percentages to one decimal.
- The tone should be factual and direct. This is a working document, not a presentation.
- If data quality issues are found (blanks, duplicates, impossible values), flag them in a "Data Notes" section at the end.

## Example interaction

User: "Run the weekly sales report"
Skill: [Reads CSV from folder] → [Calculates metrics] → [Produces formatted report]
User: "Can you also break it down by product line?"
Skill: [Adds product-level breakdown to the report]
```

---

## Live Demo: Building a Skill

Walk through building a skill from scratch in Claude Cowork. The steps:

1. Ask Cowork: "Help me create a skill for [task]"
2. Cowork will ask clarifying questions about what the skill should do
3. It will produce a SKILL.md file
4. Test it: invoke the skill and see if it works
5. Iterate: "The output needs to also include [X]" or "Change the format to [Y]"

**Suggested skill for the room to build together:**
"A skill that takes meeting notes and produces: (1) a clean summary, (2) action items with owners and due dates, (3) a follow-up email to attendees."

---

## Cron Expressions Reference

Show this table when explaining scheduled tasks.

| Expression | Meaning |
|---|---|
| `0 9 * * 1-5` | Every weekday at 9:00 AM |
| `0 8 * * 1` | Every Monday at 8:00 AM |
| `30 17 * * 5` | Every Friday at 5:30 PM |
| `0 0 1 * *` | First day of every month at midnight |
| `0 6 * * *` | Every day at 6:00 AM |
| `0 9 1,15 * *` | 1st and 15th of each month at 9:00 AM |

**Example: Schedule the weekly sales report**

```
Create a scheduled task called "weekly-sales-report" that runs every
Friday at 4:00 PM. It should:
1. Read the latest CRM export from my Sales folder
2. Run the weekly sales report skill
3. Save the report as "sales-report-[date].md" in the Reports folder
```

This produces a cron-scheduled task that runs without human intervention. The report is waiting in the folder when you arrive Monday morning.

---

## Exercise: Build and Schedule

1. Each participant picks a recurring task they do at least weekly.
2. They build a skill for it (15 minutes with Claude Cowork).
3. They write the cron expression to schedule it (5 minutes).
4. They present: "This is what I built, this is when it runs, this is how much time it saves." (2 minutes each)