Ecommerce Pulse Board

Synthesize ecommerce operational health across channels, inventory, marketing efficiency, customer metrics, and fulfillment into a single operator pulse brie...

Security Scan

The skill's code and instructions align with its stated purpose: it produces heuristic ecommerce pulse briefs from user-provided notes, does not request credentials, and contains no install or network calls.

Purpose & Capability

The name/description say the skill synthesizes ecommerce health from user-provided KPI notes (no live integrations). The code and tests only parse input text, detect windows/channels/pillars, and render a markdown brief. No credentials, platform APIs, or unrelated binaries are requested.

Instruction Scope

SKILL.md explicitly requires user-provided KPI notes and forbids live analytics/ERP access or fabricating KPI values. The handler implements keyword-based detection and builds summary sections; it references only user input and internal heuristics. I found no instructions to read unrelated files, environment variables, or to transmit data externally.

Install Mechanism

There is no install spec (instruction-only workflow plus small local Python handler). Nothing is downloaded or written by an installer; risk from install mechanisms is minimal.

Credentials

The skill requires no environment variables, credentials, or config paths. The requested scope (none) is proportional to the stated purpose of producing a heuristic brief from provided notes.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent system presence. Autonomous model invocation is allowed (platform default) but not combined with broad credentials or other red flags.

Assessment

This skill appears coherent and self-contained: it builds a markdown pulse brief from whatever KPI text you paste. Before installing, remember: (1) do not paste sensitive secrets or full PII into the prompt — the skill uses your input to generate the brief; (2) outputs are heuristic and may infer or default when data is partial, so verify any operational or financial action with source systems before acting; (3) if you want stronger guarantees, review the full handler.py locally (it is small) to confirm it contains no network calls or logging you don't want.

Overview

Use this skill to generate a structured operational pulse brief from rough KPI notes, multi-channel context, and operational observations. It applies a built-in ecommerce health framework across five pillars — traffic, conversion, inventory, marketing efficiency, and fulfillment — to surface signal, risk, and priority action items in one readable digest.

This MVP is heuristic. It does not connect to live analytics platforms, ad dashboards, ERPs, or order management systems. It relies on the user's provided KPI notes, channel mix, and operational context.

Trigger

Use this skill when the user wants a:

• daily or weekly operational pulse check across all ecommerce channels
• monthly executive health brief for a brand or store
• post-campaign operational debrief covering inventory, fulfillment, and margin side effects
• rapid health scan before a board meeting, investor update, or team sync
• structured digest when data is partial or non-standard across channels

Example prompts

• "Give me a pulse check on our Shopify and Amazon operations this week"
• "Create a monthly ecommerce health brief from these KPI notes"
• "Run a quick health scan before our investor update"
• "What should our ops team be paying attention to this week?"

Workflow

1. Capture the review window, channels in scope, and the user's main concern or question.
2. Organize KPI notes and operational observations into the five health pillars.
3. Score each pillar (green / yellow / red) with supporting evidence.
4. Surface the top 3 priority signals and recommended owner actions.
5. Return a markdown pulse brief.

Inputs

The user can provide any mix of:

• review window: daily, weekly, monthly, post-campaign, quarterly
• channel mix: Shopify, Amazon, TikTok Shop, JD, Taobao, WeChat, Weidian, other
• KPI notes: GMV, net revenue, orders, AOV, refund rate, ROAS, CPC, inventory levels, stockout SKUs
• operational context: staffing, warehouse delays, campaign context, product launch
• main concern or question: e.g., "Are we on track for Q2 targets?" or "Did the promo hurt margin?"

Outputs

Return a markdown pulse brief with:

• pulse summary: overall health score, review window, and main story in 3 sentences
• pillar health grid: traffic, conversion, inventory, marketing efficiency, fulfillment — each scored and annotated
• signal of the week: the single most important observation and what it means
• risk watchlist: top 2-3 at-risk areas with likely cause and recommended owner
• priority actions: 3-5 specific, operator-ready next steps with owner assignment
• channel spotlight: per-channel pulse for each channel in scope
• data quality note: what was confirmed, what was inferred, and what needs verification

Safety

• No live analytics, ad platform, ERP, or OMS access.
• Health scores are directional unless comprehensive data is provided.
• Do not fabricate KPI values or claim live data access.
• Strategic budget, pricing, and inventory decisions remain human-approved.

Best-fit Scenarios

• founders and ops leads who need a quick weekly or monthly health check without dashboard tooling
• teams with fragmented data across platforms that need a single structured digest
• post-campaign or seasonal debriefs that need an operational lens beyond pure media metrics

Not Ideal For

• real-time operational monitoring, automated alerting, or live KPI dashboards
• enterprises requiring formal financial reporting or audit-grade data reconciliation
• situations where data is so incomplete that any health score would be misleading

Acceptance Criteria

• Return markdown text.
• Include pillar health grid, signal of the week, risk watchlist, and priority actions.
• Cover at least 3 of the 5 health pillars.
• Make data-quality assumptions explicit when inputs are partial.
• Keep the brief practical for founders, ops leads, and channel managers.