Render the cards and charts inline instead of treating them as optional

skills/category-monitor/SKILL.md

@@ -237,13 +237,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and a
-seller-tier chart; otherwise fall back to the markdown tables plus text cards.
-Never block on visuals. The snapshot table (and the comparison table, when
-present) always render as markdown in the response text, and the downloadable
-file mirrors what is shown.
-
-When inline visuals are available:
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Cards:** estimated sales, number of products and number of active sellers,
   plus the concentration figure as a value or small bar — labelled
@@ -263,8 +278,8 @@ When inline visuals are available:
   simple line across those periods.
 
 Presentation rules: column headers are words, never a bare "Δ" symbol; show the
-color-dot legend only when those dots appear (the comparison table); render a
-chart only when the data supports it.
+color-dot legend only when those dots appear (the comparison table); and the
+downloadable file mirrors what is shown.
 
 ## Notes & Guardrails
 

skills/category-opportunity-index/SKILL.md

@@ -259,14 +259,28 @@ There is no JoomPulse category dashboard link for Shopee, so never invent one.
 
 ## Visualization
 
-When the client can render inline visuals, present the opportunity badge,
-metric cards, and the appropriate charts; otherwise fall back to a markdown
-table plus text cards. Never block on visuals — if the rich-visual path is
-unavailable for any reason, render the markdown fallback. The monthly indicators
-table always renders as markdown in the response text, on every surface, and the
-⚠️ estimate disclaimer always stays in the text.
-
-When inline visuals are available, present in one panel:
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Opportunity badge** at the top: Alta 🟢 / Média 🟡 / Baixa 🔴 (show `—` if
   missing), with the marketplace and the reference month.
@@ -299,14 +313,6 @@ or "Era | Agora"), never a bare "Δ" symbol. Show a 🟢/🔴/🆕 legend only o
 where those symbols actually appear — never on a first or baseline run. Render a
 chart only when the underlying data supports it, and skip it otherwise.
 
-On a text-only surface, render the same information as markdown and text: the
-badge as a heading line, the five metrics as the indicators table or text cards,
-the trend as one short line describing the ~12-month direction (Mercado Livre
-only, and only when there are at least about six months of history), the
-concentration as a text value under its own marketplace's label (for example
-`Monopolização: 38% (baixa — bom)` on Mercado Livre), and the seasonality as a
-text chip line on Mercado Livre only.
-
 ## Notes & Guardrails
 
 The seller should never see a system or stack error — only a friendly next step.

skills/fast-growing-international-products/SKILL.md

@@ -210,12 +210,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and a chart;
-otherwise fall back to the markdown table plus text cards. Never block on visuals.
-The product table always renders as markdown, on every surface, and the ⚠️
-disclaimer always stays in the text.
-
-When inline visuals are available:
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Three cards:** number of products in the shortlist (top-N), number of distinct
   categories represented, and average ticket.
@@ -225,10 +241,10 @@ When inline visuals are available:
   the most fast-growing international products. Render charts only when there are
   enough items (skip under about four).
 
-Presentation rules: render a chart only when the data supports it; any change
-column uses a word header, never a bare "Δ". If you show Mercado Livre seller
-medals as colored chips, use the standard palette. On Shopee there are no medals
-— write the shop tier as plain text and never colour it as a rung on a ladder.
+Presentation rules: any change column uses a word header, never a bare "Δ". If
+you show Mercado Livre seller medals as colored chips, use the standard palette.
+On Shopee there are no medals — write the shop tier as plain text and never
+colour it as a rung on a ladder.
 
 ## Notes & Guardrails
 

skills/growing-leaf-category-tracker/SKILL.md

@@ -190,12 +190,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and a chart;
-otherwise fall back to the markdown table plus text cards. Never block on visuals.
-The ranking table always renders as markdown in the response text, on every
-surface, and the ⚠️ disclaimer always stays in the text.
-
-When inline visuals are available:
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Three cards:** number of growing niches found, the single fastest-growing
   niche (name + growth %), and the average growth across the shortlist.

skills/high-demand-low-quality-finder/SKILL.md

@@ -238,10 +238,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and a chart on top
-of the markdown table — never instead of it. The product table always renders as
-markdown. Otherwise, fall back to plain text: the cards as text lines and the
-table as markdown, with no chart.
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 **Metric cards (three):**
 

skills/ml-product-analysis/SKILL.md

@@ -207,7 +207,7 @@ must belong to the same marketplace.
 
 Build a clean search query from the title or photo description, plus a broadened
 fallback query. On Shopee, titles mix Portuguese, English and Chinese, so prepare
-**short tokens in both languages** instead of one long phrase.
+**short terms in both languages** instead of one long phrase.
 
 ### Step 2 — Find analogs
 
@@ -220,7 +220,7 @@ Both the keyword and photo paths feed the same analog pipeline:
      For the photo route, the image-search results play this role.
    - **Shopee:** there is **no image search and no search by meaning**.
      Comparables come from the subject's own category plus a title search — and
-     because titles mix Portuguese, English and Chinese, search **short tokens in
+     because titles mix Portuguese, English and Chinese, search **short terms in
      both languages** rather than one long phrase, then merge the hits.
 2. **Augment when recall is thin.** Optionally widen the candidate set using
    category and keyword search, or constrain to the subject's category. On Shopee,
@@ -341,7 +341,7 @@ The seller should never see a system or stack error — only a friendly next ste
   the seller to confirm.
 - **Search returns nothing:** an empty result for a niche or non-pt-BR query is
   normal — retry once with an English or broadened query, then move on. On Shopee,
-  also try short tokens in the other language before giving up. If search is
+  also try short terms in the other language before giving up. If search is
   temporarily unavailable, say so briefly and rely on the other data.
 - **No catalogue or buy-box on Shopee:** never present catalogue status, a buy-box
   winner, a buy-box price or a seller count for a Shopee item, and never map a

skills/new-growing-products-in-category/SKILL.md

@@ -232,11 +232,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and, when the
-data supports it, a bar chart above the markdown table; otherwise present a
-short markdown cards block (or a tiny two-column Métrica | Valor table) plus
-text. **The product table always renders as markdown**, never inside a widget —
-it is the main deliverable.
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Summary cards** over the surviving listings:
   - **Produtos novos encontrados** — how many listings survived the filters.

skills/popular-international-products/SKILL.md

@@ -201,12 +201,28 @@ Shopee:
 
 ## Visualization
 
-When the client can render inline visuals, present metric cards and a chart;
-otherwise fall back to the markdown table plus text cards. Never block on visuals.
-The product table always renders as markdown, on every surface, and the ⚠️
-disclaimer always stays in the text.
-
-When inline visuals are available:
+**Render the visuals every time the data supports them.** As soon as the analysis
+is done, present the cards and charts described below as a **self-contained visual
+panel** — an artifact where the client renders artifacts, an inline widget where
+it renders widgets. Do not ask permission first, do not describe the panel instead
+of drawing it, and do not offer it as an optional extra: the cards and charts are
+part of the answer, not a follow-up.
+
+- **Order:** the cards first, then the charts, then the written read.
+- **The data table always stays markdown in the response text**, never inside the
+  panel — the panel carries cards and charts only.
+- **The estimate disclaimer always stays in the response text** as well.
+- **Skip an individual chart when its own data threshold is not met** (each
+  threshold is stated below): a chart nobody can read is worse than no chart.
+  Skipping one chart never means skipping the panel.
+- **Only the cards and charts specified below.** Do not invent extra ones, and do
+  not promote a categorical value to a bar — a chip or plain text is the honest
+  rendering for it.
+- **If no visual surface is available at all**, fall back to the markdown table
+  plus the same figures written as text cards. Never block on visuals, and never
+  leave the answer without its numbers.
+
+The panel contains:
 
 - **Three cards:** number of international products found, total estimated sales
   over the window in use — weekly on Mercado Livre, 30 days on Shopee — and

skills/pulse-find-exact-same-product/SKILL.md

@@ -10,7 +10,7 @@ description: >
   o mesmo produto", "anúncios duplicados", "esse produto já existe na Shopee",
   "procurar esse item na Shopee". Ask which marketplace when unclear; never mix
   the two. On Mercado Livre the shared catalogue anchors a match; Shopee has no
-  shared catalogue, so matching is a short-token title search confirmed by
+  shared catalogue, so matching is a title search on short terms, confirmed by
   brand, category and a plausible price band, and photo search is unsupported
   there.
 ---
@@ -147,10 +147,10 @@ numbers.
   widen to a title search inside the category if that set is thin.
 - **Shopee:** title search is a **literal substring match**, and item titles mix
   Portuguese, English and Chinese. So:
-  - search several **short tokens** instead of one long precise phrase — a long
+  - search several **short terms** instead of one long precise phrase — a long
     phrase typically returns nothing at all;
-  - try both the Portuguese and the English wording of the same token;
-  - **scope the search to a category**, because a short generic token on its own
+  - try both the Portuguese and the English wording of the same term;
+  - **scope the search to a category**, because a short generic term on its own
     comes back full of unrelated bundles and accessories.
 - Prefer a compact candidate set first, then broaden only when recall is clearly
   too low.
@@ -225,11 +225,11 @@ enough. Empty field → `—`; never guess or fabricate.
   whether a Mercado Livre product is also on Shopee, run the search twice and
   report the two sides separately.
 - **No image-similarity search on Shopee:** say so in one short sentence and
-  offer the token search based on your own reading of the photo instead. Never
+  offer a term search based on your own reading of the photo instead. Never
   imply a photo match was performed.
 - **Nothing found on Shopee:** an empty result is a floor, not a verdict —
   coverage includes only items with at least one lifetime sale, and a literal
-  title search misses the wordings you did not try. Offer to try other tokens
+  title search misses the wordings you did not try. Offer to try other terms
   or another category.
 - **Market data temporarily unavailable:** retry once quietly; if it is still
   down, say market data is temporarily unavailable and to try again shortly.