CtrlK
BlogDocsLog inGet started
Tessl Logo

supabase-automation

Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.

85

1.75x
Quality

Does it follow best practices?

Impact

95%

1.75x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A highly actionable, well-sequenced reference for Supabase MCP operations with strong workflow validation and error-recovery guidance. It is held back by duplicated pitfall content and a monolithic single-file structure with no progressive disclosure to separate reference files.

Suggestions

Remove the consolidated 'Known Pitfalls' section (or reduce it to a one-line cross-reference), since the same pitfalls are already covered in each workflow's 'Pitfalls' block — this removes ~40 lines of repetition.

Move the per-tool parameter reference and/or Quick Reference table into a separate referenced file (e.g. references/tools.md) and keep SKILL.md as a concise overview with one-level-deep links to improve progressive disclosure.

Add an explicit post-write verification step in the SQL workflow (e.g. re-query affected rows or check return counts) to strengthen the feedback loop for destructive operations.

DimensionReasoningScore

Conciseness

The body is largely concrete reference material with no basic-concept padding, but the consolidated 'Known Pitfalls' section repeats pitfalls already stated per-workflow (project_ref format, array syntax, case-sensitive identifiers, ERROR 42P01/42883, API-key handling) and the Quick Reference table re-lists tools, so it could be tightened.

2 / 3

Actionability

Gives concrete, copy-paste-ready guidance: exact tool slugs in numbered sequences, named parameters with types, value patterns ('^[a-z]{20}$'), filter operators, and SQL syntax — specific enough to act on directly.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with [Prerequisite]/[Required]/[Optional] tags, explicit validation checkpoints ('Confirm connection status shows ACTIVE before running any workflows', inspect schemas before writes, read_only:true), and error-code → remediation feedback (ERROR 42P01/42883).

3 / 3

Progressive Disclosure

Well organized into sections, but it is a single ~233-line monolithic file with no bundle files and no one-level-deep references; the detailed parameter reference and Quick Reference table are inline content that could be split out for clearer progressive disclosure.

2 / 3

Total

10

/

12

Passed

Description

82%

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 specific, third-person description that names concrete Supabase capabilities and a clear tooling niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to query or manage a Supabase database, inspect schemas, run SQL, or administer Supabase projects/organizations/storage/edge functions.' to raise completeness to 3.

Include a few more natural phrasings users might say (e.g. 'Supabase tables', 'run SQL on Supabase', 'list Supabase projects') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'database queries, table management, project administration, storage, edge functions, and SQL execution' — matching the anchor for enumerating specific capabilities.

3 / 3

Completeness

Clearly states what the skill does, but lacks a 'Use when...' clause or equivalent explicit trigger guidance; per the rubric, a missing explicit-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a user would actually say ('Supabase', 'database queries', 'SQL execution', 'storage', 'edge functions') with good coverage rather than abstract jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and explicit ('Supabase ... via Rube MCP (Composio)'), making it unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

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.