Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/pydantic-models-py
Create Pydantic models following the multi-model pattern for clean API contracts.
Passed 18 of 22 test cases with the skill, and 4 of 22 without it.
and 22 more in the full report
14 fixed4 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When adding camelCase aliases to Pydantic models for JSON payload serialization, which configuration setting allows parsing both snake_case and camelCase keys?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies setting populate_by_name = True inside class Config. | Missed | Passed |
The instructions your model reads when the skill loads.
Create Pydantic models following the multi-model pattern for clean API contracts.
Copy the template from assets/template.py and replace placeholders:
{{ResourceName}} → PascalCase name (e.g., Project){{resource_name}} → snake_case name (e.g., project)| Model | Purpose |
|---|---|
Base | Common fields shared across models |
Create | Request body for creation (required fields) |
Update | Request body for updates (all optional) |
Response | API response with all fields |
InDB | Database document with doc_type |
class MyModel(BaseModel):
workspace_id: str = Field(..., alias="workspaceId")
created_at: datetime = Field(..., alias="createdAt")
class Config:
populate_by_name = True # Accept both snake_case and camelCase
class MyUpdate(BaseModel):
"""All fields optional for PATCH requests."""
name: Optional[str] = Field(None, min_length=1)
description: Optional[str] = None
test cases passed, vs 4 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.