Name: supabase
Rating: 56.8 (1 reviews)
Author: membranedev

supabase

Supabase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Supabase data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is a solid, actionable CLI integration guide with concrete commands and a well-structured connection state machine including feedback loops. Its main weaknesses are an unnecessary introductory explanation of what Supabase is, a broken "Step 2" reference, and no validation guidance around destructive action runs.

Suggestions

Cut the opening "Supabase is an open-source Firebase alternative..." paragraph and the Database/Table/Row overview tree; Claude already knows this and they consume context without adding actionability.

Fix the broken "skip to Step 2" reference by labeling the sections as Step 1 / Step 2 (or relinking to the "Searching for actions" heading) so the sequence is unambiguous.

Add a validation checkpoint before destructive action runs, e.g. "For DELETE/UPDATE actions, run a confirming SELECT or dry-run first and confirm the affected row count with the user before executing."

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Supabase is an open-source Firebase alternative...") and the Database/Table/Row overview explain concepts Claude already knows, and "Popular actions" repeats the action-list command; the bulk is operational and efficient, so it is mostly efficient with some removable padding rather than severely verbose.	3 / 5
Actionability	Concrete, executable commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flag table and JSON-input example; not a 5 because there is no single end-to-end worked example tying the steps together with concrete values.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear and the connection flow has real feedback loops (poll --wait, handle CLIENT_ACTION_REQUIRED, inspect the error field); not a 5 because "skip to Step 2" references an unlabeled step and running potentially destructive actions has no pre-run validation checkpoint.	4 / 5
Progressive Disclosure	A single well-organized file with clear ## / ### sections and no nested references; not a 5 because at >50 lines the full proxy flag table and connection state-machine details are inlined rather than split into one-level-deep reference files, and no external reference exists for the action catalog.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is functional — it names Supabase explicitly and includes a usable "Use when" trigger — but its capability list ("manage data, records, automate workflows") is generic and lacks concrete actions and synonyms (Postgres, tables, SQL). It is clearly distinguishable yet could be sharper and more specific.

Suggestions

Replace generic verbs with concrete Supabase actions, e.g. "Query and mutate tables, manage auth users, and upload storage files" so specificity reaches the top anchor.

Add natural synonyms and file/term variations users actually say — "Postgres", "database", "tables", "SQL", ".sql" — to broaden trigger coverage.

Expand the "Use when" clause with multiple concrete triggers, e.g. "Use when the user wants to query a Supabase database, manage rows, handle authentication, or read/write storage buckets."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Supabase domain plus a couple of actions, but the actions are generic rather than concrete (cf. "extract text, fill forms, merge documents"); not a 2 because at least two named actions are present, not a 4 because none are truly specific.	3 / 5
Completeness	It answers "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Supabase data"); not a 5 because the "what" actions are generic and only a single trigger phrase is given rather than concrete triggers.	4 / 5
Trigger Term Quality	The natural term "Supabase" plus "data" and "records" are present in "interact with Supabase data", but common synonyms users say (Postgres, database, tables, SQL, queries) are missing; not a 4 because keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the distinct product "Supabase" gives it a clear niche with low conflict risk, but the broad "manage data, records, automate workflows" framing could overlap with a generic database skill; not a 5 because the action wording is not tightly scoped to Supabase-specific triggers.	4 / 5
	Total	14 / 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: membranedev/application-skills
Path: skills/supabase/SKILL.md
Commit: f484c82

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