CtrlK
BlogDocsLog inGet started
Tessl Logo

db-ops

Use when reviewing a PR that touches the Prisma schema or migrations, running migrations in staging or production, or auditing schema changes for safety.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, highly actionable database-operations skill with executable commands, a migration safety checklist, and clear rollback/deprecation workflows. Validation checkpoints are present for the destructive operations, satisfying the database-ops feedback-loop expectation; the main gap is a single under-specified failure branch in the deploy confirmation step.

Suggestions

Add an explicit failure branch to the deploy procedure: after 'npx prisma migrate status', state what to do if migrations are not all applied (e.g., fall back to the rollback procedure) to lift workflow_clarity to 5.

Consider moving the detailed Removing Deprecated Tables procedure and Credentials into a separate reference file to reduce SKILL.md length and improve progressive_disclosure.

Trim the one-line rationale sentences (e.g., 'Zero-downtime deploys require that existing rows satisfy the new schema immediately') to push conciseness closer to a 5.

DimensionReasoningScore

Conciseness

Mostly lean checklist content that assumes Claude's competence ('Never use prisma db push outside of development'), with only minor rationale lines like 'Zero-downtime deploys require...' that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — 'npx prisma migrate deploy', 'npx prisma migrate status', 'grep -r "oldColumn" src/', 'cat prisma/migrations/*/migration.sql' — plus concrete safe/unsafe Prisma snippets covering common cases.

5 / 5

Workflow Clarity

Numbered deploy, rollback, and deprecation sequences with an explicit 'Confirm status' checkpoint and a rollback feedback loop; not a 5 because the deploy step states the expected status output without an explicit 'if not applied, do X' branch.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections (When to Use, Migration Safety Checklist, Removing Deprecated Tables, Credentials) in a single appropriately-scoped file with no nested references; not a 5 because at ~95 lines it sits above the under-50 simple-skill threshold and could not point to external detail files.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, specific description that clearly states both capability and trigger conditions for a well-scoped Prisma database-operations niche. It would benefit only from a few additional natural synonyms and file extensions to round out trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'reviewing a PR that touches the Prisma schema or migrations, running migrations in staging or production, or auditing schema changes for safety' — tied to a specific domain, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (review/run/audit schema and migration changes) and when via a concrete 'Use when...' trigger clause listing multiple scenarios.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('reviewing a PR', 'Prisma schema', 'migrations', 'staging or production', 'auditing schema changes') users would actually say, but misses some synonyms/extensions like '.prisma', 'deploy', or 'schema.prisma'.

4 / 5

Distinctiveness Conflict Risk

The Prisma schema/migration niche with staging/production qualifiers is a clear, distinct trigger surface with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tessl-fe/backend-api
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.