agentleFS
dperezcabreradperezcabrera/pico-skills/.claude/skills/add-validation/SKILL.md

add-validation

Skill4 starsChanged 4 months agoMITView on GitHub

Add Pydantic validation to component methods with pico-pydantic. Use when adding input validation to services or API handlers.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add Pydantic validation to: $ARGUMENTS

    line 10
  2. Distinctive:

    Read the codebase to understand existing models and patterns, then add validation.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add Validation

Add Pydantic validation to: $ARGUMENTS

Read the codebase to understand existing models and patterns, then add validation.

Basic Usage

@validate automatically validates and transforms Pydantic BaseModel parameters. Dicts are converted to model instances.

from pydantic import BaseModel, Field
from pico_ioc import component
from pico_pydantic import validate

class CreateUserRequest(BaseModel):
    name: str = Field(min_length=1, max_length=100)
    email: str
    age: int = Field(gt=0, lt=150)

@component
class UserService:
    @validate
    async def create_user(self, data: CreateUserRequest) -> User:
        return User(name=data.name, email=data.email, age=data.age)

Both of these work:

await service.create_user({"name": "Alice", "email": "a@b.com", "age": 30})
await service.create_user(CreateUserRequest(name="Alice", email="a@b.com", age=30))

Multiple Validated Parameters

class QueryParams(BaseModel):
    limit: int = Field(default=10, gt=0, le=100)
    offset: int = Field(default=0, ge=0)

@component
class SearchService:
    @validate
    async def search(self, query: str, params: QueryParams) -> list:
        ...

Error Handling

from pico_pydantic import ValidationFailedError

try:
    await service.create_user({"name": "", "age": -1})
except ValidationFailedError as e:
    print(f"Method: {e.method_name}")
    print(f"Error: {e.pydantic_error}")

Checklist

  • Pydantic BaseModel defined with field constraints
  • @validate on methods receiving external/untrusted data
  • ValidationFailedError handled at API boundary

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.