Token导航 LogoToken导航TokenDH.com
开发只读clawhub未标认证来源可访问clear审计通过

promo-traffic-stress-monitor促销流量压力监控器

Agent Skill

promo-traffic-stress-monitor 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

6,629

周安装

279

GitHub Stars

公开资料未说明

下载量

2,321
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:promo-traffic-stress-monitor(促销流量压力监控器)
来源仓库:https://github.com/rijoyai/promo-traffic-stress-monitor
安装命令:
openclaw skills install promo-traffic-stress-monitor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install promo-traffic-stress-monitor

简介

实时监控促销期间流量与转化数据,优化广告投放策略。

  • 适用于大促前4小时的关键指标跟踪与动态调整。
  • 支持补货优先级与流量分配决策,提升销售效率。
  • 安装命令为 openclaw skills install promo-traffic-stress-monitor。
  • 需确保数据接口稳定性,避免监控盲区。

SKILL.md

name
promo-traffic-stress-monitor
description
Monitor traffic efficiency and conversion load during major promos (Black Friday, Cyber Monday, Christmas peaks, flash sales) and advise dynamic ad spend, restock, and traffic allocation. Use in the first ~4 hours after a promo goes live, when ROI drops below breakeven during a sale, when hero SKUs sell out instantly, when the user mentions scaling or cutting ads mid-campaign, server or checkout strain, or "traffic is huge but orders aren't." Steps implied: real-time (or latest) traffic → conversion efficiency → if strong, recommend scaling spend or shifting budget to winners; if weak, recommend landing-page and funnel checks before spend. Also trigger on stockouts under load, CAC spike during promos, or reallocating budget between campaigns. Do NOT use for evergreen SEO-only plans with no live promo window, or pure creative briefs without performance or inventory context.
compatibility
required
[]

Promo traffic stress monitor

You support live promo operations: traffic scale → conversion load → restock and traffic split decisions so merchants don’t overpay for broken funnels or underfund winners.

When to lean in (use when)

  • First ~4 hours after promo start — baseline efficiency vs plan.
  • ROI below breakeven during the event — pause or fix before burning budget.
  • Instant sellouts on key SKUs — restock + traffic reallocation (don’t keep pushing OOS landers).

Core workflow (always in order)

  1. Get real-time (or best available) traffic — Sessions, clicks, spend, impressions by channel/campaign; note lag (analytics vs ads manager).
  2. Calculate conversion efficiency — Session→order or click→order, AOV, ROAS or MER vs breakeven ROAS; compare to pre-promo baseline or same hour prior day.
  3. Branch

- Efficiency high (ROAS above target, CVR up, inventory OK) → Scale or reallocate — increase budget on winning campaigns/audiences; shift spend from laggards; cap only if ops risk. - Efficiency low (CVR collapse, ROAS below breakeven) → Do not scaleLanding page / checkout checklist first (speed, price match, stock message, mobile, payment errors); then small test spend if fixed.

Restock & traffic allocation (mandatory when OOS mentioned)

  • Pause or swap ads pointing to OOS PDPs; route to category / substitute SKU if strategy allows.
  • Restock priority — ETA + which channels to hold until inventory lands.
  • Traffic allocation table — where to cut vs add (by campaign or SKU).

Mandatory output shapes

A) Efficiency snapshot (every full run)

WindowTraffic (sessions or clicks)OrdersCVRSpendROAS / MERvs breakeven
First 4h (or user window)above / below

Use placeholders if data not provided; state what to pull from which dashboard.

B) Action matrix

SignalInterpretationAd actionNon-ad action
High CVR + ROAS OKDemand healthyScale or reallocate upWatch stock
Low CVR + traffic highFunnel or LanderHold / cut until fixedLander + checkout audit
SKU OOS + ads onWaste + bad UXPause / redirectRestock + swap creative

First-4-hour playbook (explicit)

  • T+0–1h: Confirm tracking, promos firing, no sitewide errors; glance CVR vs baseline.
  • T+1–2h: If ROAS > target and stock fine → +10–30% budget test on top ad set (merchant risk tolerance); if ROAS < breakeven → stop scale, open lander checklist.
  • T+2–4h: Consolidate budget to winners; list any instant sellout SKUs and traffic shift plan.

Landing-page / load checklist (when conversion low)

  • Mobile LCP, hero offer clarity, promo code auto-apply, stock banner, trust badges, payment methods, geo/currency, error rate on checkout.

When NOT to use

  • No promo window and no live metrics ask.
  • Only static brand copy with no traffic or ROI context.

For channel-agnostic thresholds and restock messaging, read references/promo_ops_playbook.md when needed.

Split with other skills

  • Abandoned checkout deep dive → checkout skill.
  • Long-term LTV → loyalty skill.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

78.36%
按下载量换算1,819

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills