portal-sync-deferred

Returns a deferred status and optional diff checklist for external restaurant portal updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Restaurant owners want one source of truth (the POS) to automatically update external portals like Tabelog, Gurunavi, their own website, and Uber Eats with business hours, temporary closures, and course menus. However, most portals prohibit bot-driven automation in their terms of service, so this Skill acts as a guardrail: it clearly reports that automated portal syncing is on hold pending legal review, instead of silently attempting risky DOM automation. ## Core Features & Use Cases - Deferred-status response: When asked to bulk-update external portals, it immediately returns a fixed-format message explaining the hold, the reason (bot-prohibition clauses), and the conditions for resumption. - Manual diff checklist: On request, it compares the POS source-of-truth data (business hours, temporary closures, courses, photos) against portal current values gathered by the owner, producing a checklist for manual updates. - Compliance guardrails: It blocks DOM automation via browser agents, prohibits marketing claims about automatic portal updates, and requires human publish approval before any external reflection. - Use Case: A store manager says "mark all portals as closed tomorrow." The Skill replies that the feature is on hold, then offers a per-portal checklist showing which sites still show old hours so staff can update them by hand. ## Quick Start Ask the assistant to update Tabelog, Gurunavi, and your website with tomorrow's temporary closure, and it will explain the hold and offer a manual diff checklist.

Frequently Asked Questions about portal-sync-deferred

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

FAQPage Schema
How do I sync my restaurant POS data to Tabelog and Gurunavi automatically?▼

Automatic syncing to Tabelog and Gurunavi is currently on hold because these portals prohibit bot-driven automation in their terms of service. The Skill returns a deferred status and can instead produce a manual diff checklist for staff to update by hand.

What is a portal diff checklist for restaurant listings?▼

A portal diff checklist compares your POS source-of-truth values (business hours, temporary closures, courses, photos) against each portal's current values. It lists store name, item, POS value, portal value, and the recommended manual action in a simple table.

Can I update Uber Eats store hours through an official API?▼

Portals with official APIs like Uber Eats are planned as legitimate integration targets, but they are not yet connected. A contract and MCP configuration must be completed before any API-based updates become available.

Why is automated portal updating blocked by terms of service?▼

Major restaurant portals such as Tabelog and Gurunavi prohibit automated bot operations on their management screens. DOM-based auto-input carries terms-of-service risk that outweighs its implementation value, so the feature stays deferred until legal review passes.

What are the limitations of the portal sync feature?▼

It never executes DOM automation, never quotes or interprets legal terms, and never claims integrations that are not connected. Its maximum output while deferred is the hold notice plus an optional manual diff checklist.