fastapi-backend-skill

Create and manage FastAPI routes, dependencies, and models

Install with Tessl CLI

npx tessl i github:WajahatAli3218664/Hackathon-02-mytodo --skill fastapi-backend-skill

What are skills?

Overall
score

61%

Review — 49%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

33%

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 the FastAPI domain and lists core components but lacks explicit trigger guidance ('Use when...'), which significantly limits Claude's ability to know when to select this skill. The trigger terms are adequate but could include more natural user language variations. The description is concise but incomplete for skill selection purposes.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building REST APIs with FastAPI, creating async endpoints, or when the user mentions FastAPI, Pydantic models, or dependency injection.'

Include additional natural trigger terms users might say: 'REST API', 'API endpoints', 'Pydantic', 'async API', 'Python web API', '.py API files'

Expand specific actions to differentiate from other frameworks: 'Define Pydantic request/response models, configure dependency injection, set up async route handlers, add OpenAPI documentation'

Dimension	Reasoning	Score
Specificity	Names the domain (FastAPI) and lists some actions (create, manage routes, dependencies, models), but lacks comprehensive detail about specific operations like authentication, middleware, or validation.	2 / 3
Completeness	Only answers 'what' (create and manage FastAPI components) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'FastAPI', 'routes', 'dependencies', and 'models' which are relevant keywords, but misses common variations like 'API endpoints', 'REST API', 'Pydantic', or 'async endpoints' that users might naturally say.	2 / 3
Distinctiveness Conflict Risk	'FastAPI' is specific enough to distinguish from general web frameworks, but 'routes', 'dependencies', and 'models' are generic terms that could overlap with Django, Flask, or other Python web framework skills.	2 / 3
	Total	7 / 12 Passed

Implementation

65%

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

This skill provides solid, actionable FastAPI guidance with executable code examples that cover common patterns well. However, it suffers from some redundancy (the complete CRUD example duplicates earlier snippets), lacks validation/testing checkpoints in the workflow, and could benefit from better progressive disclosure by splitting detailed examples into separate files.

Suggestions

Add validation steps to the 'Creating a New Route' workflow, such as 'Test the endpoint with curl or the /docs UI before proceeding'

Remove or consolidate the duplicate CRUD example at the end, or move it to a separate EXAMPLES.md file with a clear reference link

Add a brief testing section or link showing how to verify routes work (e.g., pytest example or manual /docs testing)

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary verbosity like the full project structure that Claude could infer, and the 'Instructions' header adds no value. The complete CRUD example at the end largely duplicates earlier content.	2 / 3
Actionability	Provides fully executable, copy-paste ready code examples throughout. All code snippets are complete with proper imports, type hints, and realistic implementations for Pydantic models, service layers, routes, and configuration.	3 / 3
Workflow Clarity	The 4-step process for creating a new route is clearly sequenced, but lacks validation checkpoints. No mention of testing routes, validating the API works, or error recovery steps after making changes.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline in one file. The complete CRUD example could be a separate reference file, and there are no links to external documentation for advanced topics like testing or deployment.	2 / 3
	Total	9 / 12 Passed

Validation

91%

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

Reviewed: 8 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.