PlugWiki

python-configuration Skill for Claude Code: Typed Settings From Env Vars

Teaches Claude to move Python config out of code into environment variables and typed pydantic settings that fail fast when something is missing.

Installs
11.8K
on skills.sh
Stars
42.1K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

python-configuration shows Claude how to externalize configuration with pydantic-settings. It covers a central typed Settings class, failing at startup with a clear message when a required value is missing, local development defaults, and namespaced variable names like DB_HOST. A details file adds type coercion, per-environment settings, nested groups, secrets read from files and validation.

It triggers when you ask about config, env vars, pydantic-settings or secrets. The folder holds 2 Markdown files and no scripts. The SKILL.md suggests a local .env file with placeholder values and says to keep it out of git.

Good for

  • Python developers replacing hardcoded values with env vars
  • Teams who want secrets kept out of code and git
  • Developers who need dev, staging and prod settings from one codebase

Install python-configuration

Claude Code

  1. 1

    Copy this prompt.

    Install the python-configuration skill in Claude Code. Run this command:

/plugin marketplace add wshobson/agents
/plugin install python-development@claude-code-workflows

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The python-development plugin adds 15 more Python skills, 3 agents and a /python-development:python-scaffold command. The skills-only route installs just this skill, without the plugin's agents or commands (README).

From the project README. Source.

What's in the skill

When it loads

Python configuration management via environment variables and typed settings. Use when externalizing config, setting up pydantic-settings, managing secrets, or implementing environment-specific behavior.

Sections in SKILL.md

  1. When to Use This Skill
  2. Core Concepts
  3. 1. Externalized Configuration
  4. 2. Typed Settings
  5. 3. Fail Fast
  6. 4. Sensible Defaults
  7. Quick Start
  8. Fundamental Patterns
  9. Pattern 1: Typed Settings with Pydantic
  10. Pattern 2: Fail Fast on Missing Configuration
  11. Pattern 3: Local Development Defaults
  12. Pattern 4: Namespaced Environment Variables
  13. Detailed worked examples and patterns
  14. Best Practices Summary

Key facts

Author
Seth Hobson
Repo
wshobson/agents
License
MIT
Installs on skills.sh
11,771 (Nov 2, 2026)
GitHub stars
42,081 (Nov 2, 2026), whole repo
Last commit
Oct 30, 2026 (repo)
Files in the skill folder
2 files including SKILL.md
Part of
python-development plugin: 3 agents, 16 skills, 1 command
Works in
Claude Code and Codex plugins; skills-only installers for other tools

What it includes

  • One Settings class that loads and validates all config.

    Pattern 1, using pydantic-settings and an optional .env file.

    Typed settings with Pydantic

  • Crashes at startup with a clear error list.

    Pattern 2: catch ValidationError and exit.

    Fail fast on missing config

  • Defaults for dev values, none for secrets.

    Pattern 3, with a .env example to keep out of git.

    Local development defaults

  • Prefixes related variables, such as DB_ and REDIS_.

    Pattern 4, with a command that prints variable names only, not values.

    Namespaced variables

  • Turns env strings into typed values.

    Pattern 5, in references/details.md.

    Type coercion

  • Separate dev, staging and prod settings.

    Pattern 6, in references/details.md.

    Environment-specific config

  • Groups related settings into sub-models.

    Pattern 7, in references/details.md.

    Nested configuration groups

  • Reads secrets from mounted files.

    Pattern 8, in references/details.md.

    Secrets from files

  • Checks config correctness at boot.

    Pattern 9, in references/details.md.

    Configuration validation

  • A 10-point checklist ending the SKILL.md.

    Includes never committing secrets and not calling os.getenv() across the code.

    Best practices summary

From the official docs

Questions

What does python-configuration do?

It teaches Claude to handle Python config with environment variables and pydantic-settings. That means one typed Settings object, startup validation, safe defaults and secrets kept out of code.

How do I install it?

Use the install box above. The README offers the python-development plugin, which adds 16 Python skills and 3 agents, or a skills-only install of just this skill.

Does it work in Claude.ai, Codex or Cursor?

The README documents Claude Code and Codex plugins and a Cursor plugin marketplace, plus skills-only installers for other tools. It does not describe the Claude app.

Does it need pydantic-settings?

The examples import pydantic_settings and pydantic. The skill has no install command, so add the package to your project.

Is it safe?

The skill bundles no scripts. It tells Claude to put secrets in env vars or a gitignored .env file, not in code, and its debug command prints variable names rather than values. Still check that a .env is in .gitignore before committing.

Does it cover secret managers?

Only briefly. The best practices in the SKILL.md say to use gitignored .env files or secret managers, and one pattern reads secrets from mounted files. It gives no code for a specific manager.

Information

updated Nov 2, 2026

Repository
wshobson/agents
Folder
plugins/python-development/skills/python-configuration

wshobson/agentsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. wshobson/agents README · github.com
  2. python-configuration SKILL.md · github.com
  3. python-configuration details.md · github.com
  4. python-development plugin.json · github.com

Updated Nov 2, 2026.