CtrlK
BlogDocsLog inGet started
Tessl Logo

database-architect

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

47

Quality

50%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/database-architect/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

42%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 skill is a well-structured advisory persona but is padded with capability lists that restate knowledge Claude already has, lacks concrete templates or worked examples, and does not wire validation checkpoints into its migration workflow. It would benefit from trimming the enumeration and moving reference detail into bundle files.

Suggestions

Cut the Capabilities enumeration down to decision-relevant essentials (trade-offs, selection criteria) and move the full product/category catalog into a reference file.

Add a worked example or template — e.g. a sample schema/migration-plan with rollback steps — to make the guidance concrete and copy-paste ready.

Integrate validation checkpoints directly into the Response Approach workflow (e.g. 'validate migration in staging → only then cut over') rather than relegating them to a separate Safety section.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: the Capabilities section enumerates dozens of database products and categories (PostgreSQL, MongoDB, Redis, etc.) that Claude already knows, adding padded length without novel guidance.

2 / 5

Actionability

As an instruction-only advisory skill it has no code, but the 10-step Response Approach and Output Examples list concrete deliverables (schema design, index strategy, migration plan); guidance is partially actionable but lacks templates or worked examples.

3 / 5

Workflow Clarity

Steps are sequenced (Instructions + Response Approach), but this is a destructive/batch database context and validation is only loosely mentioned in a separate Safety section rather than as explicit checkpoints in the workflow, capping the score at 3.

3 / 5

Progressive Disclosure

No bundle files exist and everything is inline; headers give reasonable structure, but the ~256-line file inlines a large capability enumeration that would fit better in a separate reference file.

3 / 5

Total

11

/

20

Passed

Description

58%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 is specific and third-person with a clear niche, but it omits any explicit 'Use when…' trigger clause and relies on jargon-leaning terms rather than natural user phrasings. Adding a concrete trigger clause and more colloquial keywords would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing a database schema, choosing between database technologies, or planning a migration'.

Add natural user-facing keywords and synonyms — 'design a database', 'Postgres vs MongoDB', 'sharding', 'zero-downtime migration' — alongside the professional terms.

Tighten 'data layer design from scratch' to a more colloquial phrase like 'greenfield database design' or 'database architecture from scratch' to improve distinctiveness and naturalness.

DimensionReasoningScore

Specificity

Lists several concrete specializations — "data layer design from scratch, technology selection, schema modeling, and scalable database architectures" — matching the 'several specific actions; minor gaps' anchor; not a 5 because coverage is not exhaustive.

4 / 5

Completeness

Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Relevant terms ("database architect", "schema modeling", "scalable database architectures") are present but lean professional/jargon; missing natural user phrasings like "design a database", "choose Postgres vs Mongo", "migrate", or "shard".

3 / 5

Distinctiveness Conflict Risk

"Database architect" is a clear, mostly distinct niche, with only minor overlap risk against closely related skills (database-optimizer, database-admin, backend-architect).

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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