Configuration
SkillDev toolsPick the home for a configuration value, environment variable, backend URL, partner key, public token, per-environment constant, build secret, and take an existing one out of `@shared/env` / `@ledgerhq/live-env` (`getEnv`, `setEnv`, `useEnv`, `injectDefinitions`). Read before adding or changing any env var, `.env` entry or `getEnv` call site.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Configuration skill
What this skill tells your AI
The instructions your AI receives, as published by ledgerhq/ledger-live in .agents/skills/configuration/SKILL.md and read by ahel’s review.
Read /docs/configuration.md — the canonical guide. It opens with a Pattern → home table mapping each kind of value to exactly one home, and has one section per home with this repo's mechanics and worked examples. Jump to the row that matches instead of paraphrasing the doc in chat.
Two rules to apply without reading further:
@shared/envand@ledgerhq/live-envare deprecated: no new definition, no new call site, including in tests. Migrating a variable means deleting its definition in the same PR.- A value in an app's
.envfile ships inside the artifact. Public configuration only; a real build secret stays in the workflow step and never reaches app code.
Signals
- GitHub stars
- 618
- Forks
- 491
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
configuration-ledgerhq- Source
- github.com/ledgerhq/ledger-live