language-detector-api

Detect languages in browser apps using the LanguageDetector API.

46|4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/webmaxru/agent-skills --skill language-detector-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-detector-api
Source: https://github.com/webmaxru/agent-skills/tree/main/skills/language-detector-api
Command: npx skills add https://github.com/webmaxru/agent-skills --skill language-detector-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Detect and manage language detection in browser-based apps using the LanguageDetector API.

Core Features & Use Cases

  • Integrates LanguageDetector to detect languages in web UIs and content streams.
  • Provides availability checks, session creation, and per-call detect with optional quota measurement.
  • Use cases include multilingual UI localization, dynamic content adaptation, and offline-first web apps.

Quick Start

Create a LanguageDetector session and detect the language of the input text 'Hello, world'

Frequently Asked Questions about language-detector-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect browser language for frontend localization using the LanguageDetector API?

Browser language detection for localized UX uses the LanguageDetector API to create guarded sessions, perform detect calls, and check availability states. The API supports expectedInputLanguages, abortable calls, and monitor callbacks for download progress.

What's the best way to manage LanguageDetector API sessions for dynamic content adaptation?

Managing LanguageDetector API sessions requires availability checks before session creation, then per-call detect with optional quota measurement. This approach supports multilingual UI localization and dynamic content adaptation in offline-first web apps.

Does the LanguageDetector API work in secure contexts and handle quota-aware usage?

The LanguageDetector API operates in secure contexts and provides quota-aware usage through detect calls. Sessions support availability checks, abortable calls, and monitor callbacks to track download progress during language detection operations.

How do I check LanguageDetector API availability and create a session for multilingual UI?

Checking LanguageDetector API availability involves calling availability() with expectedInputLanguages. Once available, create a session using create() with the same parameters, enabling detect calls for multilingual UI localization and content stream analysis.

Can I use expectedInputLanguages in both availability checks and session creation for language detection?

The LanguageDetector API supports expectedInputLanguages in both availability() and create() methods. This ensures consistent language detection configuration across guarded session creation and per-call detect operations in browser-based web apps.

What are the limitations of browser-based language detection with the LanguageDetector API?

Browser-based language detection with the LanguageDetector API requires secure contexts and quota-aware usage. Sessions need availability checks before creation, and detect calls support abortable operations with monitor callbacks for download progress tracking.