Content
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder—it lists many capabilities (schema management, index optimization, backup/restore, performance monitoring, extensions) but provides almost no actionable guidance for any of them. The single concrete command (psql SELECT) is insufficient for a skill covering destructive database operations that need explicit validation workflows and safety procedures.
Suggestions
Add executable code examples for each listed feature (e.g., CREATE INDEX, pg_dump for backup, pg_stat_statements for slow queries) instead of just listing feature names.
Define explicit multi-step workflows with validation checkpoints for destructive operations like schema changes (e.g., backup → apply migration → validate → rollback if failed).
Replace the natural language 'Usage Examples' with concrete command sequences or SQL snippets that Claude can directly execute.
Either remove features you can't document concretely, or create referenced bundle files (e.g., SCHEMA.md, BACKUP.md, MONITORING.md) with detailed guidance for each area.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but the 'Features' bullet list is a vague feature catalog that adds little actionable value. The 'Usage Examples' section lists natural language prompts rather than concrete instructions, wasting tokens on non-actionable content. | 2 / 3 |
Actionability | Almost entirely vague. Only one concrete command is provided (psql with SELECT). There's no executable code for schema management, index optimization, backup/restore, performance monitoring, or extensions management—all listed as features but never demonstrated with actionable guidance. | 1 / 3 |
Workflow Clarity | No multi-step workflows are defined despite covering destructive operations like schema changes and backup/restore. The safety rules mention confirming before destructive operations and backing up before schema changes, but provide no concrete validation steps, feedback loops, or sequenced processes. | 1 / 3 |
Progressive Disclosure | The content is short and organized into sections, which is fine for a simple skill. However, it lists six feature areas with no depth on any of them and no references to supporting files that could provide the missing detail. The structure exists but doesn't lead anywhere useful. | 2 / 3 |
Total | 6 / 12 Passed |