Python Configuration
wshobson/agents
Python configuration management via environment variables and typed settings.
Add runtime configuration to specx Python services with pydantic-settings.
Install Specx Settings
$ npx skills add maksimzayats/specx --skill specx-settings -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maksimzayats/specx specx-settings --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specx-settings .claude/skills/specx-settings && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .claude/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maksimzayats/specx/tree/main/skills/specx-settingsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maksimzayats/specx --skill specx-settings -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maksimzayats/specx specx-settings --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specx-settings .agents/skills/specx-settings && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .agents/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maksimzayats/specx --skill specx-settings -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maksimzayats/specx specx-settings --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specx-settings .cursor/skills/specx-settings && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .cursor/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maksimzayats/specx.git --path skills/specx-settings--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maksimzayats/specx --skill specx-settings -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maksimzayats/specx specx-settings --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specx-settings .gemini/skills/specx-settings && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .gemini/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maksimzayats/specx specx-settingsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maksimzayats/specx --skill specx-settings -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specx-settings .github/skills/specx-settings && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .github/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maksimzayats/specx --skill specx-settings -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maksimzayats/specx specx-settings --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specx-settings .opencode/skills/specx-settings && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "specx-settings" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-settings into .opencode/skills/specx-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-settings", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
specx-settings- GitHub stars
- 202
- Token cost
- ~707 tokens
- SKILL.md length
- 294 words
- Files
- 3 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add runtime configuration to specx Python services with pydantic-settings.
- Creating settings classes
- SKILL.md covers Rules, Code Style and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Environment variables
What it does
Specx Settings is an agent skill from maksimzayats/specx. Add runtime configuration to specx Python services with pydantic-settings. Use when creating settings classes, environment variables, .env.example, injecting settings at delivery, infrastructure, or composition edges, documenting config, mapping configuration into typed core policy collaborators, or removing direct environment reads from core code.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/settings.md`).
It sits in Development, covering Secrets management. It works with Python and Pydantic. The repository describes itself as: ⚙️ Executable architecture guardrails and agent skills for building structured Python services! The licence is MIT.
When your agent uses it
- Creating settings classes
- Environment variables
- Injecting settings at delivery
- Composition edges
Example prompts
- “/specx-settings”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 9362406. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Specx Settings loads about 707 tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 294 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:38
ettings-source tests from a developer's `.env` by changing to
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from maksimzayats/specx at commit 9362406, republished under its MIT licence (© maksimzayats). 294 words, ~707 tokens.
Download SKILL.mdSave it as
.claude/skills/specx-settings/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- specx-settings
- description
- Add runtime configuration to specx Python services with `pydantic-settings`. Use when creating settings classes, environment variables, `.env.example`, injecting settings at delivery, infrastructure, or composition edges, documenting config, mapping configuration into typed core policy collaborators, or removing direct environment reads from core code.
specx Settings
Use this skill whenever runtime configuration is needed. Read
references/settings.md before adding settings code.
Rules
- Model runtime config with classes that inherit
BaseRuntimeSettings. - Give each settings class a docstring that explains the configuration scope
and includes a concrete
Example:. - Place settings near the class that consumes them unless the setting is truly application-wide.
- Logging settings are application-wide and live beside
infrastructure/logging/configurator.pyand itsLoggingConfigurator. - Use
BaseStrEnumfor finite configuration values such as logging levels. - Inject settings objects only into delivery, infrastructure, and composition
classes. Do not inject
BaseRuntimeSettingssubclasses into core use cases, services, capabilities, entities, repositories, or gateway ports. - When configuration represents a genuine business policy, map it at the
composition root into a typed core value or capability that has no dependency
on Pydantic or
BaseRuntimeSettings. - Let
diwireauto-register settings as root-scoped singletons. Register a settings instance explicitly only for an intentional override. - At operational entrypoints, load required runtime values with
SettingsClass.from_environment(). Build explicit test or composition overrides withSettingsClass.model_validate({...})so strict type checking does not mistake raw input strings for already-validated field types. - Do not read
os.environoutside settings classes or composition code. - Use clear environment variable names and safe defaults only when safe.
- Type secret fields with
SecretStr, keep secrets out of examples, and unwrap them only at the adapter call that needs the raw value. - Update
.env.examplewhen adding user-provided environment variables. - Isolate settings-source tests from a developer's
.envby changing totmp_path, then override environment values withmonkeypatch. - Do not inherit raw
BaseSettings; inheritspecx.infrastructure.foundation.settings.BaseRuntimeSettings.
Code Style
Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.
References
references/settings.md- settings placement, examples, env naming, and test overrides.
© maksimzayats, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/specx-settings of maksimzayats/specx.
- SKILL.md
- agents/openai.yaml
- references/settings.md
Open the folder on GitHubat commit 9362406
Compare with similar skills
Specx Settings next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Specx Settings this skillmaksimzayats/specx | 202 | — | ~707 | Automated safety check: Notes | MIT | |
| Python Configurationwshobson/agents | 40k | — | ~1.6k | Automated safety check: Notes | MIT | |
| Git HooksProrise-cool/Claude-Code-Multi-Agent | 306 | — | ~3.6k | Automated safety check: Notes | None | |
| A2ui Generate Pydantic Modelsa2ui-project/a2ui | 17k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Releasezmievsa/cadwyn | 309 | — | ~522 | Automated safety check: Pass | MIT | |
| Ag2 Add Custom Toolag2ai/build-with-ag2 | 252 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Git Hooks
Prorise-cool/Claude-Code-Multi-Agent
Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.
A2ui Generate Pydantic Models
a2ui-project/a2ui
Automated generator for strongly typed Pydantic v2 data models and basic catalogs across any A2UI protocol version (v0.8, v0.9, v0.9.1, v1.0, etc.).
Release
zmievsa/cadwyn
Prepare and publish Cadwyn releases. An agent skill from zmievsa/cadwyn.
Ag2 Add Custom Tool
ag2ai/build-with-ag2
Add a custom Python tool to an AG2 beta Agent using the @tool decorator.
- Official
Adk Style
google/adk-python
Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file…
More from maksimzayats/specx
All 12 skills in this repoSpecx Add Core Service
maksimzayats/specx
Add or refactor a specx core scope service. An agent skill from maksimzayats/specx.
Specx Add Core Use Case
maksimzayats/specx
Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx.
Specx Add Delivery Controller
maksimzayats/specx
Add delivery controllers for specx services, especially FastAPI HTTP routes.
Specx Add Infrastructure Adapter
maksimzayats/specx
Add technical infrastructure adapters for specx core scopes.
Specx Component Architecture
maksimzayats/specx
Design or review specx core scope boundaries in Python services.
Specx Diwire Composition
maksimzayats/specx
Wire dependency injection for a specx Python service with diwire.
Related
Categories
Questions about Specx Settings
What does Specx Settings do?
Add runtime configuration to specx Python services with pydantic-settings. Specx Settings is an agent skill from maksimzayats/specx. Add runtime configuration to specx Python services with pydantic-settings.
When should I use Specx Settings?
Specx Settings fits situations like: creating settings classes; environment variables; injecting settings at delivery; composition edges.
How do I install Specx Settings in Claude Code?
Run `npx skills add maksimzayats/specx --skill specx-settings -a claude-code`. Or copy the skill folder (skills/specx-settings in maksimzayats/specx) into .claude/skills/specx-settings in your project. Claude Code loads it when a task matches its description.
How do I install Specx Settings in Codex?
Run `npx skills add maksimzayats/specx --skill specx-settings -a codex`. Or copy the skill folder (skills/specx-settings in maksimzayats/specx) into .agents/skills/specx-settings in your project. Codex loads it when a task matches its description.
Can I use Specx Settings in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maksimzayats/specx --skill specx-settings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specx-settings, .gemini/skills/specx-settings, .github/skills/specx-settings and .opencode/skills/specx-settings in your project.
What does Specx Settings need to run?
SKILL.md names no scripts, command-line tools or credentials: Specx Settings is instructions for the agent only. Our summary lists: Python 3.
Does Specx Settings access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Specx Settings safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Specx Settings use?
Specx Settings is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Specx Settings use?
About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Specx Settings?
Skills that share tags, products or a category with Specx Settings: Python Configuration (wshobson/agents, 40k stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 306 stars), A2ui Generate Pydantic Models (a2ui-project/a2ui, 17k stars) and Release (zmievsa/cadwyn, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specx Settings?
maksimzayats (a GitHub user) maintains it in maksimzayats/specx, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 8, 2026.
Source: maksimzayats/specx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.