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
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 extremely weak across all dimensions. It reads like auto-generated boilerplate with no concrete actions, no meaningful trigger terms, and no explicit guidance on when Claude should select this skill. The repeated trigger term 'prisma schema helper' adds no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates and validates Prisma schema files, defines models and relations, configures datasources, and assists with migrations.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about Prisma models, schema.prisma files, database relations, Prisma migrate, or ORM configuration.'
Include common file extensions and variations users might mention, such as '.prisma', 'schema.prisma', 'Prisma ORM', 'Prisma Client', 'database models'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Prisma Schema' as a domain but provides no concrete actions. There is no indication of what this skill actually does — no verbs like 'generate', 'validate', 'migrate', or 'edit'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague title, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'prisma schema helper' repeated twice. It misses natural user terms like 'prisma model', 'schema.prisma', 'database schema', 'prisma migrate', 'relations', or '.prisma file'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Prisma Schema' provides some domain specificity that distinguishes it from generic coding skills, but the lack of concrete actions or detailed triggers means it could still overlap with general database or ORM 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 is an empty template with no actual content about Prisma schemas. It contains only generic boilerplate text that repeats the skill name without providing any actionable guidance, code examples, or domain-specific knowledge. It would be entirely useless for helping Claude assist with Prisma schema tasks.
Suggestions
Add concrete Prisma schema examples showing model definitions, relations, enums, and common patterns (e.g., one-to-many, many-to-many, self-relations) with executable code blocks.
Include specific Prisma CLI commands (e.g., `npx prisma generate`, `npx prisma migrate dev`) with a clear workflow sequence and validation steps.
Replace all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') with actual technical content such as best practices for indexing, naming conventions, and common pitfalls.
Add a quick-start section with a minimal but complete schema.prisma file that Claude can adapt, covering datasource, generator, and at least two related models.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'prisma schema helper' excessively, and provides zero actual Prisma schema knowledge or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no Prisma schema syntax, no commands, no specific patterns. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured navigation, and no meaningful content organization. The sections are just repetitive boilerplate headers with no substantive content beneath them. | 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
13d35b8
- 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.