database-architect

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.

Quality

50%

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-architect/SKILL.md

The canonical home for this skill is database-architect in rmyndharis/antigravity-skills

Quality

Content

35%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 an exhaustive capability catalog that restates widely-known database knowledge rather than providing executable guidance, with no reference files to offload the bulk. Workflows are sequenced but lack validation checkpoints for destructive operations.

Suggestions

Move the Capabilities and Knowledge Base catalogs into separate reference files (e.g., references/technologies.md, references/patterns.md) and keep SKILL.md a lean overview that points to them.

Replace abstract step hints with concrete, actionable guidance — example schema sketches, a sample migration command sequence with a tool, or a checklist template for technology selection.

Add explicit validation/feedback-loop checkpoints into the migration and rollout workflow (e.g., validate in staging → verify row counts → only then promote), rather than leaving validation as a separate Safety bullet.

Dimension	Reasoning	Score
Conciseness	Roughly 150 lines of the Capabilities and Knowledge Base sections catalog technologies and concepts Claude already knows (PostgreSQL, MongoDB, normalization 1NF-5NF, ACID, CAP, B-tree indexes) with near-zero added value, which is heavily padded even though structured into categories.	2 / 5
Actionability	The Instructions and 10-step Response Approach are high-level hints ('Capture data domain, access patterns, and scale targets'; 'Recommend technology... with clear rationale') with no executable code, commands, or concrete artifacts, offering minimal concrete guidance.	2 / 5
Workflow Clarity	A sequenced process exists (Instructions and Response Approach), but the workflow has no explicit validation checkpoints or feedback loops; because the skill covers destructive migration operations, the rubric caps workflow clarity at 3 even though staging validation is mentioned separately under Safety.	3 / 5
Progressive Disclosure	Section and subsection headers give the body reasonable structure, but the large Capabilities catalog is content that clearly belongs in separate reference files and there are no bundle files (references/, scripts/, assets/) at all, leaving organization only partially realized.	3 / 5
	Total	10 / 20 Passed

Description

66%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 names a clear domain and several concrete actions but omits any explicit 'Use when...' trigger guidance, capping completeness. It is distinct from sibling database skills yet carries minor overlap risk with admin/optimizer roles.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers (e.g., 'Use when designing a new database schema, selecting a database technology, or planning a zero-downtime migration').

Include natural user phrasings and synonyms such as 'database design', 'schema design', and 'data modeling' alongside the existing terminology.

Dimension	Reasoning	Score
Specificity	Quotes 'data layer design from scratch, technology selection, schema modeling, and scalable database architectures' — several concrete actions are named, but 'scalable database architectures' stays somewhat abstract, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	The 'what' is clear ('Expert database architect specializing in...') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'database architect', 'schema modeling', and 'technology selection' appear, but common user phrasings such as 'database design', 'schema design', or 'data modeling' are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'design from scratch / scalable architectures' framing carves a clear niche, but it overlaps with closely related skills (database-admin, database-optimizer, backend-architect), so minor overlap risk remains.	4 / 5
	Total	15 / 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-architect/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.