Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

supabase

Core Supabase CLI, migrations, RLS, Edge Functions

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/supabase/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

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

A highly actionable, executable reference with strong security-conscious defaults (RLS-on-all-tables, service-key warnings) and a well-sequenced migration workflow gated by CI validation. Its main weaknesses are the total absence of progressive disclosure — everything lives inline in one long SKILL.md with no references/ files — and minor verbosity in the overview sections.

Suggestions

Split bulk reference material (the RLS policy catalog, CI/CD template, and Edge Function examples) into references/ files linked from short sections in SKILL.md, keeping the core as an overview.

Add an explicit verification step after "supabase db push" (e.g. check "supabase migration list" or smoke-test the deployed schema) to close the workflow's validation loop.

Trim the Supabase stack table and Sources section, which restate knowledge Claude already has, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is a dense, command-first reference that assumes Claude's competence ("Core Principle: Local-first, migrations in version control, never touch production directly") with almost no concept explanation; the Supabase stack table and Sources line are minor instances that could be trimmed, keeping it below the lean 5 anchor.	4 / 5
Actionability	Guidance is fully executable throughout: complete CLI commands with expected outputs ("supabase start" port listing), copy-paste SQL for RLS policies and triggers, runnable TypeScript Edge Function templates, and a full GitHub Actions workflow covering the common cases.	5 / 5
Workflow Clarity	The migration workflow presents three clearly sequenced options with checkpoints ("Review generated SQL", "supabase db reset" to test, "supabase db lint" gating the CI deploy job); a minor gap is the absence of an explicit post-push verification step after "supabase db push", so it does not reach the 5 anchor.	4 / 5
Progressive Disclosure	Sections are clearly headed and easy to scan, but there are no bundle files at all: ~420 lines are inlined monolithically, including a full CI/CD template and an RLS policy library that clearly belong in separate reference files, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%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.

A compact, domain-anchored description that names concrete capability areas with good natural keywords, but it is a noun-phrase fragment rather than a capability statement and omits any explicit 'when to use' trigger guidance in the description field itself. Folding the existing when-to-use clause into the description would resolve the main gap.

Suggestions

Rewrite the description as a full third-person capability statement, e.g. "Manages Supabase projects via the CLI: local development, migrations, RLS policies, Edge Functions, and deployment".

Add an explicit trigger clause to the description (e.g. "Use when working with Supabase — database, auth, storage, or edge functions") instead of relying on the separate when-to-use frontmatter field.

Include natural synonyms and extensions users would say (Postgres, .sql migrations, Deno functions) to lift trigger-term coverage from good to comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and lists four concrete capability areas ("Supabase CLI, migrations, RLS, Edge Functions"), matching the anchor for several specific items with minor gaps; not 5 because these are topic nouns rather than concrete actions.	4 / 5
Completeness	The description field conveys a clear 'what' but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline (the separate when-to-use frontmatter field is not part of the evaluated description).	3 / 5
Trigger Term Quality	"Supabase", "migrations", "RLS", and "Edge Functions" are natural terms users would say, giving good keyword coverage; missing common synonyms such as Postgres/auth/storage and any file extensions, so short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The description is firmly anchored to the distinct Supabase niche, but generic tokens like "migrations" carry minor overlap risk with general database-migration skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alinaqi/maggy
Path: skills/supabase/SKILL.md
Revision: 55aabe2

Reviewed: 26 days ago

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.

supabase

Table of Contents

Is this your skill?