Specx Settings

Community

maksimzayats

specx-settings

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.

Overview

Publisher	maksimzayats
Repository	`specx`
Skill name	`specx-settings`
Stars	201
Forks	34
Bundled files	2
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by maksimzayats on GitHub. Read the source before you install it.

Installation

Install the Specx Settings AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/maksimzayats/specx/tree/main/.agents/skills/specx-settings
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p .claude/skills
cp -r /tmp/specx/.agents/skills/specx-settings .claude/skills/specx-settings

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Specx Settings in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Specx Settings on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Specx Settings is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.py and its LoggingConfigurator.
Use BaseStrEnum for finite configuration values such as logging levels.
Inject settings objects only into delivery, infrastructure, and composition classes. Do not inject BaseRuntimeSettings subclasses 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 diwire auto-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 with SettingsClass.model_validate({...}) so strict type checking does not mistake raw input strings for already-validated field types.
Do not read os.environ outside 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.example when adding user-provided environment variables.
Isolate settings-source tests from a developer's .env by changing to tmp_path, then override environment values with monkeypatch.
Do not inherit raw BaseSettings; inherit specx.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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
references/settings.md9 KB

Frequently asked questions

What does the Specx Settings AI skill do?

Why use Specx Settings on TypingMind?

Because you install it once and use it with any model. Specx Settings is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Specx Settings in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/maksimzayats/specx/tree/main/.agents/skills/specx-settings. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Specx Settings?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Specx Settings?

As many as you like. As long as a model supports skills, you can use Specx Settings with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Specx Settings AI skill free?

Yes. It is published on GitHub by maksimzayats under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

specx Settings

Rules

Code Style

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now