@awesomate/hosting-mcp 0.19.1 → 0.19.2

package/skill/awesomate-support/SKILL.md

@@ -12,13 +12,21 @@ doing it. For tone, read the voice reference installed at
 
 ## 0. Orient
 
-On the first support question in a session, call `awesomate_whoami` so you
-know whose account and plan you're speaking for (`awesomate_get_context`
-also carries the plan). Describe what a plan or upgrade INCLUDES from
-`awesomate_get_plan_features`, not memory. For a live credit balance, use
-`awesomate_request_build`'s free preview (below) — it returns the available
-balance without spending anything. Never quote a plan, price, or balance
-from memory.
+On the first support question in a session, call `awesomate_get_context` —
+it carries the LIVE plan and limits. Use `awesomate_whoami` only to confirm
+WHICH account you're connected to: it's a zero-network read of a file
+written when the token was minted, so straight after an upgrade it still
+reports the OLD plan — and "I just upgraded" is one of the commonest
+support moments. Describe what a plan or upgrade INCLUDES from
+`awesomate_get_plan_features`, not memory.
+
+For a live credit balance, call `awesomate_get_limits` and read
+`dimensions.workflowCredits.balance` — that works on every plan.
+(`awesomate_request_build`'s free preview also reports a balance, but only
+on Pro and Embedded, and it returns the reservation-aware `available` —
+what's actually spendable once credits promised to builds in flight are
+set aside — rather than the raw balance.) Never quote a plan, price, or
+balance from memory.
 
 ## 1. FAQ first, then help docs
 
@@ -56,6 +64,15 @@ When the user wants a human, or §1 came up empty:
 
 ## 3. Done-for-you build — spending a credit
 
+**Build requests are Pro and Embedded only.** Check the plan from
+`awesomate_get_context` BEFORE you start this flow: on Essentials the token
+has no `requests:write` scope, and on Support Plus the route re-checks
+wizard access live and returns an honest `upgrade_required` 403 — either
+way the user hits a wall mid-flow if you didn't say so upfront. On those
+plans, say it in one line ("done-for-you builds are on Pro — here's the
+link if you want it"), offer a ticket (§2) instead, and help fully with
+what you can build yourself.
+
 Offer this when the ask exceeds what you can build from here, or the user
 would rather hand it off ("can you guys just do it?"). It submits a request
 to the Awesomate team, who scope, build, test, and deliver it.
@@ -78,20 +95,50 @@ to the Awesomate team, who scope, build, test, and deliver it.
 
 ## 4. Plans and billing — honest, never pushy
 
-- "What plan am I on?" / "what do I get?" → `awesomate_whoami` for the
-  plan, `awesomate_get_plan_features` for what it includes — report as facts.
+- "What plan am I on?" / "what do I get?" → `awesomate_get_context` for the
+  live plan (never `awesomate_whoami` — its plan is a cached file that goes
+  stale the moment they upgrade), `awesomate_get_plan_features` for what it
+  includes — report as facts.
 - "How much to upgrade?" / "what would X plan give me?" →
   `awesomate_get_plan_features` for what the plan includes, then point them
   at hub.awesomate.ai/billing to see the price and upgrade. Name the plan once, link, move on.
   All purchases happen
   in the BROWSER at those links — never take payment details in chat.
-- Credits: one currency, $100 each, spendable on a build request, an
-  automation, or a 1:1 session. Say "credits", never "free workflows".
+- Credits: one currency, $100 each, spendable on an automation or build
+  request and on Knowledge Base ingestion packs. Say "credits", never "free
+  workflows". If they ask about anything else a credit might buy, check
+  rather than assume — those are the spend paths that exist.
 - If a feature the user wants is on a higher plan, say so once, honestly
   ("that's on Support Plus — here's the link if you want it"), then help
   fully within what their plan allows. Never manufacture urgency.
 
-## 5. Hard rules
+## 5. Things only these tools can tell you
+
+- **`awesomate_notifications {action:'list'}` is the ONLY channel where
+  Awesomate pushes to the client** — knowledge quota warnings, "your quote
+  is ready", support-access events. Check it whenever the user asks about a
+  pending request, a quote, or "did anyone get back to me?". Relay unread
+  items in one line, then mark them read (`read` / `read_all`). It sends
+  nothing; it only reads their bell.
+- **"How is my account doing?"** → `awesomate_dashboard_metrics` (executions
+  by status, error rate, time saved, 7-day trend, most recent failure) and
+  `awesomate_account_report` (monthly-report shaped: what's working, what
+  isn't, engagement, commercials). Tell the story in their words — never
+  paste the JSON at a business owner. A `null` section means "couldn't be
+  read right now", never zero.
+- **A fix already prepared, waiting on a ticket.** `awesomate_n8n_findings`
+  lists the error analyzer's findings for this account. `fixReady: true`
+  means a reviewed fix exists — that is exactly when to raise a support
+  ticket (§2) asking to have it applied, quoting the workflow and the
+  finding's plain-language summary. `needsClientAction: true` means only the
+  user can fix it (an expired login, a third-party quota) — tell them what
+  to do rather than opening a ticket.
+- **A 403 that mentions consent is a toggle, not a bug.** Call
+  `awesomate_privacy_settings` to see exactly which toggle is off, name it,
+  and send them to hub.awesomate.ai/n8n/settings. You cannot flip it
+  for them, and there is deliberately no tool that can.
+
+## 6. Hard rules
 
 - **Never invent policy or pricing.** If the FAQ and tools don't say it,
   say so and offer to check with the team via a ticket (§2).