← ClaudeAtlas

socialseal-bilingual-demand-monitoringlisted

Use this skill when the user asks what people search in a local language versus English, whether a trend started in one language first, how translated/localized queries differ, or how to monitor multilingual demand. Compare language-clean SocialSeal surfaces, bridge terms with English glosses, and flag emerging queries to track or brief.
OpenSealAI/agent-skills · ★ 0 · DevOps & Infrastructure · score 65
Install: claude install-skill OpenSealAI/agent-skills
# SocialSeal Bilingual Trend and Demand Monitoring ## Overview In many markets a trend starts in the local language before it appears in English (or vice versa). If you only watch one language you see the trend late. This skill maps the **explicit split between local-language and English search demand** for the same market and platform, then compares movement across that split over time so an emerging micro-trend is caught in whichever language it begins. The unit of comparison is two (or more) language-clean tracking surfaces for the same market and intent: one local-language group and one English group. SocialSeal keeps discoverability trustworthy only when each group is one platform, one market/language context, and one coherent intent (see `references/strategy-foundations.md`). This skill compares across those clean surfaces; it does not mix languages inside one group. ## When to Use - Standing up or maintaining paired local-language and English monitoring for a market. - Detecting emerging keywords/queries early in either language. - Comparing discoverability or surfaced attention between the local-language and English split. - Bridging local queries to English (and back) so a trend spotted in one language can be briefed in the other. Route group creation to `socialseal-tracking-group-design`, opportunity sizing to `socialseal-opportunity-analysis`, and ongoing tracking hygiene to `socialseal-discoverability-tracking`. ## The bilingual split, concretely A single