BD supabase-config
Change hosted Supabase Auth settings safely: read, diff, PATCH only named keys (writes remote config). Use when config push or a redirect broke magic links. Trigger on "magic link goes to localhost".
Change hosted Supabase Auth settings safely: read, diff, PATCH only named keys (writes remote config).
As a process D 49/100 · Unfinished process — References files that are not bundled: templates/config.toml
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/config.toml
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: templates/config.toml
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 32 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4065 tokens
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 199: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (5 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.