SKILLEMALL.ai
GitHub ↗ RU Sign in

BC supabase

Set up, extend, or audit Supabase schema, grants, RLS, migrations, typed clients, storage, and external auth. Use when integrating Supabase or repairing data access and tenant isolation.

tushaarmehtaa/tushar-skills Agent Skills author: tushaarmehtaa 1 file body ≈ 738 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Set up, extend, or audit Supabase schema, grants, RLS, migrations, typed clients, storage, and external auth.

As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice

AnalyzerSupabaseSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: supabase (tushaarmehtaa/tushar-skills)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 17): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 63/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 6 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 738 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 186: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 11 items
    • +3Output format is stated explicitly
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.