postgresql

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

Quality

74%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/postgresql/SKILL.md

The canonical home for this skill is postgresql in rmyndharis/antigravity-skills

Quality

Content

78%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 comprehensive, actionable PostgreSQL schema-design reference with executable examples and a reasonable validation-aware workflow. Its main weakness is monolithic structure: large reference sections are inlined rather than split into well-signaled external files.

Suggestions

Move the long Data Types and JSONB Guidance sections into separate reference files (e.g., references/data-types.md, references/jsonb.md) and link to them from SKILL.md to improve progressive disclosure.

Make the Instructions workflow explicit with a validate->fix->retry loop (e.g., run EXPLAIN, inspect plan, adjust index, re-run) to reach full workflow clarity for destructive/batch DDL.

Tighten explanatory asides such as the sequence-gap note to reduce tokens where the behavior is already implied by the rule.

Dimension	Reasoning	Score
Conciseness	Dense bullet-point reference with concrete syntax throughout and only minor over-explanation (e.g., the sequence-gap aside); mostly lean with a few explanatory asides that could be trimmed but the bulk earns its tokens.	4 / 5
Actionability	Provides copy-paste-ready CREATE TABLE/index examples plus concrete SQL syntax and operator guidance (GIN/GiST, ON CONFLICT, EXCLUDE) covering the common design cases.	5 / 5
Workflow Clarity	A clear 5-step Instructions sequence with validation checkpoints ("validate with EXPLAIN", staging validation, rollback plan in Safety), but no explicit validate->fix->retry feedback loop in the workflow itself.	4 / 5
Progressive Disclosure	Well-organized section headers exist, but the ~225-line body inlines substantial reference material (Data Types, JSONB Guidance) that could live in separate one-level-deep reference files, and no external references are signaled.	3 / 5
	Total	16 / 20 Passed

Description

70%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 communicates a PostgreSQL-specific schema-design niche with concrete topic coverage, but it lacks any explicit "Use when..." trigger guidance. Adding when-to-use phrasing would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when designing or reviewing PostgreSQL table schemas, choosing data types, or planning indexes/partitions') to answer both what and when.

Include the synonym 'Postgres' and natural terms like 'tables' alongside 'PostgreSQL' and 'schema' for broader trigger coverage.

Reframe topic areas as concrete actions ('Designs tables, selects data types, plans indexes and partitions') to lift specificity from topic-listing to action-listing.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas — "data types, indexing, constraints, performance patterns, and advanced features" — but frames them as topics covered rather than multiple concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does ("Design a PostgreSQL-specific schema. Covers...") but provides no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like "PostgreSQL", "schema", "data types", "indexing", and "constraints" that users would say, but misses common synonyms such as "Postgres" and "tables".	4 / 5
Distinctiveness Conflict Risk	The narrow "PostgreSQL-specific schema" niche with explicit topic coverage is clearly distinguishable from generic SQL or other-database skills and carries minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/postgresql/SKILL.md
Commit: 57c135b

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