360 Secure SkillHub
360 安全技能中心

Event Readiness

核心功能：从库存、定价、流量/内容/客服支持、履约6大维度，检查卖家活动前准备情况，输出就绪结论、核心缺口及分优先级整改方案。典型场景适用于平台促销、品牌活动、季节性大促等流量高峰前的就绪核查。需输入活动类型、时间、核心SKU及各维度准备情况；支持对接工具/API，无数据时用清单模式，标注信息盲区。

leooooooow
leooooooow
热度 79.27
最近更新 2026-05-11 17:33:29
分类：营销依赖：读写文件 / 纯提示词应用场景：市场分析 / 报告撰写 / 工作流 / 任务管理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add event-readiness
Metadata
name
event-readiness
description
Check whether a seller is actually ready for a marketplace event, promo spike, or campaign window before traffic is pushed. Use when the user wants to know if inventory, pricing, creator support, content, service, and fulfillment are ready enough to participate without wasting the event.

Event Readiness

Check readiness before the team burns an event with weak preparation.

Skill Card

  • Category: Operations
  • Core problem: Are we ready enough to enter this event window?
  • Best for: Marketplace promos, brand events, seasonal pushes, and campaign spikes
  • Expected input: Event timing + hero SKUs + inventory + pricing + support readiness
  • Expected output: Readiness verdict + gap list + must-fix priorities
  • Creatop handoff: Push critical gaps into launch and campaign prep workflows

Before you run

Ask the user to clarify:

  • event type
  • event date range
  • hero products
  • current inventory situation
  • pricing plan
  • creator / affiliate support
  • content volume readiness
  • customer support coverage
  • fulfillment readiness

If the event is near and the inputs are incomplete, say so explicitly.

Optional tools / APIs

Useful but not required:

  • inventory export
  • SKU list
  • promo plan sheet
  • creator list
  • content calendar
  • fulfillment SLA sheet
  • Google Sheets / CSV

If the user has no exports, continue with checklist mode and mark blind spots.

Workflow

  1. Confirm the event scope.
  2. Review readiness across six areas:
    • inventory
    • pricing
    • traffic support
    • content support
    • customer support
    • fulfillment
  3. Flag critical gaps.
  4. Decide:
    • ready
    • ready with fixes
    • not ready
  5. Produce a must-fix sequence.

Output format

Return in this order:

  1. Readiness verdict
  2. Critical gaps
  3. Must-fix before launch
  4. Nice-to-fix if time allows
  5. Final go / no-go note

Fallback mode

If the user only has partial information:

  • run checklist mode
  • call out unknowns as risk
  • do not mark the event “ready” unless the critical path is reasonably covered

Quality rules

  • Focus on launch failure points first.
  • Distinguish critical gaps from nice-to-have polish.
  • Do not confuse “some assets exist” with true event readiness.
  • Keep the verdict decision-oriented.

License

Copyright (c) 2026 Razestar.

This skill is provided under CC BY-NC-SA 4.0 for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license.

Commercial use requires a separate paid commercial license from Razestar. No trademark rights are granted.