Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/pydantic-models-py
Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants.
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
and 18 more in the full report
13 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should newly created Pydantic resource models be defined and exported in a standard FastAPI backend project folder structure?
| Checked | Without skill | With skill |
|---|---|---|
| Models are created in src/backend/app/models/. | Missed | Passed |
| Models are exported from src/backend/app/models/__init__.py. | 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 |
from datetime import datetime
from pydantic import BaseModel, ConfigDict, Field
class MyModel(BaseModel):
model_config = ConfigDict(populate_by_name=True)
workspace_id: str = Field(..., alias="workspaceId")
created_at: datetime = Field(..., alias="createdAt")
class MyUpdate(BaseModel):
model_config = ConfigDict(populate_by_name=True)
test cases passed, vs 8 / 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.