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 with the guarded engine migration. Detection is one engine-free command; the install ladder is one flag.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin-variants/gbrain-coding/skills/postgres-adopt/SKILL.md

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable runbook with a clear sequenced workflow and proper validation/feedback for destructive operations. It is well-structured and self-contained, with only minor conciseness and actionability gaps.

Dimension	Reasoning	Score
Conciseness	Lean and action-oriented with no padding of concepts Claude already knows; minor over-explanation in the intro blockquote and 'The tradeoff' section that could be trimmed slightly.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready commands (gbrain engine status --json, gbrain init --prefer-postgres, gbrain migrate --to supabase --url …, gbrain doctor) with branch logic; the placeholder <postgres-connection-string> and described-but-not-scripted ladder rungs are minor gaps.	4 / 5
Workflow Clarity	Clear three-step sequence (Detect → Fresh install → Migrate) with explicit validation checkpoints (probe, gbrain doctor after clean run, partial-run resume manifest) and feedback loops for the destructive migration, satisfying the destructive-op validation requirement.	5 / 5
Progressive Disclosure	Single well-organized file with clearly labeled sections and one clearly-signaled one-level cross-link (../db-repair/SKILL.md); good structure with only minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 is highly specific and distinctive, naming concrete actions and domain terms. Its main gap is the absence of an explicit 'Use when…' trigger clause within the description text itself, which caps completeness even though a separate triggers field exists.

Suggestions

Add an explicit 'Use when…' clause to the description (e.g., 'Use when the operator asks which gbrain engine is active or wants to move a PGLite brain to Postgres') so the 'when' lives in the description, not only in the triggers field.

Fold one or two of the most natural user phrases from the triggers list ('upgrade to postgres', 'switch gbrain to postgres') into the description body to strengthen trigger-term coverage there.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Detect which gbrain engine is in use', 'install/provision Postgres (Supabase discovery via SUPABASE_ACCESS_TOKEN, local Postgres, opt-in Docker)', and 'move an existing PGLite brain with the guarded engine migration' — with comprehensive coverage of the skill's surface.	5 / 5
Completeness	The 'what' is clear and detailed, but the description text has no explicit 'Use when…' clause — the 'when' is only weakly implied, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good keyword coverage with natural domain terms (gbrain engine, PGLite vs Postgres, Supabase, Docker), but the description text alone misses some common user phrasings that live in the separate triggers field rather than the description itself.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (gbrain engine adoption, PGLite↔Postgres, Supabase) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: garrytan/gbrain
Path: plugin-variants/gbrain-coding/skills/postgres-adopt/SKILL.md
Commit: e78f1c3

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.