database-admin

Database administration tasks including schema changes, backups, monitoring, and user access management.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugin-creator/evals/scenario-1/inputs/SKILL.md

Quality

Content

71%Scale 1-5

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

This is a solid, highly actionable database administration skill with concrete, executable SQL and shell commands covering four major areas. Its main weaknesses are moderate verbosity from repetitive framing and Slack notification steps, and the monolithic structure that could benefit from splitting detailed reference material into separate files. Workflow clarity is good but could be strengthened by embedding validation checkpoints more explicitly within destructive operations.

Suggestions

Split detailed SQL blocks (monitoring queries, user management SQL templates) into separate reference files and link to them from the main SKILL.md overview to improve progressive disclosure.

Remove repetitive framing phrases like 'When the user needs to...' and 'When the user asks about...' — these waste tokens without adding value for Claude.

Add an explicit backup integrity verification step (e.g., `pg_restore --list backup.sql.gz | head` or checking file size) before uploading to S3 in the backup workflow.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete commands and SQL, but includes some unnecessary framing phrases ('When the user needs to...', 'When the user asks about...') and organizational overhead like Slack notification steps that pad the content. The safety rules and environment variables sections are reasonable but could be tighter.	3 / 5
Actionability	Excellent actionability throughout — every section provides copy-paste ready SQL commands and shell commands covering common cases (read-only vs read-write users, backup and restore, monitoring queries). The migration file conventions and common fixes sections add practical, specific guidance.	5 / 5
Workflow Clarity	Each workflow has clear numbered sequences with verification steps (e.g., confirming migration applied, verifying S3 upload, sanity check after restore). The migration section includes rollback on failure. However, the backup section lacks a validation step to verify the dump integrity before uploading, and the destructive operation safety rules are stated but not integrated as explicit checkpoints within each workflow.	4 / 5
Progressive Disclosure	The content is well-structured with clear section headers and horizontal rules, but at ~150 lines it's a monolithic file that could benefit from splitting detailed SQL reference blocks (monitoring queries, user management SQL) into separate files. No bundle files exist to offload content to, and no references to external files are made.	3 / 5
	Total	15 / 20 Passed

Description

58%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.

The description provides a solid enumeration of database administration capabilities but lacks a 'Use when...' clause, which limits its effectiveness for skill selection. The trigger terms are adequate but could be strengthened with synonyms, abbreviations (DBA), and specific database technologies. Overall it's a competent but incomplete description that would benefit from explicit trigger guidance.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about database administration, DBA tasks, schema migrations, database backups, database monitoring, or managing database users and permissions.'

Include natural synonyms and abbreviations such as 'DBA', 'migrations', 'permissions', 'roles', 'database performance', and mention specific database systems if applicable (e.g., PostgreSQL, MySQL, SQL Server).

Dimension	Reasoning	Score
Specificity	Lists several specific actions: schema changes, backups, monitoring, and user access management. These are concrete DBA tasks, though it could be more granular (e.g., specifying types of schema changes, backup strategies, or what monitoring entails).	4 / 5
Completeness	Clearly answers 'what' with specific DBA tasks, but has no 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant terms like 'database administration', 'schema changes', 'backups', 'monitoring', and 'user access management', but misses natural user phrases like 'DBA', 'database migration', 'permissions', 'roles', 'database performance', or specific database names (PostgreSQL, MySQL, etc.).	3 / 5
Distinctiveness Conflict Risk	The combination of 'database administration' with specific tasks like schema changes, backups, and user access management is fairly distinct. Minor overlap risk with general database query skills or DevOps/infrastructure skills, but the DBA focus narrows it well.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: tesslio/product-plugins
Path: plugin-creator/evals/scenario-1/inputs/SKILL.md
Commit: 37f0a21

Reviewed: 1 day 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.