CtrlK
BlogDocsLog inGet started
Tessl Logo

database

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

39

Quality

27%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

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 overview of database-related capabilities but lacks explicit trigger guidance ('Use when...'), which is critical for skill selection. It names the domain and some actions but could be more specific about concrete operations and include more natural user keywords.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about database connections, SQL queries, table creation, or schema modifications'

Include more natural trigger terms users would say: specific database names (MySQL, PostgreSQL, MongoDB), common operations (SELECT, INSERT, CREATE TABLE), and file extensions (.sql)

List more specific concrete actions such as 'create tables', 'write migrations', 'optimize queries', or 'export data' to improve specificity

DimensionReasoningScore

Specificity

Names the domain (databases) and lists some actions ('Connect to', 'run queries', 'manage schemas'), but lacks comprehensive detail on specific operations like creating tables, migrations, or data manipulation.

2 / 3

Completeness

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is entirely absent, warranting a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'SQL', 'NoSQL', 'databases', 'queries', and 'schemas', but misses common variations users might say like 'MySQL', 'PostgreSQL', 'MongoDB', 'table', 'SELECT', or 'database connection'.

2 / 3

Distinctiveness Conflict Risk

Specifies SQL and NoSQL databases which provides some distinction, but 'database management' is broad enough to potentially overlap with data analysis, ETL, or backend development skills.

2 / 3

Total

7

/

12

Passed

Implementation

22%

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 advertisement rather than actionable guidance. It lists what databases are supported and what features exist, but provides zero executable code, connection examples, or actual query syntax. The safety rules are good but insufficient without concrete implementation guidance.

Suggestions

Add executable connection examples for at least 2-3 databases (e.g., PostgreSQL with psycopg2, SQLite with sqlite3 module)

Include concrete SQL query examples with actual syntax, not just natural language descriptions

Add a workflow for destructive operations: confirm -> backup -> execute -> verify, with specific commands

Either add detailed content for each database type or create separate reference files (POSTGRESQL.md, MONGODB.md) with specific guidance

DimensionReasoningScore

Conciseness

The content is relatively brief but lacks substance - it lists features and databases without providing actionable guidance. The bullet points are efficient but don't add value beyond what Claude already knows.

2 / 3

Actionability

No concrete code, commands, or executable examples provided. The 'Usage Examples' are just natural language prompts, not actual database connection strings, SQL syntax, or working code snippets.

1 / 3

Workflow Clarity

No workflow sequences provided for any database operations. Critical operations like backup/restore, schema management, and data export have no steps or validation checkpoints defined.

1 / 3

Progressive Disclosure

The content is organized with clear sections, but it's essentially a feature list with no depth. No references to detailed documentation for each database type or advanced features.

2 / 3

Total

6

/

12

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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