prisma-schema-helper
Prisma Schema Helper - Auto-activating skill for Backend Development. Triggers on: prisma schema helper, prisma schema helper Part of the Backend Development skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/prisma-schema-helper/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It only identifies the technology (Prisma) but fails to describe any concrete capabilities, use cases, or natural trigger terms. The repeated trigger term 'prisma schema helper' suggests auto-generated content that wasn't properly customized.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Prisma schema files, defines models and relations, creates migrations, validates schema syntax'
Include a 'Use when...' clause with natural trigger terms like 'database models', 'schema.prisma', 'relations', 'migrations', 'ORM setup', '@prisma/client'
Remove the redundant trigger term repetition and replace with varied natural language users would actually say when needing Prisma help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Prisma Schema Helper' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'generate', 'validate', 'migrate', or 'create' are present. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There is no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'prisma schema helper' repeated twice, which is the skill name itself rather than natural user language. Missing natural terms like 'database schema', 'models', 'relations', 'migrations', '.prisma files'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Prisma' provides some specificity to a particular ORM/tool, which helps distinguish it from generic database skills. However, without describing specific capabilities, it could still overlap with other database or schema-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is an empty template with no actual Prisma schema guidance. It contains only meta-descriptions of what the skill claims to do without any concrete examples, code snippets, schema syntax, or actionable instructions. The content provides zero value for helping Claude work with Prisma schemas.
Suggestions
Add concrete Prisma schema syntax examples showing model definitions, relations, and common patterns (e.g., one-to-many, many-to-many relationships)
Include executable code snippets for common operations like generating migrations, running prisma db push, and using prisma client
Provide a clear workflow for schema changes: edit schema -> validate -> generate client -> migrate -> verify
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual Prisma-specific guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual Prisma-specific information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific Prisma schema examples are provided. The content only describes what the skill claims to do ('provides step-by-step guidance') without actually providing any guidance, schema syntax, or executable examples. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no validation checkpoints, and no actual process for working with Prisma schemas. The content is purely descriptive metadata with no operational guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure pointing to detailed materials, no references to schema examples, migration guides, or related documentation. There's nothing to disclose progressively. | 1 / 3 |
Total | 4 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
994edc4
- 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.