all-store-health-check

Ranks underperforming stores across a chain using two-pass outlier detection on POS data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Headquarters staff managing multiple restaurant locations need to know which stores to visit today, but querying deep insights for every store wastes API quota and produces noisy, misleading comparisons. This Skill triages all stores with a lightweight first pass, then deep-dives only the true outliers. ## Core Features & Use Cases - Two-pass triage: Runs a light business-summary sweep across all stores, then calls heavy store-insights only for the top N underperformers to protect rate limits. - Range-based outlier detection: Judges performance against each store's similar-business-day range (mean ± std) instead of naive week-over-week percentages, avoiding false alarms from event-driven spikes. - Deterministic scoring and handoff: Ranks stores with a fixed severity/direction formula, separates "no signal" from "insufficient data" pools, and hands off top stores to sales-review or sudden-drop-investigation skills. - Use Case: An HQ manager asks "which stores should I check this week?" and receives a prioritized table with each store's revenue deviation, a one-line hypothesis (traffic vs. ticket vs. menu mix), and one concrete action. ## Quick Start Ask the assistant to run a health check across all stores for this week and list which locations need attention first.

Frequently Asked Questions about all-store-health-check

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

FAQPage Schema
How do I find underperforming stores across multiple restaurant locations?▼

Run a two-pass health check: first collect sales, customer count, and ticket-size direction for every store, then deep-dive only the top outliers with store insights. This produces a priority-ranked table with a hypothesis and action per store.

How to detect store sales drops without false alarms from weekly comparisons?▼

Compare current performance against each store's similar-business-day range (mean ± std) instead of simple week-over-week percentages. Stores with low sample confidence are moved to an undetermined pool rather than flagged as outliers.

Does this health check modify store data or settings?▼

No, it is strictly read-only. It never calls execution-type tools such as price changes, promotions, or inventory updates; any action requires owner confirmation and a separate skill with human approval.

Why does the health check avoid calling insights for every store?▼

Store insight calls are heavy and rate-limited (business summaries are capped at 5 per minute and 100 per day). Restricting deep queries to the top N outliers protects quota and keeps the output focused.

What happens to stores with insufficient sales data?▼

Stores with low-confidence similar-day samples, shallow operating history, or missing cost data are placed in a separate undetermined pool with the reason noted. They are never mislabeled as healthy or underperforming.