SuperAPI AI Directory

commerce-morning-brief

General & other

View repository

Updated 10-15 21:02

About this skill

Commerce Morning Briefing

Overview

Collects store operation data and consolidates it into a 1-line summary. It is a daily morning routine skill that compresses the manual 30-minute task of checking channel admin dashboards (SmartStore, Coupang Wing, Cafe24, etc.) one by one into a 30-second briefing.

2 SCOPE Modes

SCOPE Trigger Phrase Examples Deliverables
Full Morning Briefing (default) "Make me a morning briefing", "Show me today's store status" 1-line consolidation of 4 areas: orders, inquiries, trends, ROAS
Order Summary Only "Summarize today's orders", "Consolidate new orders", "Orders by channel at a glance" New orders from 3 channels—SmartStore, Cafe24, and I'mweb—plus totals

SCOPE is automatically selected based on the utterance. If it is "morning briefing", it enters the full 4-area mode; if it is "order summary/consolidation", it enters the order summary mode.

Data Sources (Priority)

  1. Connected commerce MCP connector — use it if store data can be queried directly
  2. Channel admin dashboard export files (CSV, Excel) or screenshots attached by the user
  3. Text status pasted by the user (order, inquiry, and ad metrics)

Quality Checklist Summary 1-line summary based on persona tone + confirmation of .md save.


Trigger Keywords

morning briefing, morning brief, store status, yesterday's orders, new inquiries, check ROAS, store dashboard, daily brief, 30-second briefing, today's order summary, consolidate new orders, channel-integrated orders, SmartStore Cafe24 I'mweb, dashboard integration, order totals by channel


Workflow

Input Slots

Slot Required Default Description
Store Data Required None Commerce MCP connector query results, dashboard export files (CSV, Excel), or screenshots
date Optional Yesterday's date (automatic) Reference date for the query (YYYY-MM-DD)
persona_tone Optional Persona default Apply the persona tone configured in CLAUDE.md

Processing Chain

  1. Collect store data (connector query or analysis of attached files/screenshots)
  2. Organize data for 4 areas (orders, inquiries, trends, ROAS) — mark missing areas as "no data"
  3. Generate a 1-line summary by applying the persona tone
  4. Save the result as an .md file

When data is insufficient

If some areas (e.g., ROAS) are missing from the attached data, mark those areas as "No data" and summarize only the remaining areas. If there is no way at all to access store data, guide the user to the list of materials that can be exported from the channel manager (order history, inquiry list, ad report).


Usage examples

Example 1 — Basic call (file attachment)

"Give me this morning's briefing" (attach yesterday's order history, inquiry list, ad report)

첨부 데이터 분석 → 어제 날짜 기준 정리
출력:
[2026-05-11 아침 브리핑]
주문: 신규 32건 (전일 대비 +8%) · 문의: 5건 미답변 · 트렌드: "여름 원피스" 급상승 · ROAS: 3.2
→ morning-brief-20260511.md 저장

Example 2 — Specify a particular date

"Show me last Monday's briefing"

첨부 데이터에서 date: "2026-05-05" 기준 정리
출력: 해당 날짜 주문·문의·트렌드·ROAS 통합 요약

Example 3 — Screenshot input

"This is a SmartStore dashboard screenshot, give me a briefing"

스크린샷에서 수치 추출 → 매장 어제 현황 1줄 요약 → .md 저장

Output format

# [날짜] 아침 브리핑

**주문**: [신규 N건] (전일 대비 ±N%)
**문의**: [미답변 N건] / 전체 N건
**트렌드**: "[키워드]" [상승/하락/유지]
**ROAS**: [N.N]

> [페르소나 톤 적용 1줄 요약]

Save path: 작업_폴더/morning-brief-YYYYMMDD.md


Order summary mode (integrated new orders across channels)

Entered when the user says things like "Summarize today's orders," "Integrate new orders," or "I want to stop switching back and forth between 5 dashboards." It aggregates new orders across the 3 channels SmartStore, Cafe24, and I'mweb and compresses them into 1 line. This is the version that expands the order area of the full morning briefing down to channel-level detail.

Input slots (order summary mode)

Slot Required Default Description
Order data Required None Commerce MCP connector query results, per-channel order history exports (CSV/Excel), or screenshots
channels Optional All channels Specify when querying only particular channels (smartstore, cafe24, imweb)
date Optional Today's date (automatic) Reference date for the query

Processing steps

  1. Collect order data (connector query or analysis of attached files/screenshots)
  2. Organize new orders across the 3 channels — mark missing channels as "No data"
  3. Per-channel + combined aggregation
  4. Generate 1-line integrated summary + save .md

Order summary output format

# [날짜] 채널 통합 신규 주문

| 채널 | 신규 주문 | 금액 |
|------|-----------|------|
| 스마트스토어 | N건 | ₩N,NNN,NNN |
| 카페24 | N건 | ₩N,NNN,NNN |
| 아임웹 | N건 | ₩N,NNN,NNN |
| **합계** | **N건** | **₩N,NNN,NNN** |

> [1줄 요약]: 오늘 3채널 합산 N건, 총 ₩N,NNN,NNN

Save path: 작업_폴더/order-summary-YYYYMMDD.md

Order summary mode usage examples:

"오늘 주문 요약해줘" (채널별 주문 내역 첨부)
→ 스마트스토어 18건 · 카페24 9건 · 아임웹 5건 = 합계 32건 (₩4,820,000) → order-summary-YYYYMMDD.md 저장

Quality checklist

Full morning briefing mode

  • Includes 1-line summary based on persona tone
  • Confirm .md file saved
  • Includes all 4 areas (orders, inquiries, trends, ROAS) (areas without data explicitly marked as "No data")

Order summary mode

  • Includes combined summary across the 3 channels SmartStore + Cafe24 + I'mweb (channels without data explicitly noted)
  • 5 dashboards → 1-line integrated summary format + confirm .md saved

Related skills

  • moai-officer:setup-mcp-connector — Authentication guide for when you want to query store data directly via the connector
  • moai-seller:commerce-integrated-strategy — Strategy development based on briefing/order data

When not to use this skill

  • When external news, market trends, or competitor information is needed → moai-officer:productivity-briefing use
  • If you need new order details by channel → use this skill's order summary mode ("Summarize today's orders")
  • If you need an in-depth report analyzing ad campaign performance → use a separate ad analysis skill
  • If you are trying to query directly through the MCP connector but authentication has not been completed → moai-officer:setup-mcp-connector run first