CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

database-architect

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/database-architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 has sound high-level sectioning (use/don't-use triggers, instructions, safety) but the instructions are abstract directives with no executable specifics, and the fractal reference structure is entirely broken — none of the 14 referenced sub-skill files exist in the bundle. Redundant Purpose/Philosophy sections and an empty Capabilities heading add tokens without adding information.

Suggestions

Make the Instructions actionable: add concrete decision criteria (e.g., a SQL vs NoSQL vs TimeSeries selection matrix), example schema/index/migration patterns, and specific validation commands instead of one-line directives like 'Choose the database model and architecture pattern'.

Fix progressive disclosure: either ship the 14 referenced sub-skills/*.md files in the bundle or inline their essential content into SKILL.md; annotate each link with a one-line note on when to consult it, and remove the empty '## Capabilities' heading.

Delete the redundant 'Purpose' section (it duplicates the frontmatter description almost verbatim) and fold the Safety items into the workflow as explicit validation checkpoints (e.g., 'validate migration plan in staging; only proceed to production rollout when validation passes').

DimensionReasoningScore

Conciseness

The 'Purpose' section restates the frontmatter description nearly verbatim ('Expert database architect with comprehensive knowledge of data modeling, technology selection...') and 'Core Philosophy' offers generic guidance Claude already knows ('Design the data layer right from the start to avoid costly rework'); the rest is lean but these padded sections and the empty '## Capabilities' heading could be trimmed.

3 / 5

Actionability

The Instructions are high-level directives — 'Capture data domain, access patterns, and scale targets', 'Choose the database model and architecture pattern', 'Design schemas, indexes, and lifecycle policies' — with no concrete criteria, examples, commands, or decision methods for executing any step. This sits between anchor 2 (high-level hints, missing specific steps) and anchor 3, closer to 2 since no step includes executable specifics.

2 / 5

Workflow Clarity

Four steps are listed in a sensible sequence and the Safety section mentions backups, rollbacks, and staging validation, but validation is not an explicit checkpoint within the workflow itself (no validate-then-proceed ordering). Per the rubric's cap for database operations involving destructive changes, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The body links to 14 sub-skill files (e.g. './sub-skills/technology-selection-evaluation.md', './sub-skills/data-modeling-schema-design.md'), but no sub-skills directory or any bundle files exist in the skill package — every reference is dead, the links carry no annotation about when to use each module, and '## Capabilities' is an empty heading. The reference structure does not resolve to any actual content, leaving navigation broken and the main body with almost no usable detail.

2 / 5

Total

10

/

20

Passed

Description

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

A strong description: comprehensive, third-person, concrete capability list plus an explicit 'Use PROACTIVELY' trigger clause naming three trigger domains. The only gap is a handful of natural trigger synonyms.

DimensionReasoningScore

Specificity

Enumerates many concrete capabilities — 'data layer design from scratch, technology selection, schema modeling, and scalable database architectures', 'SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design', 'greenfield architectures and re-architecture' — with comprehensive coverage, all in third-person voice ('Masters...', 'Handles...').

5 / 5

Completeness

Explicitly answers both what (the detailed capability list) and when: 'Use PROACTIVELY for database architecture, technology selection, or data modeling decisions' — an explicit trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

'database architecture', 'technology selection', and 'data modeling' are natural phrases a user would say, but common variations like 'schema design', 'database migration', 'pick/choose a database', or 'SQL vs NoSQL' are missing from the trigger clause.

4 / 5

Distinctiveness Conflict Risk

'Expert database architect specializing in data layer design from scratch... greenfield architectures and re-architecture' carves a clear niche with distinct triggers; minimal overlap risk with adjacent skills (query tuning or app-level design are explicitly out of scope in the body).

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 14 possibly missing (./sub-skills/caching-architecture.md, ./sub-skills/cloud-database-architecture.md, ./sub-skills/data-modeling-schema-design.md, ./sub-skills/disaster-recovery-high-availability.md, ./sub-skills/indexing-strategy-design.md, +9 more)

Warning

Total

13

/

16

Passed

Repository

Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI

Path

.agent/skills/database-architect/SKILL.md

Reviewed

Table of Contents

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.