SKILLEMALL.ai

BC postgres-adopt

Detect which gbrain engine is in use (PGLite vs Postgres), prefer Postgres for agent-harness installs, install/provision Postgres (Supabase discovery via SUPABASE_ACCESS_TOKEN, local Postgres, opt-in Docker), and move an existing PGLite brain to Postgres with its history (plan, ask, run). Detection is one engine-free command; the install ladder is one flag.

garrytan/gbrain Agent Skills author: garrytan MIT 1 file body ≈ 1 931 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Detect which gbrain engine is in use (PGLite vs Postgres), prefer Postgres for agent-harness installs, install/provision Postgres (Supabase discovery via…

As a process C 55/100 · Has gaps — References files that are not bundled: ../db-repair/SKILL.md, ../conventions/agent-operator-protocol.md

AnalyzerDockerPostgreSQLSupabaseInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: ../db-repair/SKILL.md, ../conventions/agent-operator-protocol.md
Tools and files w 18
0
Inputs and preconditions w 11
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: postgres-adopt (garrytan/gbrain)

How to improve

  1. The text references files that are not there: add them or drop the references.
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

  • warning missing-ref reference to a missing file: ../db-repair/SKILL.md
  • warning missing-ref reference to a missing file: ../conventions/agent-operator-protocol.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "mutating"
  • note frontmatter-key unknown frontmatter key "brain_first"

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../db-repair/SKILL.md, ../conventions/agent-operator-protocol.md
  • 0Tools and files. 2 referenced file(s) missing: ../db-repair/SKILL.md, ../conventions/agent-operator-protocol.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 30 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1931 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 359: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 30 items
  • +3Output format is stated explicitly
  • +4Has examples (6 code blocks)

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