pydantic-models-py

Create Pydantic models following the multi-model pattern for clean API contracts.

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pydantic-models-py/SKILL.md

Quality

Content

47%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 skill provides a reasonable overview of the multi-model Pydantic pattern with useful code snippets for specific concerns (aliases, optional fields, DB documents), but suffers from a missing template file that the Quick Start depends on, vague integration steps without validation, and a meaningless 'When to Use' section. The actionability is hampered by showing only fragments rather than a cohesive, complete example of the full pattern.

Suggestions

Provide the referenced assets/template.py in the bundle, or inline a complete multi-model example showing all five model types (Base, Create, Update, Response, InDB) working together.

Add validation steps to the Integration Steps section, such as running type checks or importing the models to verify they work correctly.

Remove the 'When to Use' section entirely—it adds no information and wastes tokens.

Make the Integration Steps more concrete with specific file paths, example export statements, and a brief TypeScript type example.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of tables and concise code examples. The 'When to Use' section is a vacuous tautology that wastes tokens, and the 'Quick Start' section's template reference is fine but the multi-model pattern table could arguably be trimmed since Claude understands these patterns.	4 / 5
Actionability	Provides some concrete code snippets for aliases, optional fields, and DB documents, but the core workflow relies on a template file (assets/template.py) that isn't provided in the bundle. The code examples are fragments rather than a complete, executable model definition showing the full multi-model pattern together.	3 / 5
Workflow Clarity	The 'Integration Steps' section lists 3 steps but they are vague ('Add corresponding TypeScript types' with no specifics). There's no validation checkpoint—no mention of running tests, checking imports, or verifying the models work. For a skill that involves creating multiple interdependent models and exporting them, the workflow is underspecified.	2 / 5
Progressive Disclosure	References assets/template.py which is not provided in the bundle, making the core 'Quick Start' workflow broken. No bundle files exist to support the referenced paths. The content is relatively short and doesn't need external files beyond the template, but the missing template is a critical gap.	2 / 5
	Total	11 / 20 Passed

Description

45%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.

The description identifies a specific technology (Pydantic) and a particular pattern (multi-model for API contracts), giving it reasonable distinctiveness. However, it lacks a 'Use when...' clause, doesn't enumerate concrete actions beyond 'create', and misses common synonyms and trigger terms users would naturally use.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Pydantic', 'data model', 'schema', 'validation', 'request/response model', 'FastAPI models'.

Expand the capability list with specific actions such as 'generates base models, request/response schemas, nested models, and field validators'.

Include natural synonyms and related terms users might say, such as 'data validation', 'serialization', 'BaseModel', or 'type-safe API schemas'.

Dimension	Reasoning	Score
Specificity	Names the domain (Pydantic models) and one concrete pattern ('multi-model pattern for clean API contracts'), but doesn't elaborate on what specific actions are performed—e.g., generating base models, request/response schemas, validation, nested models, etc.	3 / 5
Completeness	Provides a partial 'what' (create Pydantic models following a specific pattern) but has no 'when' clause or trigger guidance. Per rubric, missing 'Use when...' caps completeness at 3, and the 'what' itself is only moderately clear, placing this at 2.	2 / 5
Trigger Term Quality	Includes 'Pydantic models' and 'API contracts' which are relevant keywords, but misses natural user phrases like 'data validation', 'schema', 'BaseModel', 'request model', 'response model', 'serialization', or 'FastAPI'.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Pydantic models' and 'multi-model pattern' is fairly distinctive and unlikely to conflict with most other skills. Minor overlap risk with general Python code generation or API development skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/pydantic-models-py/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.