Claude Code Skills Guide: Teach AI Your Exact Workflow

---
name: daily-report
description: Generate a structured daily work report
---

# Daily Report Generator

## Task
Generate a well-formatted daily report based on work items provided by the user.

## Output Format
1. Completed today
2. Planned for tomorrow
3. Items needing coordination

## Guidelines
- Keep each item under 20 words
- Sort by priority

.claude/
└── skills/
    └── daily-report/
        └── SKILL.md

mkdir -p .claude/skills/finance-report

---
name: finance-report
description: Analyze financial data and generate a monthly report with KPIs, YoY/MoM comparisons, anomaly alerts, and recommendations
---

# Monthly Financial Report Skill

## Overview

Generate a structured monthly financial analysis report from user-provided data.

## Input Requirements

The user should provide the following (as tables, text, or screenshots):
- Current month revenue breakdown
- Current month expense breakdown
- Previous month / same period last year data (for comparison)

## Analysis Framework

### 1. Key Metrics Overview
- Total revenue, total expenses, net profit
- Gross margin, net margin
- Revenue composition by segment

### 2. Year-over-Year and Month-over-Month Analysis
- Compare with previous month (MoM)
- Compare with same period last year (YoY)
- Flag growth/decline percentages

### 3. Anomaly Alerts
- Any single expense exceeding budget by 20%+
- Revenue decline exceeding 10% in any business line
- Profit margins below industry average

### 4. Recommendations
- Provide 2-3 actionable recommendations based on data
- Be specific, not generic

## Output Format

```
# [Month] Financial Analysis Report

## 1. Key Metrics
| Metric | This Month | Last Month | MoM | Last Year | YoY |
|--------|-----------|------------|-----|-----------|-----|
| Revenue | xxx | xxx | +x% | xxx | +x% |
| ... | ... | ... | ... | ... | ... |

## 2. Revenue Structure Analysis
[Charts or descriptions]

## 3. Expense Analysis
[Key expense items analysis]

## 4. Anomaly Alerts
- [Anomaly item 1]
- [Anomaly item 2]

## 5. Recommendations
1. [Specific recommendation 1]
2. [Specific recommendation 2]
```

## Guidelines

- Round all numbers to 2 decimal places
- Use +/- signs for percentage changes
- Highlight anomalies clearly
- Base all recommendations on actual data

mkdir -p .claude/skills/interview-questions

---
name: interview-questions
description: Generate structured interview questions from a job description, covering technical skills, soft skills, and culture fit
---

# Interview Question Generator Skill

## Overview

Automatically generate a structured set of interview questions from a job description (JD) to help interviewers evaluate candidates comprehensively.

## Input Requirements

The user provides:
- Job title
- Job responsibilities
- Requirements/qualifications
- (Optional) Company culture / team characteristics

## Question Generation Framework

### 1. Technical Competency (3-5 questions)

Design questions targeting the core skills listed in the JD.

Format per question:
- The question
- What it assesses
- Key points in an excellent answer

### 2. Project Experience (2-3 questions)

Use the STAR method to evaluate real project experience.

- Situation: What was the context
- Task: What was the assignment
- Action: What did they do
- Result: What was the outcome

### 3. Soft Skills (2-3 questions)

Assess communication, collaboration, and resilience.

### 4. Culture Fit (1-2 questions)

Evaluate alignment with company values and career goals.

## Output Format

```
# [Job Title] Interview Question Sheet

## Section 1: Technical Competency (Weight: 40%)

### Q1: [Question]
- Assesses: xxx
- Strong answer includes: xxx
- Follow-up: xxx

### Q2: [Question]
...

## Section 2: Project Experience (Weight: 30%)

### Q1: Describe a project you led in [relevant domain]
- Assesses: Project management, technical depth
- Follow-ups:
  - What was the biggest challenge?
  - What would you do differently?

## Section 3: Soft Skills (Weight: 20%)

### Q1: [Question]
...

## Section 4: Culture Fit (Weight: 10%)

### Q1: [Question]
...

---
Scoring guide:
- Rate each question 1-5
- Final score = weighted average
- Recommended hire threshold: 3.5+
```

## Guidelines

- Questions must be specific (avoid vague questions like "How would you describe yourself?")
- Always include follow-up directions for the interviewer
- Adjust weights based on role requirements
- Avoid legally prohibited questions (age, marital status, religion, etc.)

mkdir -p .claude/skills/amazon-listing-pro

---
name: amazon-listing-pro
description: Expert in Amazon A9/COSMO/Rufus algorithms. Generate high-converting listing copy based on competitor analysis and keyword data
---

# Amazon Listing Professional Optimization Skill

## Role

You are a Listing optimization expert with deep knowledge of Amazon's algorithms (A9, COSMO, Rufus) and a strong compliance mindset.

## Input Requirements

The user should provide as much of the following as possible (missing data reduces optimization quality):

### Required
1. **Product attribute sheet**: All specific parameters (dimensions, materials, weight, colors, features, etc.)
2. **Target marketplace**: US, EU, Japan, etc.

### Strongly Recommended
3. **Competitor keyword reports**: Traffic source analysis (exported from Helium10, JungleScout, etc.)
4. **ABA keyword data**: Amazon Brand Analytics data for keyword weighting
5. **Competitor listing text**: Copy from top competitors plus Review pros/cons summary

## Workflow

### Step 1: Multi-dimensional Data Analysis

#### 1.1 Rufus Attribute Extraction
Read the product attribute sheet thoroughly and extract all parameters as the **factual foundation** of the Listing. Every claim must be grounded in real attributes -- never fabricate.

#### 1.2 Competitor Landscape Analysis

**Find Parity**:
- Identify selling points that all competitors emphasize
- These are market standards we must cover
- Example: waterproof, durable, eco-friendly materials

**Find Gaps**:
- Spot scenarios that competitors consistently overlook
- Analyze recurring pain points across Reviews
- These are our core differentiation opportunities
- Example: complaints about flimsy packaging, unclear instructions

#### 1.3 COSMO Scene Mapping
Cross-reference competitor keyword reports to identify the real-world usage scenarios customers care about most.

#### 1.4 A9 Keyword Tiering
Based on ABA keyword data, classify keywords into:
- **S-tier**: Top 3 search volume, must appear in the first 80 characters of the title
- **A-tier**: Top 10 search volume, in the title or first bullet point
- **B-tier**: Long-tail keywords, distributed across bullet points and description
- **C-tier**: Synonyms/variants, placed in backend Search Terms

### Step 2: Write the Listing

#### 2.1 Title

**Formula**: [Brand] + [Top ABA keyword] + [Key improvement addressing competitor pain point] + [COSMO scenario] + [Specifications]

**Rules**:
- US marketplace limit: 200 characters, aim for 150-180
- First 80 characters must contain the highest-weight keywords
- Title case (except prepositions)
- No special symbols (hyphens allowed)
- Differentiate from competitors explicitly (e.g., instead of "durable," say "20% thicker double-layer design")

#### 2.2 Bullet Points

**Approach**: 5-point structure that leverages our strengths against common competitor weaknesses.

**Format**: Each bullet starts with an ALL-CAPS phrase header

**Structure**:
- **Point 1 - Pain Point Strike**: Directly address common competitor shortcomings
- **Point 2 - Scene Immersion**: Describe COSMO scenarios competitors underserve
- **Point 3 - Hard Specs**: Reference specific data from the attribute sheet for Rufus
- **Point 4 - Target Audience**: Define ideal users, mention gifting scenarios
- **Point 5 - Trust & Support**: Return policy, brand guarantees

**Length**: 200-250 characters per bullet

#### 2.3 Product Description

**Format**: HTML layout including:
- Brief brand story
- Detailed specifications table
- FAQ section (specifically addressing common competitor negative reviews)

**HTML template**:
```html
<h3>Why Choose [Brand]?</h3>
<p>[Brand differentiation description]</p>

<h3>Specifications</h3>
<ul>
<li><b>Material:</b> [material]</li>
<li><b>Dimensions:</b> [dimensions]</li>
<li><b>Weight:</b> [weight]</li>
</ul>

<h3>FAQ</h3>
<p><b>Q: [Question addressing competitor pain point]?</b></p>
<p>A: [Our solution]</p>
```

#### 2.4 Backend Search Terms

**Rules**:
- Total character count must not exceed 249
- Do not repeat words already used in the title and bullets
- Space-separated, no commas
- Include: synonyms, spelling variants, Spanish keywords (for US marketplace)
- Never include competitor brand names

### Step 3: Compliance Check

**Complete these checks before final output**:

#### 3.1 Promotional Language Check
Scan and remove: Best seller, #1, Top rated, Free shipping, On sale, Limited time, Guarantee, etc.

#### 3.2 Infringement Check
Scan and replace: Competitor brand names, patented terms, unauthorized certifications (e.g., "FDA approved")

#### 3.3 Exaggeration Check
Verify all parameter claims come from the product attribute sheet. Do not fabricate features.

#### 3.4 Amazon Format Rules
- No emojis in listings
- No HTML tags in bullet points (HTML is for Description only)
- No full-width characters

## Output Format

```
# [Product Name] Listing Optimization Plan

## 1. Optimized Title
[Title content]
(Character count: xxx/200)

## 2. Bullet Points

1. [PAINPOINT SOLUTION] [Description]
2. [PERFECT FOR] [Description]
3. [PREMIUM QUALITY] [Description]
4. [IDEAL GIFT] [Description]
5. [WORRY-FREE] [Description]

## 3. Product Description (HTML)
[HTML code]

## 4. Backend Search Terms
[Keyword list]
(Character count: xxx/249)

## 5. Competitor Analysis Insights

### Common Competitor Weaknesses:
1. [Weakness 1]
2. [Weakness 2]
3. [Weakness 3]

### Our Targeted Improvements:
- For weakness 1: [Our solution]
- For weakness 2: [Our solution]
- For weakness 3: [Our solution]

### Keyword Strategy:
- S-tier: [keyword 1], [keyword 2]
- A-tier: [keyword 1], [keyword 2], [keyword 3]
- Key differentiator: [core differentiation point]
```

## Constraints

1. **Factual accuracy**: Never fabricate features not in the product attribute sheet
2. **Compliance first**: Compliance checks have the highest priority; any violation must be corrected
3. **Holistic view**: Learn from all competitors' strengths, avoid their shared weaknesses -- do not copy any single competitor
4. **Data-driven**: All decisions must be grounded in provided data, never assume market conditions

mkdir -p .claude/skills/your-skill-name

---
name: skill-name          # Required, English, use hyphens
description: One-line summary  # Required, tells Claude when to use it
---

# Title

## Overview
What this Skill does

## Input Requirements
What the user needs to provide

## Execution Steps
How to do it

## Output Format
What the result looks like

## Guidelines
What pitfalls to avoid