language-detector-api

Implements and debugs browser Language Detector API integrations in JavaScript or TypeScript web apps. Use when adding LanguageDetector support checks, availability and model download flows, session creation, detect() calls, input-usage measurement, permissions-policy handling, or compatibility fallbacks for built-in language detection. Don't use for server-side language detection SDKs, cloud translation services, or generic NLP pipelines.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean, highly actionable procedural skill with clear sequencing and a validation phase. Its one real defect is that the body references six bundle files (references, assets, scripts) that are not present, undermining progressive disclosure.

Suggestions

Ship the referenced bundle files so the condition-gated references resolve: references/language-detector-reference.md, examples.md, compatibility.md, troubleshooting.md, assets/language-detector-session.template.ts, and scripts/find-language-detector-targets.mjs.

If any referenced file is not yet authored, either create a stub or remove the reference from the body so Claude is not directed to a missing path.

Consider folding a minimal inline create()/detect() code snippet into Step 3 so the core flow is copy-paste ready even before the asset template is opened.

Dimension	Reasoning	Score
Conciseness	Tight imperative instructions with no concept-explaining fluff (no 'what is the Language Detector API' padding); every step is actionable and assumes Claude's competence, with only minor purposeful repetition of the secure-context/availability constraint across workflow phases.	3 / 3
Actionability	Names the concrete API surface — 'LanguageDetector.create()', 'availability()', 'detect()', 'measureInputUsage()', 'destroy()', options 'expectedInputLanguages'/'monitor', 'allow="language-detector"', error types 'NotAllowedError'/'InvalidStateError'/'QuotaExceededError', and the executable command 'node scripts/find-language-detector-targets.mjs .'; per scoring_notes, absence of inline code in an instruction-only skill is not penalized when guidance is this actionable.	3 / 3
Workflow Clarity	Five sequenced steps with sub-steps, explicit stop/ask checkpoints (1.5, 1.6, 2.8), a dedicated 'Step 5: Validate behavior' checklist, and an Error Handling section providing recovery feedback loops — matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	Signaling is excellent — six references are condition-gated ('Read references/compatibility.md when preview flags ... matter') and one level deep — but none of the referenced files (references/*.md, assets/language-detector-session.template.ts, scripts/find-language-detector-targets.mjs) exist in the bundle, so navigation breaks in practice and 'easy navigation' is not realized.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: third-person voice, comprehensive concrete actions, explicit 'Use when' triggers, and clear negative scope that bounds the niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'Implements and debugs', 'support checks, availability and model download flows, session creation, detect() calls, input-usage measurement, permissions-policy handling, ... compatibility fallbacks' — matching the multiple-specific-actions anchor; not merely naming the domain.	3 / 3
Completeness	Explicitly states what ('Implements and debugs browser Language Detector API integrations in JavaScript or TypeScript web apps') and when ('Use when adding LanguageDetector support checks ...'), plus negative scope ('Don't use for ...'), satisfying both what-and-when with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural terms a developer would say — 'Language Detector API', 'LanguageDetector support checks', 'detect() calls', 'model download', 'permissions-policy', 'built-in language detection' — with good breadth rather than single generic jargon.	3 / 3
Distinctiveness Conflict Risk	Narrow browser-only JS/TS niche with explicit exclusion of server-side SDKs, cloud translation, and generic NLP pipelines makes it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	15 / 16 Passed

Repository: webmaxru/web-ai-agent-skills
Path: skills/language-detector-api/SKILL.md
Commit: f4c5a23

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.