neon-postgres-egress-optimizer

Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.

Quality

88%

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

Quality

Content

77%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced workflow with executable SQL and a genuine verification loop. The main weakness is conciseness (some explanatory padding) and progressive disclosure, since all detail lives inline in a single long file.

Suggestions

Trim explanatory asides Claude already knows (e.g. 'This is easy to miss because the application may work fine with small datasets') to improve token efficiency.

Split the diagnostic query catalog and fix recipes into a reference file (e.g. references/diagnostic-queries.md) and keep SKILL.md as a lean overview, improving progressive disclosure.

Move the 'Further reading' links into the reference file or verify they resolve, since they point at .md documentation URLs that may not be the canonical paths.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and executable, but includes some unnecessary padding such as restating the problem framing ('This is easy to miss because...') and explanatory asides ('not a direct egress measure, but helps...') that Claude does not need.	2 / 3
Actionability	Provides copy-paste-ready, executable SQL for diagnostics and concrete before/after fixes for each anti-pattern, with no pseudocode.	3 / 3
Workflow Clarity	Clear four-step sequence (Diagnose, Analyze, Fix, Verify) with an explicit Verify step that resets stats, runs tests, and re-measures — a real feedback loop for database changes.	3 / 3
Progressive Disclosure	Well-organized sections, but it is a monolithic ~200-line SKILL.md with no references split out; the detailed diagnostic queries and fix recipes could live in a reference file with a lean overview.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description with explicit 'Use when' triggers, concrete actions, and natural user phrasing tied to a specific niche. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Diagnose and fix excessive Postgres egress', 'SELECT * optimization', 'query overfetching') tied to a specific domain rather than vague language.	3 / 3
Completeness	Explicit 'Use when...' clause answers both what (diagnose/fix egress) and when (high bills, egress spikes, cost-efficiency review), with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural phrases users would say — 'why is my Neon bill so high', 'database costs jumped', 'high database bills', 'egress spikes' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Neon/Postgres egress niche is distinct and the triggers (data transfer costs, Neon bill) are unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: openai/plugins
Path: plugins/neon-postgres/skills/neon-postgres-egress-optimizer/SKILL.md
Commit: 11c74d6

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