database

Database management and queries. Connect to SQL and NoSQL databases, run queries, and manage schemas.

Quality

23%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./public/skills/0xterrybit/database/SKILL.md

Quality

Content

14%

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 feature overview or README placeholder rather than an actionable skill document. It lists databases and capabilities without providing any concrete code, connection examples, query patterns, or workflows. For a skill covering 5 different database systems with destructive operations, the lack of executable guidance, validation steps, and supporting reference files is a critical gap.

Suggestions

Add concrete, executable code examples for at least the most common operations (connecting, querying, schema inspection) for each supported database, with actual connection strings and library imports.

Define explicit multi-step workflows with validation checkpoints for destructive operations (DELETE, DROP, schema migrations), including a confirm-before-execute pattern and rollback guidance.

Split detailed per-database guidance into separate referenced files (e.g., POSTGRESQL.md, MONGODB.md) and link them from the main skill with clear navigation.

Replace the vague 'Features' bullet list with actionable instructions or code snippets that Claude can directly execute.

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes feature bullet lists that are vague and don't add actionable value. The 'Supported Databases' and 'Features' sections are essentially marketing copy rather than useful instructions for Claude.	2 / 3
Actionability	There is no executable code, no concrete commands, no connection strings, no actual SQL examples, and no specific guidance on how to connect to or query any of the listed databases. The 'Usage Examples' are just natural language prompts, not actionable instructions.	1 / 3
Workflow Clarity	There are no multi-step workflows defined. For database operations—which include destructive actions like DELETE/DROP—there are no validation checkpoints, no feedback loops, and no sequenced processes. The safety rules mention confirming before DELETE/DROP but don't describe how to implement that confirmation.	1 / 3
Progressive Disclosure	The content is a flat, shallow document with no references to supporting files and no structured navigation. Given the breadth of databases covered (5 different systems), there should be detailed guides or references for each, but none exist.	1 / 3
	Total	5 / 12 Passed

Description

32%

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 provides a reasonable but surface-level overview of database-related capabilities. It lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms cover the basics but miss many natural variations users might employ.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about database connections, writing SQL queries, managing schemas, or working with databases like PostgreSQL, MySQL, MongoDB, or SQLite.'

Include more natural trigger terms and common database names/extensions: 'MySQL', 'PostgreSQL', 'MongoDB', 'SQLite', '.sql', 'table', 'migration', 'query optimization'.

List more specific concrete actions such as 'create and alter tables, write and optimize queries, perform migrations, manage indexes, import/export data'.

Dimension	Reasoning	Score
Specificity	Names the domain (database management) and lists some actions (connect, run queries, manage schemas), but these are fairly high-level and not deeply specific — e.g., it doesn't mention migrations, indexing, backups, or specific query types.	2 / 3
Completeness	It describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2 — and since the 'what' is also somewhat thin, this lands at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'SQL', 'NoSQL', 'databases', 'queries', and 'schemas', but misses common user variations such as 'MySQL', 'PostgreSQL', 'MongoDB', 'table', 'migration', '.sql files', or 'database connection string'.	2 / 3
Distinctiveness Conflict Risk	The mention of SQL and NoSQL databases provides some specificity, but 'database management and queries' is broad enough to potentially overlap with data analysis, ORM, or migration-specific skills.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: about 2 months 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.