Neon Postgres Egress Optimizer
v1.0.0Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer cost...
⭐ 0· 110·0 current·0 all-time
byAndre Landgraf@andrelandgraf
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Postgres egress diagnosis & fixes) match the instructions: queries against pg_stat_statements, schema/code inspection, and query-level fixes. The skill does not ask for unrelated binaries, services, or environment variables.
Instruction Scope
The SKILL.md focuses on reading pg_stat_statements and analyzing code/query patterns, which is appropriate. It also suggests operations that change database state (CREATE EXTENSION IF NOT EXISTS pg_stat_statements; SELECT pg_stat_statements_reset();). Those are reasonable for gathering diagnostics but are state-changing and may require elevated privileges or affect monitoring — so they warrant caution before running on production systems.
Install Mechanism
No install spec or downloaded code — instruction-only skill. Nothing is written to disk or installed by the skill itself.
Credentials
The skill declares no required environment variables or credentials. Its operations require DB access in practice (the user or operator would need to supply connection credentials), which is proportional to the task. No unrelated secrets are requested by the skill metadata or instructions.
Persistence & Privilege
The skill is not always-enabled, does not request persistent system presence, and does not modify other skills or system-wide agent settings. Autonomous invocation is allowed by platform default but not excessive for this purpose.
Assessment
This skill appears coherent for diagnosing Postgres egress, but exercise operational caution before running its SQL on production: - Prefer providing read-only or monitoring replicas instead of full-production writable credentials. - CREATE EXTENSION may require elevated privileges and may be disallowed in managed DBs; ask your DB admin first. - pg_stat_statements_reset() clears historic statistics (it will disrupt existing monitoring windows); avoid running it if you need existing stats. - If you cannot or will not share DB credentials, you can supply query outputs or anonymized samples instead, or let the skill focus on codebase analysis only. - Be careful not to expose secrets when sharing code or schema; consider masking sensitive fields. Overall this skill is internally consistent, but protect production systems and credentials when following its instructions.Like a lobster shell, security has layers — review code before you run it.
latestvk976827wxdsyxf7gdgeb6d6dr5833hks
License
MIT-0
Free to use, modify, and redistribute. No attribution required.