postgres

PostgreSQL database management. Run queries, manage schemas, and monitor performance.

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/postgres/SKILL.md

Quality

Discovery

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description effectively communicates concrete capabilities with good specificity, but lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select it. The PostgreSQL focus provides some distinctiveness, but could benefit from more natural trigger terms and variations users might say.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when working with PostgreSQL databases, postgres, psql commands, or .sql files for Postgres'

Include common keyword variations: 'postgres', 'psql', 'pg_', 'Postgres database', 'SQL queries on PostgreSQL'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Run queries, manage schemas, and monitor performance' - these are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what' (run queries, manage schemas, monitor performance) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes 'PostgreSQL' and 'database' which are relevant keywords, but missing common variations like 'postgres', 'psql', 'SQL queries', 'db', or file extensions.	2 / 3
Distinctiveness Conflict Risk	PostgreSQL is specific, but 'database management' and 'run queries' could overlap with MySQL, SQLite, or generic SQL skills. Needs clearer PostgreSQL-specific triggers.	2 / 3
	Total	9 / 12 Passed

Implementation

52%

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

The skill is concise and well-structured at a high level, but lacks the actionable depth needed for effective database management. Critical operations like backups, schema changes, and performance monitoring are mentioned but not explained with concrete commands or workflows. The safety rules are good principles but lack implementation guidance.

Suggestions

Add executable examples for each major feature (backup: `pg_dump`, schema changes: `ALTER TABLE`, performance: `EXPLAIN ANALYZE`)

Create a workflow with validation steps for destructive operations: backup -> verify backup -> make change -> validate -> rollback if needed

Either add concrete commands for listed features or link to separate reference files for backup/restore, performance monitoring, and extensions

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations of what PostgreSQL is or how databases work. Every section serves a purpose without padding.	3 / 3
Actionability	Provides one concrete psql command and environment variable setup, but most 'features' are just listed without executable examples. Usage examples show prompts but not actual SQL/commands to execute.	2 / 3
Workflow Clarity	No clear workflow sequences for multi-step operations like schema changes or backups. Safety rules mention backup before schema changes but don't show how. Missing validation checkpoints for destructive operations.	1 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but features like backup/restore, performance monitoring, and extensions management are listed without any detail or references to where to find more information.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

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