langchain-multi-env-setup
Build reliable dev / staging / prod isolation for LangChain 1.0 services\ \ \u2014\nPydantic `Settings` + `SecretStr`, cloud Secret Manager in prod, per-env\n\ prompt and model version pinning, env-specific checkpointer and observability.\n\ Use when graduating from `.env`-in-dev to real prod infra, or debugging a\nconfig\ \ that loaded the wrong values in the wrong env.\nTrigger with \"langchain multi-env\"\ , \"langchain pydantic settings\",\n\"langchain secret manager\", \"langchain env\ \ config\", \"langchain prod setup\".\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# LangChain Multi-Env Setup (Python) ## Overview A team ships a LangChain 1.0 service to staging with `python-dotenv` loading `.env.staging` into `os.environ`. Security audits — `docker exec STAGING-POD env` prints `ANTHROPIC_API_KEY=sk-ant-api03-...` in plain text. Anyone with `kubectl exec`, any sidecar, any core dump, any error tracker that auto-captures process env sees the key. This is pain *
What does the langchain-multi-env-setup skill do?
Build reliable dev / staging / prod isolation for LangChain 1.0 services\ \ \u2014\nPydantic `Settings` + `SecretStr`, cloud Secret Manager in prod, per-env\n\ prompt and model version pinning, env-specific checkpointer and observability.\n\ Use when graduating from `.env`-in-dev to real prod infra, or debugging a\nconfig\ \ that loaded the wrong values in the wrong env.\nTrigger with \"langchain multi-env\"\ , \"langchain pydantic settings\",\n\"langchain secret manager\", \"langchain env\ \ config\", \"langchain prod setup\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langchain-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.