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.
64
47%
Does it follow best practices?
Impact
95%
1.75xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/supabase-automation/SKILL.mdQuality
Discovery
67%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 does a good job listing specific Supabase-related capabilities and identifying the tooling mechanism, making it distinctive. However, it lacks an explicit 'Use when...' clause, which weakens its completeness for skill selection. Some natural trigger terms users might use (e.g., 'rows', 'insert', 'RLS policies') are missing.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Supabase databases, managing tables, running SQL queries, uploading to Supabase storage, or deploying edge functions.'
Include additional natural trigger terms users might say, such as 'rows', 'insert', 'RLS', 'auth', 'buckets', 'migrations', or 'Supabase project'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: database queries, table management, project administration, storage, edge functions, and SQL execution. Also specifies the tooling (Rube MCP/Composio) and a procedural note about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with a list of capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain terms. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Supabase', 'database queries', 'SQL', 'storage', 'edge functions', but misses common user variations like 'rows', 'insert', 'RLS', 'auth', 'buckets', or '.sql'. The term 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Supabase' and 'Rube MCP (Composio)' creates a very clear niche. This is unlikely to conflict with generic database skills or other MCP-based skills due to the specific platform references. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%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 coverage of Supabase tools with well-structured workflow sequences and useful pitfall documentation. However, it is severely undermined by extreme verbosity, duplicated content (pitfalls repeated in each workflow AND a dedicated section, plus what appears to be corrupted content with the rubric embedded multiple times), lack of concrete executable examples, and a monolithic structure that should be split across multiple files.
Suggestions
Drastically reduce content length by removing duplicated pitfalls (keep only the consolidated 'Known Pitfalls' section or inline pitfalls, not both) and fix the corrupted content where the rubric is embedded within the skill.
Add at least one concrete, copy-paste-ready example showing a complete tool invocation with realistic parameter values and expected output format for the most common workflow (e.g., querying a table).
Split detailed parameter documentation and the quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with workflow sequences.
Add explicit validation steps for write operations: e.g., 'After INSERT/UPDATE, run a SELECT to verify the mutation succeeded' or 'Check affected row count in the SQL response'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely verbose and repetitive. Pitfalls and known issues are duplicated across workflow sections and then again in a dedicated 'Known Pitfalls' section. Parameter details that Claude could discover via RUBE_SEARCH_TOOLS are exhaustively listed inline. The document also appears to contain corrupted/duplicated content (the rubric itself is embedded multiple times within the skill content), making it massively bloated. | 1 / 3 |
Actionability | The skill provides specific tool names, parameter names, and filter operators, which is concrete guidance. However, there are no executable code examples or copy-paste-ready tool invocation examples showing actual parameter values. The guidance describes what tools to call but doesn't show a concrete example of a complete tool call with realistic parameters and expected output. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled as [Prerequisite], [Required], [Optional]. However, for database write operations (INSERT/UPDATE/DELETE via RUN_SQL_QUERY), there are no explicit validation checkpoints or feedback loops (e.g., verify schema before write, confirm row count after mutation). The rubric requires feedback loops for database operations to score 3. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload detailed content. The extensive parameter documentation, filter operator lists, pitfalls (repeated twice), and quick reference table are all inline in a single massive file. The detailed parameter specs for each workflow and the duplicated pitfalls section should be split into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.