CtrlK
BlogDocsLog inGet started
Tessl Logo

pydantic-ai

Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.

55

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/pydantic-ai/SKILL.md

The canonical home for this skill is pydantic-ai in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Scale 1-5

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

This is a highly actionable skill with excellent, executable code examples covering PydanticAI's core features comprehensively. Its main weaknesses are verbosity (explaining things Claude already knows, like what PydanticAI is) and poor progressive disclosure — all content is crammed into one large file when examples, pitfalls, and advanced patterns could be split into supporting files. The workflow is logically sequenced but could benefit from explicit checkpoints.

Suggestions

Split the 3 full examples (Code Review, Retry Logic, Multi-Agent Pipeline), Common Pitfalls, and Security Notes into separate bundle files (e.g., EXAMPLES.md, PITFALLS.md) and reference them from the main SKILL.md to improve progressive disclosure.

Trim the Overview and 'When to Use This Skill' sections significantly — Claude doesn't need a paragraph explaining what PydanticAI is or bullet points about when type-safe outputs matter. A single sentence like 'PydanticAI: type-safe Python agent framework supporting structured outputs, DI, tools, and multi-model backends' suffices.

Condense the installation section to just `pip install pydantic-ai` with a note that provider extras exist (e.g., `pydantic-ai[openai]`) rather than listing every provider separately.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary verbosity. The 'Overview' paragraph explains what PydanticAI is at length (Claude likely knows this), the 'When to Use This Skill' section is somewhat redundant with the overview, and installation extras for every provider add bulk. However, the code examples themselves are reasonably tight.

3 / 5

Actionability

Excellent actionability — every step includes complete, executable Python code with imports, model definitions, and runnable examples. The examples cover the full spectrum from minimal agent to multi-agent pipelines, tool use, testing, streaming, and multi-turn conversations. Code is copy-paste ready.

5 / 5

Workflow Clarity

The steps are clearly sequenced from installation through increasingly complex patterns (minimal → structured output → tools → DI → testing → streaming → multi-turn). The retry/validation example includes a feedback loop via ModelRetry. However, there's no explicit validation checkpoint workflow for the overall agent-building process — e.g., 'verify your agent works before adding tools.' Since this isn't a destructive/batch operation skill, the missing validation doesn't cap the score.

4 / 5

Progressive Disclosure

All content is inlined in a single monolithic file (~300+ lines). The API reference details, multiple full examples, best practices, pitfalls, and security notes could be split into separate files. The 'Related Skills' section references other skills but there are no bundle files to offload detailed content. For a skill this long, the lack of any content splitting is a notable weakness.

2 / 5

Total

14

/

20

Passed

Description

58%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 names a specific framework (PydanticAI) and lists several concrete features, giving it reasonable specificity and distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for Claude's skill selection, and the trigger terms lean toward framework jargon rather than natural user language. Adding trigger guidance and more user-facing keywords would significantly improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PydanticAI, building type-safe AI agents, or using Pydantic for LLM tool calling.'

Include natural synonyms and related terms users might say, such as 'LLM agent', 'pydantic agent', 'agent framework', 'tool calling', or 'model-agnostic agents'.

Rephrase capabilities as actions Claude performs, e.g., 'Generates PydanticAI agent code, configures tool definitions, sets up dependency injection, and integrates multiple LLM providers.'

DimensionReasoningScore

Specificity

Lists several specific capabilities: 'type-safe tool use, structured outputs, dependency injection, and multi-model support.' These are concrete features, though they describe framework features rather than actions Claude performs (e.g., no verbs like 'generates', 'configures', 'debugs').

4 / 5

Completeness

The 'what' is reasonably clear — build AI agents with PydanticAI using specific features. However, there is no explicit 'when' clause (e.g., 'Use when...'), which per the rubric caps this dimension at 3.

3 / 5

Trigger Term Quality

Includes 'PydanticAI', 'AI agents', 'type-safe', 'structured outputs', 'dependency injection', and 'multi-model' — but misses natural user phrases like 'pydantic ai agent', 'LLM agent framework', 'agent tool calling', or synonyms a user might actually type when seeking help.

3 / 5

Distinctiveness Conflict Risk

Naming 'PydanticAI' specifically makes it fairly distinct from generic agent-building or other framework skills. However, terms like 'AI agents', 'structured outputs', and 'multi-model support' could overlap with skills for LangChain, CrewAI, or other agent frameworks.

4 / 5

Total

14

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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