supabase-python

FastAPI with Supabase and SQLAlchemy/SQLModel

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The skill is highly actionable with complete, executable code across the stack, but it is monolithic—everything lives inline in SKILL.md with no external references—and workflow steps for migrations and destructive DB operations lack explicit validation checkpoints.

Suggestions

Move boilerplate reference material (full models, alembic env, conftest, API route sets) into files under references/ and link to them one level deep, keeping SKILL.md an overview.

Add explicit validation checkpoints to the migration and testing workflows (e.g. run alembic check / alembic history, assert schema state) with fix-and-retry feedback loops for destructive ops.

Tighten or remove framework boilerplate that restates what Claude already knows (pydantic-settings Config class, basic CORS setup) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code over prose, but it embeds full reference-style blocks (entire config, models, alembic env, conftest) that largely restate framework boilerplate Claude already knows, so it could be tightened.	2 / 3
Actionability	Code blocks are concrete, executable, and copy-paste ready across setup, DB, auth, routes, storage, realtime, testing, and running, with specific commands and versions.	3 / 3
Workflow Clarity	Sections are well-ordered, but database/migration and destructive operations (alembic downgrade, drop_all) lack explicit validation checkpoints or feedback loops, capping workflow clarity at 2 per the rubric note.	2 / 3
Progressive Disclosure	It is a single monolithic SKILL.md with no bundle files (references/scripts/assets absent) and no one-level-deep references, so detailed reference material that should be split out is inline.	2 / 3
	Total	9 / 12 Passed

Description

45%

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 is a terse stack label rather than an action-oriented capability statement; it omits concrete verbs and any 'Use when...' trigger, relying on the separate when-to-use field. It is distinctive but under-specific.

Suggestions

Rewrite as action-oriented capabilities, e.g. 'Build FastAPI apps with Supabase Auth/storage and SQLAlchemy/SQLModel database access. Use when scaffolding a Python/FastAPI service backed by Supabase.'

Add an explicit 'Use when...' trigger clause inside the description field itself rather than only in when-to-use.

Use third-person action verbs ('Builds', 'Scaffolds') and concrete capabilities (auth, storage, realtime, migrations) to lift specificity.

Dimension	Reasoning	Score
Specificity	The description 'FastAPI with Supabase and SQLAlchemy/SQLModel' names a stack but states zero concrete actions, reading like a title rather than a capability list.	1 / 3
Completeness	It names the stack (what), and the separate when-to-use field provides the trigger, but the description field itself lacks any 'Use when...' clause, capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	It includes naturally-occurring terms (FastAPI, Supabase, SQLAlchemy, SQLModel, Python) but is missing common action-oriented phrasings a user would say (e.g. 'build an API', 'add auth').	2 / 3
Distinctiveness Conflict Risk	The combination of FastAPI + Supabase + SQLAlchemy/SQLModel defines a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.