CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-configuration

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

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable — every pattern is complete, executable pydantic-settings code with correct modern APIs — and well organized by concept. Its weaknesses are redundancy (the fail-fast and defaults patterns repeat code) and a monolithic single-file layout that inlines advanced material better kept in a reference file.

Suggestions

Merge the nearly identical fail-fast try/except blocks in Pattern 1 and Pattern 2 into a single pattern, keeping the richer per-field error printing version and deleting the duplicate.

Move the advanced patterns (nested configuration groups, secrets from files, custom model validation) into a references/ADVANCED.md and summarize them in one-line pointers from SKILL.md, keeping only the Quick Start and fundamental patterns inline.

Trim Pattern 3, which re-demonstrates defaults already shown in Pattern 1 — fold its 'defaults for local dev, required for secrets' guidance into a sentence under Pattern 1 or the Best Practices list.

DimensionReasoningScore

Conciseness

The pattern-per-concern structure is mostly efficient, but the fail-fast try/except with sys.exit(1) appears nearly verbatim in both Pattern 1 and Pattern 2, and Pattern 3 re-demonstrates defaults already shown in Pattern 1. The duplication is substantial rather than minor, so this sits at anchor 3 rather than 4.

3 / 5

Actionability

Every pattern ships complete, executable code — full Settings classes with Field aliases, model_config ("env_file", "env_nested_delimiter", "secrets_dir"), a working field_validator for comma-separated lists, and a model_validator for cross-field checks — plus copy-paste env-var and .env examples. This matches anchor 5: copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Not a multi-step or destructive process, so no validation cap applies; organization flows logically (Quick Start → Fundamental → Advanced → Best Practices) and the fail-fast pattern includes a feedback loop (print each missing field, instruct user, exit). Anchor 4 rather than 5 because there is no explicit sequenced path for the "setting up a new project's configuration system" use case.

4 / 5

Progressive Disclosure

Single ~365-line file with good section headers, but the advanced patterns (nested groups via env_nested_delimiter, secrets_dir, model validation) are inlined where a references file would keep SKILL.md lean, and the under-50-line simple-skill exception does not apply at this length. Anchor 3 (content that should be separate is inline) fits better than 4, which expects most content appropriately split.

3 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete mechanism, and an explicit multi-trigger "Use when" clause that together answer both what the skill does and when to reach for it. Its only weaknesses are minor — a few missing natural synonyms ("env vars", ".env", "dotenv") and slight overlap risk on the secrets trigger.

DimensionReasoningScore

Specificity

"Python configuration management via environment variables and typed settings" names the domain and mechanism, and the when-clause lists several concrete actions ("externalizing config", "setting up pydantic-settings", "managing secrets", "implementing environment-specific behavior"). Matches anchor 4 — several specific actions with minor coverage gaps — rather than anchor 5, whose action list is more comprehensively enumerated.

4 / 5

Completeness

Explicitly answers both: the "what" is the leading capability statement ("Python configuration management via environment variables and typed settings") and the "when" is a dedicated "Use when..." clause with four concrete triggers. This matches anchor 5; the when-clause leaves nothing implicit, so anchor 4's caveat about weaker 'when' doesn't apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "externalizing config", "setting up pydantic-settings", "managing secrets", "environment-specific" — giving good keyword coverage. Not anchor 5 because common synonyms and artifacts like "env vars", ".env", or "dotenv" are missing.

4 / 5

Distinctiveness Conflict Risk

The pydantic-settings/typed-settings framing carves a clear niche with distinct triggers, but "managing secrets" overlaps with dedicated secrets-management skills. Anchor 4 (mostly distinct, minor overlap risk) fits better than 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Dicklesworthstone/pi_agent_rust

Path

tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-configuration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.