204 lines
5.3 KiB
Markdown
204 lines
5.3 KiB
Markdown
---
|
||
name: sales-decision-report
|
||
description: Analyze sales data and produce decision-oriented reports with KPI summaries, anomaly explanation, channel and region analysis, and HTML-ready report structure. Use when the user asks for sales analysis, management dashboards, sales summaries, or decision reports from business data. 中文触发词包括：销售分析、经营分析、销售周报、销售月报、数据决策报告、HTML 报表。
|
||
category: Writing & Reporting
|
||
---
|
||
|
||
# Sales Decision Report
|
||
|
||
## Overview
|
||
|
||
This skill turns sales data into a decision report for operators, managers, and leadership teams.
|
||
|
||
It focuses on:
|
||
- KPI interpretation
|
||
- trend and anomaly analysis
|
||
- region / channel / product comparisons
|
||
- action-oriented reporting
|
||
- HTML-ready report structure for later automation
|
||
|
||
## Quick Start
|
||
|
||
When the user asks for a sales analysis report:
|
||
|
||
1. Confirm the business objective
|
||
2. Confirm the source data and dimensions
|
||
3. Clarify comparison logic and reporting period
|
||
4. Analyze the data into findings, not just tables
|
||
5. Package the result as a structured report, optionally in HTML outline form
|
||
|
||
### 中文任务映射
|
||
- “做销售周报/销售月报” → quick summary 或 standard report
|
||
- “分析一下为什么业绩下滑” → diagnostic analysis
|
||
- “生成一个 HTML 报表结构” → HTML report structure
|
||
- “做经营分析和行动建议” → decision report
|
||
|
||
|
||
## Input Requirements
|
||
|
||
| Field | Required | Description |
|
||
|-------|----------|-------------|
|
||
| business objective | yes | What decision the report should support |
|
||
| reporting period | yes | Daily, weekly, monthly, quarterly, custom |
|
||
| source data | yes | CSV, XLSX, pasted table, dashboard export |
|
||
| dimensions | no | Region, channel, product, team, customer segment |
|
||
| target / benchmark | no | Budget, target, last period, YoY, MoM |
|
||
| key KPIs | no | Revenue, orders, conversion, AOV, repeat rate, returns |
|
||
| audience | no | Sales ops, regional lead, GM, founder |
|
||
| output mode | no | Summary / detailed report / HTML-ready outline |
|
||
|
||
## Workflow Decision Tree
|
||
|
||
### Quick Sales Summary
|
||
Use for short KPI snapshots and headline findings.
|
||
|
||
### Diagnostic Analysis
|
||
Use when the user wants to know why performance moved.
|
||
|
||
### Decision Report
|
||
Use when the user wants recommendations, priorities, and next actions.
|
||
|
||
### HTML Report Structure
|
||
Use when the user explicitly wants an HTML report or a report that will later be automated into HTML.
|
||
|
||
## Instructions
|
||
|
||
### Step 1: Frame the question
|
||
Clarify whether the report is about:
|
||
- performance monitoring
|
||
- problem diagnosis
|
||
- opportunity finding
|
||
- action prioritization
|
||
|
||
### Step 2: Read the data by level
|
||
Review performance across:
|
||
- total performance
|
||
- time trend
|
||
- region
|
||
- channel
|
||
- product or category
|
||
- customer segment
|
||
|
||
Only include dimensions that materially affect the decision.
|
||
|
||
### Step 3: Identify meaningful changes
|
||
Look for:
|
||
- sharp increases or declines
|
||
- missed targets
|
||
- concentration risks
|
||
- outlier regions or channels
|
||
- mix shifts
|
||
- repeatable strengths
|
||
|
||
### Step 4: Turn findings into decisions
|
||
Each important finding should answer:
|
||
- what happened
|
||
- where it happened
|
||
- likely cause
|
||
- what action should follow
|
||
|
||
### Step 5: Prepare report packaging
|
||
If HTML is requested, structure content into sections suitable for cards, tables, and chart blocks.
|
||
|
||
## Output Format
|
||
|
||
### Standard Report
|
||
```markdown
|
||
# [Sales Report Title]
|
||
|
||
## Executive Summary
|
||
[Short performance summary]
|
||
|
||
## Reporting Scope
|
||
- Period:
|
||
- Objective:
|
||
- Audience:
|
||
- Data source:
|
||
|
||
## KPI Snapshot
|
||
| KPI | Current | Target / Comparison | Variance | Comment |
|
||
|-----|---------|---------------------|----------|---------|
|
||
|
||
## Key Findings
|
||
### 1. [Finding]
|
||
- What happened:
|
||
- Why it matters:
|
||
- Likely cause:
|
||
- Recommended action:
|
||
|
||
## Risks and Opportunities
|
||
- [Item]
|
||
|
||
## Recommended Actions
|
||
1. [Action]
|
||
2. [Action]
|
||
```
|
||
|
||
### HTML-ready Outline
|
||
```markdown
|
||
# HTML Report Structure
|
||
|
||
## Page Header
|
||
- Title
|
||
- Period selector
|
||
- Summary badges
|
||
|
||
## Section 1: KPI Cards
|
||
- Revenue
|
||
- Orders
|
||
- Conversion
|
||
- Average order value
|
||
|
||
## Section 2: Trend Analysis
|
||
- Time-series highlights
|
||
- Major inflection points
|
||
|
||
## Section 3: Breakdown Views
|
||
- Region table
|
||
- Channel table
|
||
- Product table
|
||
|
||
## Section 4: Actions
|
||
- Priority actions
|
||
- Owners or next-step suggestions
|
||
```
|
||
|
||
## Quality Checklist
|
||
|
||
Before finalizing, verify:
|
||
- the report supports a clear business decision
|
||
- metrics and benchmarks are labeled correctly
|
||
- anomalies are explained, not just surfaced
|
||
- recommendations follow logically from findings
|
||
- dimensions are not overloaded without purpose
|
||
- HTML output is structured, not just prose copied into sections
|
||
|
||
## Fallback Strategy
|
||
|
||
If data quality is weak:
|
||
- note missing or inconsistent fields
|
||
- avoid overconfident conclusions
|
||
- provide best-effort observations plus a data cleanup list
|
||
|
||
## Related Skills
|
||
|
||
- `skills/xlsx/SKILL.md` - spreadsheet reading, analysis, and output handling
|
||
- `skills/financial-report-generator/SKILL.md` - finance-oriented reporting when the task is more financial than sales-oriented
|
||
- `skills/auto-daily-summary/SKILL.md` - recurring condensed summary outputs
|
||
|
||
## Examples
|
||
|
||
**User**: "根据这份销售表做一个月度经营分析"
|
||
|
||
Expected output:
|
||
- KPI summary
|
||
- channel/region findings
|
||
- anomalies
|
||
- recommended actions
|
||
|
||
**User**: "帮我生成一个销售分析 HTML 报表结构"
|
||
|
||
Expected output:
|
||
- HTML-ready page outline
|
||
- sections for KPI, trends, breakdowns, and action items
|