CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

database

Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.

Quality

69%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, lean orchestration index: sequenced phases, concrete dispatch prompts, and a quality-gate checklist. Its main gaps are the absence of error-recovery feedback loops in risky operations (migrations, batch changes) and minor redundancy across sections.

Suggestions

Add explicit feedback loops for risky phases, e.g. after 'Test migration': 'If validation fails, restore from backup, fix the script, and re-test before executing.'

Remove the redundant 'Database Technology Workflows' section (or fold it into the Overview) since it re-lists skills already cited per phase.

DimensionReasoningScore

Conciseness

Efficient listing format with no explanations of concepts Claude already knows; every phase is a terse skills/actions/prompts triple. Minor trimmable redundancy: the Overview repeats the frontmatter description, and 'Database Technology Workflows' re-lists skills already cited per phase.

4 / 5

Actionability

Each phase provides copy-paste ready invocation prompts ('Use @database-migrations-sql-migrations to create migrations') plus named skills and specific action steps. Minor gaps: actions like 'Analyze slow queries' and 'Optimize indexes' are high-level directions without how-to detail.

4 / 5

Workflow Clarity

A clear 7-phase sequence with a Quality Gates checklist, and the destructive migration phase includes validation ('Test migration', 'Verify data integrity'). Falls short of anchor 5 because no feedback loops or error-recovery guidance (what to do when a migration or benchmark fails) is provided.

4 / 5

Progressive Disclosure

Well-organized, navigable sections with no nested references; the body is an appropriately self-contained index that dispatches to other skills rather than inlining detail. Minor organization gaps: the tech quick-reference section duplicates per-phase skill lists and the whole could be tightened.

4 / 5

Total

16

/

20

Passed

Description

50%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 clearly identifies the domain and breadth of the workflow, but reads as a topic enumeration rather than an action-oriented capability statement, includes no 'when to use' trigger guidance, and is so broad within the database domain that it risks competing with the individual skills it orchestrates.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to design a schema, write or run migrations, optimize slow queries, or set up database operations.'

Convert topic nouns into concrete actions and include common user vocabulary: 'Design schemas, write and run migrations, tune slow queries, and set up backups/replication for PostgreSQL, MongoDB, and Redis.'

Narrow or sharpen the scope framing so the bundle triggers for multi-phase database work rather than any single database question that a child skill (e.g. postgresql, prisma-expert) already covers.

DimensionReasoningScore

Specificity

The description names the domain and several activity areas ("database design, migrations, optimization, and data engineering"), but frames them as topics the workflow 'covers' rather than concrete actions. It names more areas than anchor 2 but lacks the explicit action verbs of anchor 4.

3 / 5

Completeness

The 'what' is clear (database development and operations workflow covering listed areas), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "SQL, NoSQL, migrations, optimization" are present, matching anchor 3's 'some relevant keywords'. Common variations users actually say are missing: no PostgreSQL/MongoDB, no 'schema', no 'query tuning' or 'slow queries'.

3 / 5

Distinctiveness Conflict Risk

Distinct from non-database skills, but the scope spans essentially all database work ("SQL, NoSQL, database design, migrations, optimization, and data engineering"), creating overlap risk with the many individual database skills it dispatches to (postgresql, prisma-expert, database-optimizer). Fits anchor 3: somewhat specific but could still overlap with similar skills.

3 / 5

Total

12

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/database/SKILL.md

Revision

64adc55

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill