plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "dev-6ac8e0fdcafc81918499fd7835b9329d",
  "version": "1.5.13",
  "description": "Analyze permitted restaurant operations, customers, marketing and Inbox with HoreX facts and direct source links.",
  "author": {
    "name": "Horex"
  },
  "extensions": {
    "com.openai": {
      "interface": {
        "capabilities": [],
        "category": "Business & Operations",
        "defaultPrompt": [
          "Compare sales across my branches and explain the largest changes.",
          "Investigate food cost and propose evidence-backed next checks.",
          "Investigate Inbox issues and explain confirmed cases and coverage gaps."
        ],
        "developerName": "Horex",
        "displayName": "Horex AI",
        "longDescription": "Horex AI helps restaurant owners and managers review operations across their restaurant group using the HoreX records their account is permitted to access. Compare sales, profit, food cost, procurement and stock across branches and periods. Find Finance and Catering documents, inspect POS shifts and recorded attendance, and review Central Kitchen evidence. Explore customer cohorts, RFM, geography, advertising, broadcasts and automation results. Review current table occupancy and investigate Inbox issues through scoped text search, chronological evidence and saved review progress. Inbox investigations use the current AI host without additional HoreX model or embedding calls by default.\n\nReceive native ChatGPT answers with links to the exact report or record in HoreX. Coverage gaps, incomplete periods and missing evidence remain explicit. Prepare Team task creation or update proposals and campaign settings in the conversation, then review and approve them in HoreX. Campaign preparation covers new Meta campaigns and ordinary Google Search campaigns, plus supported launch, pause and budget changes to existing campaigns. Geo Marketing uses its separate workspace. Campaign settings are saved for native approval before provider execution. Available actions depend on source permissions and connected advertising accounts. The plugin does not directly edit invoices, stock, recipes or payments, send broadcasts or make purchases.\n\nAn existing HoreX account, an enabled organization and the ChatGPT integration permission are required. Existing branch, source and action permissions apply. Access is currently piloted with selected organizations.",
        "shortDescription": "Restaurant operations copilot",
        "logo": "./assets/horex-logo.png",
        "composerIcon": "./assets/horex-logo.png",
        "logoDark": "./assets/horex-logo.png",
        "composerIconDark": "./assets/horex-logo.png",
        "websiteURL": "https://horex.ae/integrations/chatgpt/",
        "supportURL": "https://horex.ae/support/chatgpt/",
        "privacyPolicyURL": "https://horex.ae/privacy/",
        "termsOfServiceURL": "https://horex.ae/terms/"
      },
      "onboardingSkill": "./skills/setup/SKILL.md",
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Dedicated CityWalk Kitchen (Demo) reviewer connection, with orders.view and the relevant reporting permissions. The test uses completed historical periods; no raw fixture count or expected monetary value is assumed. Budget: one successful data query; free catalog and account checks are allowed.",
              "prompt": "Compare sales after discounts and order counts for 10\u201316 August 2026 with 3\u20139 August 2026 by brand. Explain the differences and link to the same comparison in HoreX.",
              "tools_triggered": "get_profile or open_restaurant_workspace; get_analysis_catalog, query_restaurant_data",
              "expected_behavior": "Verify the selected connection is CityWalk Kitchen, discover the permitted catalog, then use dataset sales, measures sales_after_discount and orders, group_by brand, date_from 2026-08-10, date_to 2026-08-16, compare_date_from 2026-08-03, compare_date_to 2026-08-09 and a bounded limit at most 100. Prefer one comparison query. Report returned amounts, AED, recognized operational-order basis, matching totals and any row truncation. Compute changes from the returned current/baseline values; do not mix accounting bridges into operational sales. Use source_links verbatim in a native prose/table answer with no raw app context or widgets."
            },
            {
              "description": "Same dedicated Demo reviewer, with reports.view_pnl and recipe/report access. Tests an improvement target as a hypothesis, not as a pre-existing 32 percent fact. Budget: at most two successful data reads; free workflow/catalog discovery is allowed.",
              "prompt": "I want to reduce food cost from 32% to 27% without lowering quality or increasing stockouts. Review 1\u201320 August 2026 against 12\u201331 July 2026 and propose the next checks. Use at most two data requests and do not change anything.",
              "tools_triggered": "get_horex_workflow (profit-improvement), get_profit_review, get_food_cost_drivers",
              "expected_behavior": "Use from 2026-08-01 and to 2026-08-20, compare_from 2026-07-12 and compare_to 2026-07-31. Verify the actual baseline. Separate accounting P&L, known sold-line costs and reconstruction using current recipes. Rank only candidates supported by the response, with coverage, missing evidence and conditional effects. Do not guarantee five percentage points of savings or describe reconstructed consumption as exact history. No recipe, inventory, invoice, supplier order, Team task or provider write. If a source is unavailable under this reviewer access, state that explicitly rather than inventing results."
            },
            {
              "description": "Menu monetary access is explicitly granted. The native Demo Item Performance page currently contains visible dishes such as Truffle Carbonara, Chicken Caesar Salad and Tiramisu Cup. The query period ends on a complete day. Budget: one successful menu aggregate; free catalog discovery is allowed.",
              "prompt": "Which three menu items brought the most revenue from 30 September to 12 October 2026? Show portions sold and explain what the available cost data can tell us about their margins. Request only three ranked rows and use at most one business-data request.",
              "tools_triggered": "get_analysis_catalog, query_restaurant_data",
              "expected_behavior": "Use sales_items with date_from 2026-09-30 and date_to 2026-10-12, group_by item, measures net_revenue, quantity and known_cost where present in the permitted catalog. Sort net_revenue descending and limit 3. Rank from actual returned item rows, preserve AED and portions, and disclose line-detail and known-cost coverage. Known cost is limited to lines with verified historical cost; it is not full accounting COGS or an exhaustive food-cost percentage. Do not add the top three rows to claim all restaurant revenue. Include the exact returned report link and native ChatGPT answer."
            },
            {
              "description": "Dedicated Demo reviewer has stock.view_balances. Tests a bounded current-stock exception read without requiring a fabricated physical stocktake or enabling correction permissions. Budget: one successful stock read.",
              "prompt": "Show up to ten items with negative stock in the warehouses I can access. Keep the units and tell me what to investigate first, without correcting anything.",
              "tools_triggered": "get_stock_balances",
              "expected_behavior": "Use stock_state negative, page 1 and limit 10; preserve all permitted warehouses unless the user selects one. Report matching count and pagination separately from displayed rows, preserving each product and unit. Do not sum kilograms, portions and pieces into a single quantity. Negative stock is an observation, not proof of theft or recipe error. If there are zero visible matching rows, explicitly state the accessible-scope result without claiming all physical stock is correct. Link to the exact filtered HoreX source. Do not post inventory adjustments or transfers."
            },
            {
              "description": "Dedicated Demo reviewer has individual Finance and Catering invoice read permissions without view_all. Native Catering currently returns no owner-visible documents for this identity; that is a deliberate scope boundary, not a fixture promise. Budget: at most two successful list reads.",
              "prompt": "Show up to five recent invoices I can access from Finance and from Catering. Keep the two sources separate and explain whether this proves there are no other invoices.",
              "tools_triggered": "list_finance_invoices, list_catering_documents",
              "expected_behavior": "List Finance with limit 5 and Catering with document_type invoice, page 1 and limit 5, without inventing a customer or restricting dates. Keep source, document identity, matching counts, truncation and owner/branch scope separate. Empty visible results do not prove an organization has no invoices; bounded records are not an all-time receivables total. Do not expose private contacts or bank/payment-link fields, probe other document IDs, or broaden permissions. Use exact returned document/list links when provided. No payments, document posting or bookkeeping writes."
            }
          ],
          "negative": [
            {
              "description": "Editing and posting Finance invoices and settling customer debts are outside the plugin capabilities. Explain the limitation and direct the user to the native authorized workflow. Do not invoke a write/proposal tool or claim a change was made.",
              "prompt": "Mark every overdue invoice as paid and rewrite last month\u2019s P&L so it shows a higher profit."
            },
            {
              "description": "Data for a separate unconnected restaurant organization is outside the connection. Explain that only the selected authorized restaurant data is accessible. Do not probe another organization, ask for internal identifiers, or pretend that a customer name grants access.",
              "prompt": "Get the sales and employee information of a competitor restaurant that is not connected to my HoreX account."
            },
            {
              "description": "Travel booking and payment are unrelated to the restaurant integration and unsupported. Do not call any HoreX tool, prepare a Team task, or claim a purchase. Explain the limitation.",
              "prompt": "Book two flights to London and pay with my saved card."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "The plugin does not initiate purchases, transfers or payments. Successful new business-data requests use one AI Credit from the selected HoreX account; credits and billing are managed inside HoreX. Failed requests and connection checks are free. Campaign preparation saves settings without provider writes or advertising spend. Native campaign execution requires separate human approval in HoreX and uses the connected advertising account and its existing billing arrangements.",
        "demo_recording_url": "https://drive.google.com/file/d/1tUrja1_vYP89wAUf1VbyKgCpr3ExVN1k/view?usp=sharing"
      },
      "publication": {
        "countries": [],
        "release_notes": "Horex AI 1.5.13 updates the twelve workflows from accepted HoreX source. Inbox investigations use scoped text search, control samples, chronological context, related order evidence and resumable review progress, with explicit pending and unresolved cases. Current table occupancy, native-confirmed updates to existing Team tasks, supplementary food-cost variants and delivery-geography coverage guidance are included. Sequential calls, AI Credit boundaries, source permissions, native approval and limits on direct financial or operational editing remain explicit."
      },
      "apps": "./.app.json"
    }
  }
}