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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill prisma-schema-helperOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The only distinguishing element is the 'Prisma' keyword, but without describing capabilities, Claude cannot make informed decisions about when to select this skill.
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', 'Prisma migrations', 'database relations', 'ORM setup'
Remove the redundant trigger term repetition and replace with varied, natural phrases 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 obvious terms like 'database schema', 'models', 'migrations', 'relations', '.prisma files'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Prisma' provides some specificity to distinguish from generic database or schema skills, but without describing actual capabilities, it could still conflict with other Prisma-related or database schema skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about Prisma schemas. It contains only generic boilerplate text that could apply to any skill, with no executable code, specific guidance, or actionable instructions. The skill fails to teach Claude anything about Prisma schema design, syntax, relationships, or best practices.
Suggestions
Add concrete Prisma schema examples showing model definitions, relations (@relation), and common field types with actual executable code
Include specific guidance on Prisma schema patterns like one-to-many, many-to-many relationships, enums, and indexes
Provide a workflow for schema changes: edit schema -> prisma format -> prisma validate -> prisma migrate dev
Remove all generic boilerplate ('automated assistance', 'industry best practices') and replace with Prisma-specific content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Prisma schemas. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The content describes what the skill does in abstract terms but never shows how to actually work with Prisma schemas. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps or procedures. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured content organization, and no navigation to detailed materials. The content is a shallow placeholder with no depth to disclose. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.