postgresql

Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

Quality

66%

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 ./skills/postgresql/SKILL.md

Quality

Content

72%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 content is highly actionable and mostly token-efficient, with concrete SQL and copy-paste examples throughout. Its main gaps are the lack of an explicit validation feedback loop for destructive DDL and the absence of progressive disclosure — everything lives in one large inline file with no supporting references.

Suggestions

Add an explicit validation checkpoint to the workflow (e.g., 'Apply changes in staging, validate with EXPLAIN and test queries, then promote to production with a rollback plan') to lift workflow clarity above the destructive-operation cap.

Split the large reference into one-level-deep bundle files (e.g., references/data-types.md, references/indexing.md, references/partitioning.md) and link them from SKILL.md so the overview stays lean.

Trim a few explanatory parentheticals that restate general database behavior Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is dense, reference-style guidance that mostly assumes Claude's competence and avoids generic concept explanations; a few parenthetical asides (e.g., "unlike some databases that silently truncate or round") could be trimmed, placing it at anchor 4 rather than a fully lean 5.	4 / 5
Actionability	Provides specific SQL syntax, named data types and index types, and three copy-paste-ready CREATE TABLE examples (users, orders, JSONB profiles) covering common cases, matching the fully-executable anchor 5.	5 / 5
Workflow Clarity	The Instructions section gives a clear 5-step sequence with some validation (EXPLAIN in step 3, staging in Safety), but because the work involves destructive DDL there is no explicit validate-then-proceed checkpoint/feedback loop, so per the feedback-loops note workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	The skill has clear section headers and good internal organization, but it is a ~230-line monolithic file with no bundle files or one-level-deep references, so content that could be split (data types, indexing, partitioning) is fully inlined, fitting anchor 3.	3 / 5
	Total	15 / 20 Passed

Description

61%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 clearly states what the skill does and targets a distinct PostgreSQL niche, but it omits any "Use when..." trigger guidance and relies on topic categories rather than concrete actions. Adding explicit trigger phrases and a few synonyms (e.g., "Postgres") would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when designing or reviewing a PostgreSQL schema, choosing data types, or planning indexes/partitions').

Include the common alias 'Postgres' and concrete action verbs (e.g., 'Design, review, and optimize PostgreSQL schemas') to improve trigger-term quality and specificity.

Tighten the topic list into concrete actions so the description reads as capabilities rather than a table of contents.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ("Design a PostgreSQL-specific schema") and enumerates coverage areas ("data types, indexing, constraints, performance patterns, and advanced features"), but these are topic categories rather than multiple distinct concrete actions, so it sits at the anchor-3 level rather than 4.	3 / 5
Completeness	The "what" is clear (design a PostgreSQL schema with the listed coverage), but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a developer would say ("PostgreSQL", "schema", "data types", "indexing", "constraints") with good coverage; the common alias "Postgres" and phrases like "database schema design" / "DDL" are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"PostgreSQL-specific schema" carves a clear niche with low conflict risk against non-PostgreSQL skills, though without explicit trigger phrases it could still mildly overlap a general database-modeling skill, fitting anchor 4 rather than 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/postgresql/SKILL.md
Commit: 3eff4af

Reviewed: 23 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.