SKILLEMALL.ai
GitHub ↗ RU Sign in

CD supabase-cli

This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.

fcakyon/claude-codex-settings Agent Skills author: fcakyon 57 files body ≈ 1 424 tokens Open the sourcegithub.com↗ analyzed 7 h ago

This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase…

As a process D 36/100 · Unfinished process — weak spots: steps, result and completion, when it triggers

IntegrationSupabaseInfrastructureOperations and projectsSoftware developmenttype 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
C
87/100
safety, quality, tests
Safety 60%
92
Quality 40%
80
Run on models
none yet
Process rating
D
36/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 4

    ✓ No critical or high findings

    Medium and low: 4
    • medium Dangerous commands cmd-pipe-to-shell-known-host references/overview.md:29
      Pipe-to-shell installer from a well-known host (still executes remote code)
      curl -fsSL https://raw.githubusercontent.com/supabase/cli/main/install | bash
    • low Obfuscation obf-base64-blob references/examples.yaml:89
      Long base64-looking blob (test fixture / example file)
      service_role key: eyJh…1IU
      fixture
    • low Obfuscation obf-base64-blob references/examples.yaml:100
      Long base64-looking blob (test fixture / example file; quoted — discussed, not commanded)
      SERVICE_ROLE_KEY="eyJh…1IU"
      fixturequoted
    • low Obfuscation obf-base64-blob references/examples.yaml:111
      Long base64-looking blob (test fixture / example file; quoted — discussed, not commanded)
      SUPABASE_SERVICE_KEY="eyJh…1IU"
      fixturequoted

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "references"

    Process rating: all ten parameters 36/100

    • 0Steps. Prose only: no discrete steps
    • 0Result and completion. Does not say what the result is
    • 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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1424 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 259: enough signal without eating the budget
    • +4Structure: 17 headings
    • +4Has examples (13 code blocks)
    • +1License stated

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