CtrlK
BlogDocsLog inGet started
Tessl Logo

postgresql-psql

Comprehensive guide for PostgreSQL psql - the interactive terminal client for PostgreSQL. Use when connecting to PostgreSQL databases, executing queries, managing databases/tables, configuring connection options, formatting output, writing scripts, managing transactions, and using advanced psql features for database administration and development.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/postgresql-psql/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A thorough, actionable psql reference weighed down by substantial general-SQL padding Claude already knows, missing validation checkpoints on batch/destructive workflows, and a monolithic structure that should be split into reference files.

Suggestions

Remove or move general SQL/PostgreSQL sections (basic CRUD, window functions, CTEs, JSON, GRANT/CREATE USER, triggers) that are not psql-specific; keep only psql client behavior — meta-commands, connection options, pset options, .psqlrc, variable substitution, scripting.

Add explicit validation checkpoints to destructive/batch workflows, e.g. verify a pg_restore listing before restore, confirm row counts before/after DELETE, and dry-run maintenance scripts against a single database before looping over all databases.

Split the inlined reference tables (meta-commands, command-line options, pset options) into bundled reference files under references/ and point to them from a concise SKILL.md overview to enable proper progressive disclosure.

DimensionReasoningScore

Conciseness

Large sections teach general SQL/PostgreSQL Claude already knows — basic SELECT/INSERT/UPDATE, window functions, CTEs, JSON ops, transaction control, GRANT/CREATE USER, triggers — which are padded, off-topic material for a psql-the-client skill.

2 / 5

Actionability

Abundant concrete, mostly copy-paste-ready bash/SQL/meta-command examples; minor gaps like the unimplemented 'current_user_id()' RLS policy and the invalid 'cat users.csv piped into the client-side copy meta-command' and '-sslmode' syntax keep it just below fully executable.

4 / 5

Workflow Clarity

Sequences exist (script best practices, backup/restore) but destructive/batch operations — automated VACUUM/REINDEX across all databases, pg_dump/restore, DROP/DELETE, COPY imports — lack explicit validate-then-proceed checkpoints, capping this at 3 per the batch/destructive rule.

3 / 5

Progressive Disclosure

Well-organized with clear section headers, but it is a monolithic ~1330-line file with no bundle files and no external references; the meta-command and option tables clearly belong in separate reference files rather than inlined in SKILL.md.

3 / 5

Total

12

/

20

Passed

Description

88%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, specific description that clearly answers both what the skill does and when to use it, with concrete action verbs and natural trigger terms. The main weakness is minor keyword redundancy and slight breadth-related overlap risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'connecting to PostgreSQL databases, executing queries, managing databases/tables, configuring connection options, formatting output, writing scripts, managing transactions' — giving comprehensive coverage rather than just a few actions.

5 / 5

Completeness

Explicitly states both what ('Comprehensive guide for PostgreSQL psql - the interactive terminal client for PostgreSQL') and when ('Use when connecting... executing queries... managing transactions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-keyword coverage ('PostgreSQL', 'psql', 'queries', 'databases/tables', 'scripts', 'transactions'), but 'PostgreSQL' repeats four times and a few natural terms like 'terminal', 'command-line', or 'CLI' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'psql' / PostgreSQL terminal framing is a clear niche with distinct triggers, but the broad 'database administration and development' scope creates minor overlap risk with general SQL or DBA skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1337 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
einverne/dotfiles
Reviewed

Table of Contents

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.