Name: prisma-expert
Rating: 52.8 (1 reviews)
Author: administrakt0r

prisma-expert

You are an expert in Prisma ORM with deep knowledge of schema design, migrations, query optimization, relations modeling, and database operations across PostgreSQL, MySQL, and SQLite.

Quality

58%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/prisma-expert/SKILL.md

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

Quality

Content

57%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 content is actionable with solid code examples across schema, migrations, queries, connections, and transactions, but it is a monolithic single file with no progressive disclosure and lacks explicit validation feedback loops for its destructive database operations.

Suggestions

Add explicit validate-fix-retry checkpoints to the migrations and production-deploy workflows (e.g. run `prisma validate` then retry on failure before proceeding).

Split the large problem playbooks into one-level-deep reference files (e.g. references/migrations.md, references/query-optimization.md) and keep only an overview in SKILL.md.

Remove the generic 'When to Use' filler line or replace it with concrete trigger guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code and checklists, but it is padded in places — notably the generic filler 'When to Use: This skill is applicable to execute the workflow or actions described in the overview' and some redundant diagnosis sections that could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands (npx prisma validate, migrate status), TypeScript client snippets, and schema examples covering the common cases, with only minor gaps.	4 / 5
Workflow Clarity	A rough sequence exists (Step 0 routing, environment detection, apply strategy, per-problem playbooks), but destructive/batch database operations like migrate reset and production deploys lack explicit validate-fix-retry checkpoints, capping workflow clarity at 3 per the database-operations feedback-loop rule.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), so ~350 lines of five full problem playbooks, checklists, and anti-patterns are inlined in one monolithic SKILL.md; section headers give some structure, but content that clearly belongs in separate files is not split out.	3 / 5
	Total	13 / 20 Passed

Description

60%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 is well-scoped to Prisma ORM with strong distinctiveness and decent trigger terms, but it is written in second-person voice and omits any explicit 'when to use' trigger guidance, capping its completeness and specificity.

Suggestions

Rewrite in third person and convert knowledge areas into concrete actions, e.g. 'Designs Prisma schemas, creates and resolves migrations, optimizes N+1 queries, and manages connection pooling across PostgreSQL, MySQL, and SQLite.'

Add an explicit trigger clause, e.g. 'Use when working with Prisma ORM, prisma/schema.prisma files, migrations, or Prisma Client query issues.'

Dimension	Reasoning	Score
Specificity	The description names the Prisma domain and several capability areas ('schema design, migrations, query optimization, relations modeling, and database operations'), but these are knowledge domains rather than concrete actions, and the second-person 'You are an expert in' voice triggers a 1-point specificity penalty per the rubric guidelines.	2 / 5
Completeness	It clearly states what the skill covers (Prisma ORM expertise across the listed areas) but provides no explicit 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the missing-when rule.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ('Prisma ORM', 'schema design', 'migrations', 'query optimization'), though a few natural synonyms and file extensions (e.g. '.prisma', 'prisma schema file') are missing.	4 / 5
Distinctiveness Conflict Risk	It is tightly scoped to Prisma ORM with a clear niche (schema, migrations, queries across PostgreSQL/MySQL/SQLite), making it highly distinct with minimal conflict risk against unrelated skills.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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-claude/skills/prisma-expert/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.