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.
71
Quality
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./claude/skills/postgresql-psql/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly identifies the specific tool (psql), lists comprehensive concrete actions, includes an explicit 'Use when' clause with natural trigger terms, and is distinctive enough to avoid conflicts with other database-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'connecting to PostgreSQL databases, executing queries, managing databases/tables, configuring connection options, formatting output, writing scripts, managing transactions, and using advanced psql features'. | 3 / 3 |
Completeness | Clearly answers both what ('Comprehensive guide for PostgreSQL psql - the interactive terminal client') and when ('Use when connecting to PostgreSQL databases, executing queries, managing databases/tables...'). Has explicit 'Use when' clause with detailed triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'PostgreSQL', 'psql', 'queries', 'databases', 'tables', 'connection', 'scripts', 'transactions', 'database administration'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to PostgreSQL's psql tool - the combination of 'PostgreSQL', 'psql', and 'interactive terminal client' creates a clear niche that wouldn't conflict with general database skills or other database systems. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive but severely over-engineered for its purpose. It functions more as exhaustive reference documentation than a focused skill guide, explaining concepts Claude already knows and listing every possible option rather than curating the most useful patterns. The actionability is strong with executable examples, but the extreme verbosity and lack of progressive disclosure make it inefficient for context window usage.
Suggestions
Reduce content by 70-80% by removing explanations of basic concepts (REPL, SQL commands, what psql is) and focusing only on non-obvious patterns and gotchas
Split into multiple files: keep SKILL.md as a quick-start overview (~100 lines) with references to separate files for meta-commands reference, scripting patterns, and troubleshooting
Add explicit validation checkpoints to multi-step workflows, especially for backup/restore and destructive operations (e.g., 'Verify backup integrity before proceeding')
Remove exhaustive lists of every meta-command option - Claude can look these up; instead focus on the 10-15 most commonly needed commands with context on when to use each
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1000+ lines. Explains basic concepts Claude already knows (what REPL is, what SQL commands are), includes exhaustive lists of every meta-command and option rather than focusing on what's actually useful, and contains significant redundancy throughout. | 1 / 3 |
Actionability | Provides extensive executable code examples throughout - connection strings, SQL queries, bash scripts, and psql commands are all copy-paste ready with concrete syntax and real examples. | 3 / 3 |
Workflow Clarity | While individual operations are clear, multi-step workflows like backup/restore lack explicit validation checkpoints. The 'SQL Script Best Practices' section shows some workflow structure but doesn't include verification steps for destructive operations. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline regardless of complexity - API references, examples, troubleshooting, and advanced features are all crammed into one massive document rather than being appropriately split. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Repository
- einverne/dotfiles
- Commit
b1b2fe0
- 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.