FastAPI with Supabase and SQLAlchemy/SQLModel
35
32%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/supabase-python/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially just a technology stack label with no actions, capabilities, or trigger guidance. It fails to communicate what the skill does or when Claude should select it, making it very weak for skill selection among a large pool of available skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Scaffolds FastAPI applications with Supabase backend, defines SQLAlchemy/SQLModel database models, configures database connections, and creates CRUD API endpoints.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks to build a FastAPI app, set up a Supabase database, create REST API endpoints, or define SQLModel/SQLAlchemy models.'
Include natural keyword variations users might say, such as 'REST API', 'backend', 'database models', 'ORM', 'Python web app', 'CRUD operations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names technologies (FastAPI, Supabase, SQLAlchemy/SQLModel) but describes no concrete actions whatsoever. There are no verbs or capabilities listed—it reads as a topic label, not a capability description. | 1 / 3 |
Completeness | There is no 'what does this do' beyond naming technologies, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing. | 1 / 3 |
Trigger Term Quality | It includes relevant technology keywords (FastAPI, Supabase, SQLAlchemy, SQLModel) that users might naturally mention, but lacks common variations like 'API', 'REST', 'database', 'ORM', 'backend', or file extensions that would improve matching. | 2 / 3 |
Distinctiveness Conflict Risk | The specific combination of FastAPI + Supabase + SQLAlchemy/SQLModel is somewhat distinctive, but without describing what the skill actually does, it could overlap with any general Python web development or database skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable code covering the full FastAPI + Supabase + SQLModel stack, which makes it highly actionable. However, it is far too verbose for a skill file—most of the content is standard boilerplate that Claude can generate from brief instructions. The monolithic structure with no progressive disclosure means it consumes excessive context window for information that could be conveyed in a fraction of the tokens.
Suggestions
Reduce the SKILL.md to ~80-100 lines covering only the core principle (SQLAlchemy for queries, Supabase for auth/storage), the auth dependency pattern, the dual-client setup, and anti-patterns—move full route examples, test fixtures, and migration config to separate referenced files.
Remove boilerplate Claude already knows: pyproject.toml contents, basic FastAPI app setup, CORS middleware, standard CRUD patterns, and Alembic initialization steps.
Split detailed examples into referenced files like ROUTES.md, TESTING.md, and MIGRATIONS.md, with clear one-level-deep links from the main SKILL.md.
Add explicit validation checkpoints, e.g., 'verify Supabase connection with health check before proceeding' and 'run alembic check after migration to confirm schema matches models'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, presenting a full project scaffold that Claude could generate from minimal guidance. Most of this (project structure, pyproject.toml, CORS middleware, basic CRUD routes, test fixtures) is boilerplate Claude already knows. The entire content could be reduced to core principles, key patterns (auth dependency, dual client setup), and anti-patterns in under 100 lines. | 1 / 3 |
Actionability | All code examples are fully executable, copy-paste ready, and cover the complete stack from config through models, routes, migrations, storage, realtime, and testing. Specific commands for running, migrating, and testing are included. | 3 / 3 |
Workflow Clarity | The content follows a logical progression (setup → config → db → auth → routes → migrations → testing → running), but lacks explicit validation checkpoints. For example, the migration workflow lists commands but doesn't include verification steps, and there's no guidance on validating that auth is correctly configured or that the database connection works before proceeding. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of code with no references to external files. The project structure, full route implementations, test fixtures, migration config, storage helpers, and realtime examples are all inline. Much of this should be split into separate reference files (e.g., routes examples, testing setup, migration config) with the SKILL.md serving as a concise overview. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (711 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
65efb33
Table of Contents
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.