sales-review

Analyzes restaurant POS sales trends and translates revenue changes into directional insights and next actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Store managers asking "how was this week?" often get raw sales numbers with no interpretation. This Skill turns rocky-regi POS data into a directional read (upward/downward), checks whether the trend is continuous, identifies likely causes, and recommends the next analysis step. ## Core Features & Use Cases - Directional Sales Analysis: Compares current period vs. prior period via get_business_summary, decomposing changes into customer count vs. average spend. - Continuity Detection: When sales trend downward, it iterates up to 3 periods to confirm whether the decline is consecutive, while respecting API rate limits. - Goal Tracking & Insights: Pulls goal progress with pace-based landing estimates and attaches up to 2 warning-level store insights as supporting evidence. - Use Case: A manager asks "今月の目標間に合う?" and receives the direction, week-over-week continuity, contributing factors, and a pointer to the next workflow such as dead-menu tracking or sudden-drop investigation. ## Quick Start Ask "How were sales this week compared to last week, and what should I look at next?"

Frequently Asked Questions about sales-review

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

FAQPage Schema
How do I analyze weekly restaurant sales trends from POS data?▼

Compare the current period against the prior period using get_business_summary, then decompose the change into customer count and average spend. If the direction is downward, repeat for up to three consecutive periods to confirm whether the decline is a sustained trend.

How to check if monthly sales goals will be met?▼

Retrieve active goals with get_goals and fetch progress via get_goal_progress, then apply simple pace proration based on elapsed days. If the data is insufficient or below anonymity thresholds, report that judgment is not yet possible rather than declaring a miss.

Does this sales analysis modify POS data or promotions?▼

No, the workflow is read-only. It only interprets sales data and suggests next steps; execution actions like creating promotions are handed off to separate skills such as seasonal promo swap.

Why does the analysis limit repeated summary calls to three periods?▼

The get_business_summary endpoint enforces rate limits of 5 calls per minute and 100 per day. Iteration is capped at three periods and only runs when the trend is downward, avoiding wasted calls on upward trends.

What does it mean when no store insights are returned?▼

Zero insights means no detection rules matched, not that the store is performing well. The output states "no rule matched" explicitly, and missing cost data is reported as gross margin being undeterminable.