[Feature Request] Support multi-language skill trigger phrases — non-English users cannot auto-trigger skills

Background

I'm a Traditional Chinese speaker who uses Claude Code daily. I recently discovered that several skills I had installed — including supreme-leader (parallel multi-agent orchestration) — had zero triggers over 45 days, despite being fully enabled and working correctly.

After investigation, the root cause was simple: every trigger phrase in each skill's description field was written in English (e.g. "split this across multiple agents", "orchestrate this", "spin up a team"). Because I interact with Claude entirely in Traditional Chinese, the model never matched my natural language to these English-only trigger conditions.

The real cost isn't tokens

The token overhead from loading unused skill descriptions is negligible. What I actually lost was far more significant: I had capable tools I didn't know I had. I spent time manually working through problems that installed skills would have handled automatically — not because the skills didn't exist, but because the bridge between my language and their activation language was missing entirely.

I only discovered this gap by accident, while auditing my skill dashboard. For every user who finds this, there are likely many more who never do.

Proposed solutions

1. Multi-language trigger support in skill descriptions

Allow skill authors to specify trigger phrases in multiple languages, or support a triggers frontmatter field with language-keyed entries:

---
name: my-skill
description: "Short description for context budget"
triggers:
  en: ["orchestrate this", "split this across agents", "spin up a team"]
  zh-TW: ["開多個 agent", "平行執行", "拆成多個子任務", "分工處理"]
  ja: ["並列実行", "複数のエージェントで"]
---

2. Language-aware skill matching

When a session language is configured (e.g. "language": "traditional chinese" in settings.json), the model should weight trigger matching toward that language — or at minimum, surface a warning when installed skills have no trigger phrases in the user's configured language.

3. Official localization for built-in and marketplace skills

For first-party and featured marketplace skills, provide translated descriptions and trigger examples in Traditional Chinese, Japanese, Spanish, and other major non-English languages.

Why this matters beyond my case

Claude Code's skill system is genuinely powerful. But right now it implicitly assumes English as every user's working language. A non-English speaker ends up with a degraded experience — not because of any capability gap, but because of a localization gap in the trigger layer.

A user who speaks Chinese, Japanese, Spanish, or Arabic shouldn't need to switch to English when talking to Claude just to unlock tools they've already installed. The skill is there. The intent is there. Only the language match is missing.

My workaround

I've since manually added Traditional Chinese trigger phrases to my local skill descriptions and translated all skill content to Traditional Chinese. It works — but it requires knowing the problem exists in the first place, which most users won't.

---

I've learned far more from using Claude Code than I've ever lost to misconfigured tooling. I'm filing this because I'd like other non-English speakers to have the full experience from day one, not after 45 days of silent misfires.

Thank you for building something worth caring about.