Name: database-admin
Rating: 40.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

database-admin

Expert database administrator specializing in modern cloud databases, automation, and reliability engineering.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/database-admin/SKILL.md

The canonical home for this skill is database-admin in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

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

The body is a persona resume — long enumerations of known tools and vague behavioral guidance with no executable instruction, no validation checkpoints, and a broken reference to a missing playbook. It tells Claude what kind of expert to be rather than what to do.

Suggestions

Replace the capability/tool enumerations with a concise overview and move the detailed platform/technology matrices into real reference files (e.g. references/platforms.md, references/security.md).

Add concrete, executable guidance: example Terraform/Flyway snippets, backup/restore commands, failover runbook steps — not just "Apply relevant best practices".

Fix or remove the broken `resources/implementation-playbook.md` reference (the file does not exist), and add explicit validation checkpoints (validate schema migration, test backup restore, verify failover) to the workflow.

Dimension	Reasoning	Score
Conciseness	The body restates the same cloud-database/automation/reliability persona across redundant sections (Purpose, Capabilities, Behavioral Traits, Knowledge Base) and enumerates tool inventories (RDS, Aurora, DynamoDB, Terraform, Flyway) Claude already knows, making it noticeably verbose and padded though not a single-concept explainer.	2 / 5
Actionability	The Instructions ("Clarify goals", "Apply relevant best practices and validate outcomes") and the 9-step Response Approach are high-level hints with no concrete commands, code, or specific procedures, matching the minimal-concrete-guidance anchor.	2 / 5
Workflow Clarity	The Response Approach lists a sequenced lifecycle, but database admin involves destructive/batch operations (migrations, failover, backups) with no validation checkpoints or feedback loops, so the missing-validation cap holds it at 3.	3 / 5
Progressive Disclosure	60+ lines of capability enumerations that belong in separate reference files are inlined into SKILL.md, and the one external reference (`resources/implementation-playbook.md`, line 24) does not exist on disk — a broken, minimal-structure case.	2 / 5
	Total	9 / 20 Passed

Description

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

The description reads as a persona/job-title rather than an action-oriented capability statement, and it lacks any explicit "Use when" trigger guidance. It is domain-distinct butgeneric in action specificity and missing trigger synonyms.

Suggestions

Rewrite the description as concrete actions, e.g. "Provisions, migrates, backs up, and tunes cloud databases across AWS/Azure/GCP; automates failover, monitoring, and recovery."

Add an explicit "Use when" clause listing natural trigger phrases users would say ("database admin", "DBA", "database backup", "schema migration", "failover", "query tuning").

Include common synonyms and file/engine extensions (PostgreSQL, MySQL, DynamoDB, .sql) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Expert database administrator specializing in modern cloud databases, automation, and reliability engineering" names the domain well but contains no concrete actions — "specializing in" describes expertise rather than a capability the skill performs, so it sits just above the entirely-vague anchor and below the 1-2-concrete-actions anchor.	2 / 5
Completeness	It gives a clear "what" (a database-admin expert persona) but entirely omits any "when"/Use-when clause, so per the missing-trigger-guidance cap it cannot exceed 3.	3 / 5
Trigger Term Quality	"database", "cloud databases", "automation", and "reliability engineering" are relevant keywords a user might say, but common synonyms and concrete triggers like "DBA", "SQL", "PostgreSQL", "backup", or "migration" are missing, matching the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	Database administration is a clear niche with distinct triggers, but "automation" and "reliability engineering" create minor overlap with SRE/cloud-ops skills, fitting the mostly-distinct anchor.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/database-admin/SKILL.md
Commit: 57c135b

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