Name: postgres-best-practices
Rating: 77 (1 reviews)
Author: administrakt0r

postgres-best-practices

Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

1.25x

Quality

74%

Does it follow best practices?

Impact

89%

1.25x

Average score across 3 eval scenarios

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/postgres-best-practices/SKILL.md

The canonical home for this skill is postgres-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

50%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 well-structured as an overview but is undermined by broken references (no rules/ directory or AGENTS.md exists), a duplicate vague 'When to Use' section, no inline executable SQL, and no validation steps for a destructive/batch database context.

Suggestions

Ship the referenced bundle (rules/*.md and AGENTS.md) or remove the references, since every cited path currently 404s and breaks progressive disclosure.

Delete the duplicate '## When to Use' section at the end whose boilerplate line adds no information.

Add a validation/verification checkpoint to the workflow (e.g., EXPLAIN ANALYZE before/after, or run in a transaction and rollback) since schema, index, and RLS changes are destructive/batch operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient (compact priority table, terse file listing) but includes unnecessary padding: a duplicate '## When to Use' section whose closing line 'This skill is applicable to execute the workflow or actions described in the overview' is vague boilerplate that earns no token.	3 / 5
Actionability	Provides concrete structural guidance (priority table, rule prefixes, description of each rule file's contents) but no executable SQL or commands, and the 'How to Use' merely directs to rule files that do not exist, leaving key execution details missing.	3 / 5
Workflow Clarity	A loose sequence is implied (identify category by priority -> read rule file -> apply) but there are no validation or verification checkpoints; since this is a database skill involving schema, index, and RLS changes (destructive/batch context), the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	The body is well-organized as an overview with clearly signaled one-level-deep references (rules/*.md, AGENTS.md), but no bundle files exist and every referenced path is broken, so navigation fails in practice rather than being merely a minor organization gap.	3 / 5
	Total	12 / 20 Passed

Description

87%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.

A strong description that explicitly answers both what and when with concrete, domain-specific trigger phrases and third-person voice. Minor gaps are missing synonyms (SQL, PostgreSQL, indexes) and somewhat generic action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations'), but the verbs are generic and coverage of optimization actions is not comprehensive enough for a 5.	4 / 5
Completeness	Clearly states what it does ('Postgres performance optimization and best practices from Supabase') and explicitly when to use it with concrete trigger phrases ('Use this skill when writing, reviewing, or optimizing...').	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Postgres queries, schema designs, database configurations, performance optimization') but misses common synonyms users would say like 'SQL', 'PostgreSQL', and 'indexes'.	4 / 5
Distinctiveness Conflict Risk	Clear Postgres-specific niche with Supabase attribution and distinct triggers; minimal risk of firing for an unrelated skill.	5 / 5
	Total	18 / 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/postgres-best-practices/SKILL.md
Commit: 64adc55

Reviewed: 8 minutes 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.