database

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

Quality

26%

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

Quality

Content

17%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a table of contents that delegates everything to other skills without providing any concrete guidance itself. It lacks executable code, specific commands, validation steps, and meaningful workflow detail. The repetitive phase structure adds bulk without substance, and the 'copy-paste prompts' are trivially simple invocations that don't help Claude perform any actual database work.

Suggestions

Add concrete, executable examples for at least the most common tasks (e.g., a sample migration script, an EXPLAIN ANALYZE workflow for query optimization, a backup command sequence).

Add explicit validation and verification steps for destructive operations like data migrations (e.g., 'Run SELECT COUNT(*) before and after migration to verify row counts match').

Remove the generic action lists ('Gather requirements', 'Design schema') that Claude already knows and replace them with specific, actionable guidance unique to each phase.

Either provide actual bundle files for the referenced skills or consolidate the most critical guidance inline rather than delegating everything to unlinked external skills.

Dimension	Reasoning	Score
Conciseness	The content is heavily padded with repetitive structure across 7 phases, each following the same template of 'Skills to Invoke', 'Actions', and 'Copy-Paste Prompts'. The actions are vague platitudes ('Gather requirements', 'Design schema') that Claude already knows. The copy-paste prompts are trivially simple and don't add value.	2 / 5
Actionability	The skill provides no concrete, executable guidance whatsoever. There are no SQL examples, no actual commands, no code snippets, no specific configurations. Every 'action' is a vague directive like 'Analyze slow queries' or 'Set up backups' with no specifics on how. The 'copy-paste prompts' are just '@skill-name' invocations with no substance.	1 / 5
Workflow Clarity	While there is a rough 7-phase sequence, the steps within each phase are generic and poorly defined (e.g., 'Plan migration strategy', 'Execute migration'). There are no validation checkpoints, no feedback loops, and no error recovery guidance. Phase 4 (Data Migration) involves destructive/batch operations but lacks any validation steps, which should cap this at 3 maximum, but the overall vagueness brings it below that.	2 / 5
Progressive Disclosure	The skill references many other skills by name but provides no actual file links or paths. There are no bundle files to support the references. The content is a monolithic list that could benefit from being split into separate files per phase or technology, but instead everything is inlined in a repetitive flat structure.	2 / 5
	Total	7 / 20 Passed

Description

36%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 identifies the domain but reads as a list of topic areas rather than concrete capabilities. It lacks any 'Use when...' clause, making it difficult for Claude to know precisely when to select this skill. The breadth of coverage (SQL, NoSQL, data engineering, optimization) without specific actions makes it feel like a category label rather than a functional skill description.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks about writing SQL queries, designing database schemas, creating migrations, or optimizing query performance.'

Replace broad category labels with specific actions using verbs, e.g., 'Writes and optimizes SQL queries, designs database schemas, creates and runs migration scripts, configures indexes for performance.'

Include common synonyms and specific technologies users might mention, such as 'PostgreSQL', 'MySQL', 'MongoDB', 'schema', 'indexes', 'query optimization', '.sql files'.

Dimension	Reasoning	Score
Specificity	Names the domain (database development) and lists broad categories (SQL, NoSQL, migrations, optimization) but these are sub-domains rather than concrete actions. No specific verbs describing what the skill actually does (e.g., 'writes migration scripts', 'optimizes query performance', 'designs schemas').	2 / 5
Completeness	Provides a vague 'what' (covers database development and operations) but has no 'when' clause at all. There is no 'Use when...' guidance or explicit trigger phrases to help Claude decide when to select this skill. Per rubric guidelines, missing 'Use when' should cap completeness at 3, and this description's 'what' is also quite vague.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'SQL', 'NoSQL', 'database design', 'migrations', 'optimization', and 'data engineering' that users might naturally mention. However, it misses common variations and synonyms like 'query', 'schema', 'indexes', 'PostgreSQL', 'MongoDB', 'ORM', 'tables', or specific database names.	3 / 5
Distinctiveness Conflict Risk	The database focus provides some distinctiveness, but the breadth of the description ('SQL, NoSQL, database design, migrations, optimization, data engineering') is so wide it could overlap with data engineering skills, backend development skills, or DevOps skills. The term 'data engineering' especially broadens conflict risk.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/database/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.