joomcode · fiharet34 · Sep 11, 2026
@@ -66,8 +66,11 @@ JoomPulse MCP setup before it can monitor a category.
 - **Read-only.** The skill never writes or modifies anything; it does not store
   the snapshot — the user keeps the downloadable table and brings it back next
   period.
-- **Language:** detect the seller's language and respond in it. Default to
-  pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **The baseline is user-supplied.** Never claim a change without a previous
   table to compare against, and never infer or fabricate one from memory.
 
@@ -180,8 +183,16 @@ an incomplete month.
 
 ## Output
 
-Respond in the seller's language (default pt-BR). Name the marketplace the
-figures came from.
+Respond in the language of the seller's request (default pt-BR). Name the
+marketplace the figures came from.
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 **Snapshot (always):** a markdown table `| Métrica | Valor atual |`, plus a
 downloadable `.csv` / `.xlsx` of the same data.

@@ -21,13 +21,14 @@ description: >
 
 This skill answers a single question for **one** category on **Mercado Livre
 (Brasil) or Shopee Brasil**: is it worth entering? Given a marketplace and a
-category named in free text, it reads that category's **opportunity index** (low,
-medium, or high) and its current monthly market indicators — estimated revenue,
-estimated sales, sellers, listings, and average ticket — then writes a short
-pt-BR summary that interprets the opportunity level together with how
-concentrated the market is and which way it is growing. On Mercado Livre the
-summary can also draw on a year of history and a seasonality read; on Shopee
-neither exists yet, and the report says so plainly instead of guessing.
+category named in free text, it reads that category's **opportunity index**
+(low, medium, or high) and its current monthly market indicators — estimated
+revenue, estimated sales, sellers, listings, and average ticket — then writes a
+short summary, in the language the seller wrote in, that interprets the
+opportunity level together with how concentrated the market is and which way it
+is growing. On Mercado Livre the summary can also draw on a year of history and
+a seasonality read; on Shopee neither exists yet, and the report says so
+plainly instead of guessing.
 
 This is a point-in-time snapshot, not a tracker. To rank the sellers inside a
 category, use the top-sellers-in-category skill. For the trending search terms
@@ -59,8 +60,11 @@ JoomPulse MCP setup before it can report a category's opportunity index.
   marketplace's own rounded sold counters refined with review movement. Use the
   matching disclaimer.
 - **Read-only.** The skill never writes or modifies anything.
-- **Language:** detect the seller's language and respond in it. Default to
-  pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** The seller wants the answer, not a play-by-
   play. If one approach does not return data, switch to another quietly; only if
   every approach fails do you say one short, friendly sentence. Never fill gaps
@@ -173,13 +177,22 @@ Do not draw a trend and do not pass three points off as one: state plainly that
 long-run trend is not available for Shopee yet, and report the snapshot plus the
 month-over-month change instead.
 
-### Step 4 — Build the report (pt-BR)
+### Step 4 — Build the report
 
-1. Lead with the **opportunity index**, prominently: 🟢 alto / 🟡 médio / 🔴
-   baixo (show `—` if it is missing), noting the marketplace, the category name
-   and level, and the month the figures describe.
+Write the whole report in the language of the message you are answering — not
+the language of the store or its listings, which are Brazilian either way.
+Every Portuguese word in this step and in Output is a pt-BR template: translate
+the badge wording, the table headers, the section labels and the disclaimer.
+Keep the emoji, the table structure and `R$` exactly as they are. When the
+message is in English, no Portuguese is left anywhere in the report.
+
+1. Lead with the **opportunity index**, prominently: 🟢 alto / 🟡 médio / 🔴 baixo
+   — pt-BR wording, translated for any other language, emoji unchanged — (show
+   `—` if it is missing), noting the marketplace, the category name and level,
+   and the month the figures describe.
 2. Show the monthly indicators table (see Output).
-3. Write a 2–4 sentence **resumo** that interprets the opportunity index
+3. Write a 2–4 sentence summary — labelled **Resumo** in pt-BR — that
+   interprets the opportunity index
    together with concentration and growth:
    - What the level means — high implies good room for new sellers; low implies
      little relative upside.
@@ -203,9 +216,17 @@ month-over-month change instead.
 
 ## Output
 
-Respond in the seller's language, default pt-BR, with no commentary about how the
-report was produced. The indicators table always renders as markdown so it shows
-cleanly in any client.
+Respond in the language of the seller's request, default pt-BR, with no
+commentary about how the report was produced. The indicators table always
+renders as markdown so it shows cleanly in any client.
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 **Opportunity badge** — a heading line naming the marketplace, the category and
 the month the figures cover, for example:
@@ -236,6 +257,9 @@ cells show `—`.
 **Resumo** — the 2–4 sentence interpretation described in the workflow.
 
 **Disclaimer (every report) — use the variant for the marketplace you queried.**
+Each variant below carries the pt-BR wording and the English wording separated by
+` / `. Emit only the half that matches the language of the seller's request —
+never both halves and never the slash.
 
 Mercado Livre:
 

@@ -53,7 +53,11 @@ JoomPulse MCP setup before it can find international products.
   the marketplace's own rounded sold counters refined with review movement. Use
   the matching disclaimer, and disclose the estimate caveat in every output.
 - **Read-only.** The skill never writes or modifies anything.
-- **Language:** detect the seller's language and respond in it. Default to pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** Show `—` for any missing value; never fabricate.
 
 **Shopee data — what differs from Mercado Livre**
@@ -149,9 +153,18 @@ weekly ranking**. Label it plainly as a *top-by-revenue fallback*, never call it
 
 ## Output
 
-Respond in the seller's language (default pt-BR). Lead with a short line naming
-the **marketplace** you queried. The product list always renders as a markdown
-table, and **includes a Category column** (the cross-category differentiator).
+Respond in the language of the seller's request (default pt-BR). Lead with a
+short line naming the **marketplace** you queried. The product list always
+renders as a markdown table, and **includes a Category column** (the
+cross-category differentiator).
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 **Product table (Mercado Livre):**
 

@@ -62,7 +62,11 @@ JoomPulse MCP setup before it can find growing niches.
   own rounded sold counters refined with review movement. Use the matching
   disclaimer.
 - **Read-only.** The skill never writes or modifies anything.
-- **Language:** detect the seller's language and respond in it. Default to pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** Surface the answer, not the steps. Never fill
   gaps from general knowledge; show `—` for any missing value.
 
@@ -155,11 +159,20 @@ the most recent month with the one before it and read nothing longer-run into it
 
 ## Output
 
-Respond in the seller's language (default pt-BR), with no commentary about how the
-result was produced. Lead with a short line naming the **marketplace**, the parent
-category, the **level the ranking is at**, and the month the figures describe. On
-Shopee that line also says plainly that niches deeper than the third level are
-folded into their level-3 ancestor and cannot be separated here.
+Respond in the language of the seller's request (default pt-BR), with no
+commentary about how the result was produced. Lead with a short line naming the
+**marketplace**, the parent category, the **level the ranking is at**, and the
+month the figures describe. On Shopee that line also says plainly that niches
+deeper than the third level are folded into their level-3 ancestor and cannot
+be separated here.
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 The ranking always renders as a markdown table:
 

@@ -59,7 +59,11 @@ JoomPulse MCP setup before it can find opportunities.
   historical listing data, on Shopee from the marketplace's own rounded sold
   counters refined with review movement. Use the matching disclaimer.
 - **Read-only.** The skill does not sign in as the seller or modify any listing.
-- **Language:** detect the seller's language and respond in it. Default to pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** The seller wants the answer, not a play-by-
   play. If one approach does not return data, switch to another quietly; only if
   every approach fails do you say one short, friendly sentence.
@@ -159,9 +163,17 @@ needs. Pull a generous set so the filters have room to work.
 
 ## Output
 
-Respond in the seller's language. Present the result with no commentary about how
-it was produced. The product table always renders as markdown so it displays
-cleanly in any client.
+Respond in the language of the seller's request. Present the result with no
+commentary about how it was produced. The product table always renders as
+markdown so it displays cleanly in any client.
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 Lead with a short intro line naming the **marketplace**, the category and the
 rating threshold actually applied.

@@ -58,8 +58,11 @@ JoomPulse MCP setup before it can analyze a product or find competitors.
 - **Prices are marketplace prices only.** Do not surface sourcing prices,
   margins, or profit figures.
 - **Read-only.** The skill does not sign in as the seller or modify any listing.
-- **Language:** detect the seller's language and respond in it. Default to
-  pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** The seller wants the answer, not a play-by-
   play. Do the analysis quietly and present only the result. If one approach to
   finding the product or its competitors does not work, switch to another
@@ -242,8 +245,16 @@ Both the keyword and photo paths feed the same analog pipeline:
 
 ## Output
 
-Respond in the seller's language. The visible reply contains only the result, in
-this order, with no commentary about how it was produced:
+Respond in the language of the seller's request. The visible reply contains
+only the result, in this order, with no commentary about how it was produced:
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 1. An optional one-line framing sentence, naming the **marketplace**.
 2. The subject product card.
@@ -287,11 +298,12 @@ rating, reviews, favourites, cross-border shipping, photo count, shop tier, and
 links column holding the item and shop links on Shopee. **No catalogue, buy-box
 or seller-count columns** — drop them, do not leave them blank.
 
-You may translate the column headers and card labels into the seller's language.
-Note that the sales windows are **not** the same on the two marketplaces: Mercado
-Livre reports weekly and monthly figures, Shopee reports 30-day figures only —
-label the Shopee columns as 30 days and never present a 30-day figure under a
-weekly or monthly heading. Empty field → `—`; never guess or fabricate.
+You may translate the column headers and card labels into the language of the
+seller's request. Note that the sales windows are **not** the same on the two
+marketplaces: Mercado Livre reports weekly and monthly figures, Shopee reports
+30-day figures only — label the Shopee columns as 30 days and never present a
+30-day figure under a weekly or monthly heading. Empty field → `—`; never guess
+or fabricate.
 
 **Disclaimer (every report) — use the variant for the marketplace you queried.**
 

@@ -19,9 +19,10 @@ description: >
 # Mercado Livre — My Product vs. Catalog (Buy-Box Competitiveness)
 
 This skill compares the seller's **own** Mercado Livre (Brasil) listing against
-**the available competing listings of the same catalog product** — the sellers competing
-for the same buy-box — and tells the seller, in pt-BR, where they win, where they
-lose, and **what to fix first** to win the buy-box and convert more.
+**the available competing listings of the same catalog product** — the sellers
+competing for the same buy-box — and tells the seller, in the language of their
+request, where they win, where they lose, and **what to fix first** to win the
+buy-box and convert more.
 
 Given a product by a Mercado Livre link, a JoomPulse link, a Mercado Livre listing
 identifier, or a catalog product identifier, it identifies the seller's listing and
@@ -63,7 +64,11 @@ JoomPulse MCP setup before it can compare a listing against its catalog.
   review count, logistics, and seller attributes are real Mercado Livre data — say
   so, it is a strength of the report.
 - **Read-only.** The skill does not sign in as the seller or modify any listing.
-- **Language:** detect the seller's language and respond in it. Default to pt-BR.
+- **Language:** write in the language of the message you are answering, and
+  default to pt-BR only when that is unclear. Never infer the language from the
+  store, its listings or the marketplace — those are Brazilian whatever
+  language the seller writes in, so a seller who asks in English gets the whole
+  report in English.
 - **Keep the workflow invisible.** The seller wants the answer, not a play-by-play.
   If one lookup returns nothing, switch approaches quietly; only if everything fails
   do you say one short, friendly sentence.
@@ -116,7 +121,16 @@ Each parameter gets one status, with a colour marker so it reads at a glance:
 
 ## Output
 
-Respond in pt-BR, leading with the verdict:
+Respond in the language of the seller's request, default pt-BR, leading with
+the verdict:
+
+The column headers, labels and disclaimers below are written in pt-BR because
+that is the default. They are a template, not literal strings: when the seller
+writes in another language, translate all of them — the headers, row values
+such as `sim` / `não` / `ouro`, and the disclaimer — and keep the structure,
+the emoji and the `R$` money formatting, which stays the same in every language
+because the marketplace trades in reais. When the request is in English, no
+Portuguese is left anywhere in the answer.
 
 1. **Veredito** — two to four sentences: where the seller wins, where they lose,
    their buy-box position, and the single top priority.