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

87%

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

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

A high-quality, immediately actionable skill: executable SQL and commands throughout, a clearly sequenced four-step workflow with a real verify-and-measure feedback loop, and disciplined conciseness. The only structural gap is the absence of any progressive-disclosure layer — the anti-pattern catalog and the neon.ts IaC section are inline monoliths that could be split into reference files.

Suggestions

Move the five anti-pattern before/after examples into a references/anti-patterns.md file, keeping one-line summaries in SKILL.md, so the overview stays lean.

Move the neon.ts infrastructure-as-code section into the parent neon skill or a references file and keep a single pointer in SKILL.md, since it addresses compute/storage costs rather than egress.

Trim restated conclusions (e.g., the 'No duplication.' recap after the JOIN-split example) to lift conciseness to fully lean.

Dimension	Reasoning	Score
Conciseness	The body is code-first and lean: diagnostic SQL, before/after pairs, and a tight neon.ts snippet with no padding or explanation of concepts Claude already knows. It is not a 5 because a few sentences restate the obvious ("Two queries instead of one JOIN. The product data is fetched once. The reviews are fetched once. No duplication.") and the neon.ts infrastructure section repeats its rationale twice.	4 / 5
Actionability	Everything is executable: ready-to-run pg_stat_statements queries ("SELECT query, calls, rows AS total_rows, rows / calls AS avg_rows_per_call FROM pg_stat_statements WHERE calls > 0 ORDER BY rows DESC LIMIT 10"), CREATE EXTENSION, reset/re-measure commands, bash install/apply commands, and a complete neon.ts config. Before/after examples cover the common anti-patterns (SELECT *, missing pagination, JOIN duplication, application-side aggregation).	5 / 5
Workflow Clarity	The four steps are explicitly sequenced ("Work the four steps in order: diagnose... analyze... fix... verify") and Step 4 is a genuine validation feedback loop: run existing tests, check response shapes, then "reset it (SELECT pg_stat_statements_reset();), let traffic run, then re-run the diagnostic queries to compare before and after". Edge cases (missing extension, empty stats after scale-to-zero) are handled with explicit recovery paths.	5 / 5
Progressive Disclosure	The single-file body is well organized into clear sections with one-level-deep, clearly signaled references to the parent `neon` skill and two external doc URLs; no nested-reference indirection exists. It is not a 5 because there is no reference layer at all — the anti-pattern catalog and the neon.ts infrastructure section are sizeable bodies of content that could live in separate reference files, and the neon.ts section is tangential to egress diagnosis.	4 / 5
	Total	18 / 20 Passed

Description

86%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 with excellent, natural trigger terms and an explicit, well-scoped 'Use when' clause. Its main weakness is that 'diagnose and fix' understates the full capability set, and the cost-efficiency broadening clause slightly widens the trigger surface beyond the egress niche.

Suggestions

List the full capability set in the what-clause (e.g., 'Diagnose top egress queries via pg_stat_statements, analyze the codebase for overfetching anti-patterns, apply fixes (column selection, pagination, caching, aggregation pushdown, JOIN splitting), and verify the transfer drop') to lift specificity.

Tighten the closing broadening clause ('Also use when reviewing query patterns for cost efficiency') to explicitly anchor it to data transfer or Postgres to reduce overlap with general query-optimization skills.

Dimension	Reasoning	Score
Specificity	"Diagnose and fix excessive Postgres egress (network data transfer) in a codebase" names the domain and exactly two concrete actions (diagnose, fix), matching the '1-2 concrete actions but not comprehensive' anchor. It is not a 4 because the description never mentions the other capabilities the skill actually performs (analyze the codebase, verify fixes, caching/pagination/JOWN restructuring).	3 / 5
Completeness	It clearly answers both what ("Diagnose and fix excessive Postgres egress (network data transfer) in a codebase") and when ("Use when a user mentions high database bills... or wants to reduce data sent from their database to their application"), with concrete trigger phrases throughout. The broadening clause ("Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress") further strengthens the when.	5 / 5
Trigger Term Quality	The description covers natural terms comprehensively with synonyms: "high database bills", "egress spikes", "why is my Neon bill so high", "database costs jumped", "SELECT * optimization", "query overfetching", "reduce Neon costs", "optimize database usage". These are phrases a real user would naturally say, including exact quoted utterances.	5 / 5
Distinctiveness Conflict Risk	The niche is clear (Postgres/Neon egress and data-transfer costs) and triggers are distinct from generic skills. It is not a 5 because the broadening clause ("reviewing query patterns for cost efficiency") and terms like "optimize database usage" create minor overlap risk with the closely related parent `neon` skill and general query-optimization skills.	4 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: stevenknowswhy/ProfessionalBuyer
Path: .agents/skills/neon-postgres-egress-optimizer/SKILL.md
Commit: 92cff92

Reviewed: 6 hours 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.