bridge-drop-winback

Diagnoses single-store sales drops and chains churn analysis into win-back LINE coupon campaigns.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Techno-Rocky/rocky-regi-plugins --skill bridge-drop-winback-techno-rocky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bridge-drop-winback
Source: https://github.com/Techno-Rocky/rocky-regi-plugins/tree/main/plugins/rocky-ops/skills/bridge-drop-winback
Command: npx skills add https://github.com/Techno-Rocky/rocky-regi-plugins --skill bridge-drop-winback-techno-rocky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a store manager or HQ notices a sudden sales drop at one location, it is easy to overreact to noise or launch untargeted promotions. This Skill first verifies whether the drop is a genuine anomaly against an expected range, then attributes the cause using in-store data, identifies churning customer segments via RFM, and connects the diagnosis to a holdout-measured win-back coupon campaign. ## Core Features & Use Cases - False-alarm gate: Compares actual sales against the expected range (mean±std) from similar business days and stops the workflow when the drop is within range or the sample size is insufficient. - Cause attribution: Cross-references cancellations, hourly heatmaps, menu engineering quadrants, and survey feedback to determine whether the drop is operational or demand-driven. - Churn-to-winback chain: Extracts real churning segments via RFM, generates SSR hypotheses about why they left, prepares approved visuals, and sends LINE coupons with mandatory holdout groups for ROI measurement. - Use Case: A manager asks "Did Store A's sales drop yesterday?" The Skill confirms the drop is outside the expected range, finds dinner-hour Star items collapsed, identifies 200 churning dinner regulars, and prepares a holdout-measured win-back coupon pending owner approval. ## Quick Start Ask the assistant to check whether yesterday's sales drop at a specific store is a real anomaly and, if so, diagnose the cause and prepare a win-back campaign for churning customers.

Frequently Asked Questions about bridge-drop-winback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a sudden sales drop at one restaurant store?▼

Start by comparing actual sales against the expected range from similar business days using get_similar_business_days. If the drop falls outside the range, attribute the cause using cancellation patterns, hourly heatmaps, menu engineering quadrants, and survey feedback before planning any response.

How to avoid false alarms when monitoring daily store sales?▼

Use an expected-range check based on similar business days (mean±std) with a confidence score. If actual results fall within the range or the sample size is insufficient (confidence low), declare it non-anomalous and stop without launching further analysis or campaigns.

Can I send win-back coupons to churning customers via LINE?▼

Yes, after extracting churn-risk segments via RFM analysis, preview the segment reach with preview_line_segment, check remaining quota with get_line_messaging_quota, and create a coupon scenario with a mandatory holdout group. Owner approval is required before any send executes.

Why does the skill refuse to run SSR churn analysis without RFM data?▼

SSR hypotheses must be conditioned on real customer attributes like RFM bucket, visit frequency, and spending band. Running persona simulations on imaginary churning customers produces unreliable hypotheses, so actual RFM extraction is a mandatory prerequisite step.

What happens when the embedding or image generation connector is not connected?▼

Without an embedding connector, SSR outputs are treated as qualitative model estimates rather than measured-looking decimal scores. Without an image generation connector, the skill stops at presenting prompt candidates instead of producing win-back visuals.

Does this skill run Meta Ads retargeting or external portal checks?▼

No. Meta Ads MCP is not connected, so retargeting is left to owner-driven manual operation. External portal crawling is deferred due to BOT terms-of-service risk and is never invoked from this skill.