database-admin

Expert database administrator specializing in modern cloud databases, automation, and reliability engineering. Masters AWS/Azure/GCP database services, Infrastructure as Code, high availability, disaster recovery, performance optimization, and compliance. Handles multi-cloud strategies, container databases, and cost optimization. Use PROACTIVELY for database architecture, operations, or reliability engineering.

Quality

43%

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 ./skills/database-admin/SKILL.md

Quality

Content

20%

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 generic persona/catalog skill that lists technologies Claude already knows without providing concrete, executable guidance or validation-gated workflows. It is over-long and monolithic, with no progressive disclosure structure.

Suggestions

Replace the technology catalog and redundant persona sections with concrete, executable guidance — specific commands, IaC snippets, or query examples a DBA would actually run.

Add validation/verification checkpoints and fix-and-retry feedback loops into the "Response Approach" workflow, especially for destructive or batch database operations.

Move the lengthy capabilities catalog into a separate reference file and keep SKILL.md as a lean overview that links one level deep, rather than a 135-line monolith.

Dimension	Reasoning	Score
Conciseness	The ~135-line body is a verbose catalog enumerating technologies and tools Claude already knows (PostgreSQL, MySQL, Terraform, Flyway, Liquibase, etc.), padded with redundant "Capabilities", "Knowledge Base", and "Behavioral Traits" sections rather than adding non-obvious guidance.	1 / 3
Actionability	There is no executable code, specific commands, or concrete examples; the instructions are abstract ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes"), describing rather than instructing.	1 / 3
Workflow Clarity	The "Response Approach" provides a 9-step sequence, but it lacks explicit validation checkpoints or fix-and-retry feedback loops, which the rubric requires for database operations, capping this at 2.	2 / 3
Progressive Disclosure	At 135 lines the content is monolithic with no bundle files or one-level-deep references, though it is organized into headed sections; the large capability catalog that should be split out is inline, matching the "some structure but content that should be separate is inline" anchor.	2 / 3
	Total	6 / 12 Passed

Description

67%

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 is well-structured with an explicit trigger clause and clear domain focus, scoring well on completeness. Its main weaknesses are abstract rather than concrete actions and jargon-heavy, somewhat broad triggers that raise overlap risk.

Dimension	Reasoning	Score
Specificity	The description names concrete domains ("AWS/Azure/GCP database services", "Infrastructure as Code", "high availability, disaster recovery") but frames them with abstract verbs ("Masters", "Handles") rather than listing concrete actions a DBA performs, so it falls short of the multi-action anchor 3.	2 / 3
Completeness	It answers both what the skill does and when to use it via the explicit trigger clause "Use PROACTIVELY for database architecture, operations, or reliability engineering", satisfying the anchor for clearly answering both what AND when.	3 / 3
Trigger Term Quality	It includes natural user terms ("database architecture", "operations", "reliability engineering") but leans heavily on jargon ("Infrastructure as Code", "multi-cloud strategies", "container databases") and misses common variations, matching the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	Database administration is a recognizable niche, but the triggers ("database architecture, operations") are broad enough to overlap with general development or DevOps skills, so it sits at the "somewhat specific but could overlap" anchor rather than a clearly conflict-free niche.	2 / 3
	Total	9 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/database-admin/SKILL.md
Commit: e63f7dd

Reviewed: about 5 hours 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.