Name: prisma
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

prisma

Prisma integration. Manage data, records, and automate workflows. Use when the user wants to interact with Prisma data.

Quality

60%

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 ./skills/prisma/SKILL.md

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 body is actionable, packed with executable Membrane CLI commands and a useful proxy reference, but it opens with unnecessary Prisma background, has broken step numbering, and keeps all content in one inlined file with no progressive disclosure. Validation for destructive action/proxy calls is absent.

Suggestions

Remove or condense the introductory 'Prisma is an open-source ORM...' paragraph and the abstract Schema/Model/Field tree, which restate what Claude already knows.

Fix the workflow numbering: define Step 1a/1b and an actual 'Step 2' so 'skip to Step 2' resolves, and add a verify step after running actions or proxy mutations (e.g. check the `output`/error fields before proceeding).

Move the detailed clientAction field reference and proxy flags table into a separate reference file (e.g. REFERENCE.md) and link to it from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining what Prisma is and the abstract Schema/Model/Field overview tree plus 'Use action names and parameters as needed' restate concepts Claude already knows, matching 'mostly efficient but includes some unnecessary explanation'; not a 4 because the padding is more than minor.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a full proxy-flags table, fitting 'mostly executable guidance with minor gaps'; not a 5 because some examples rely on placeholders and common-case coverage is incomplete.	4 / 5
Workflow Clarity	The connection flow has a real state-machine checkpoint (polling READY/BUILDING/CLIENT_ACTION_REQUIRED), but navigation is broken ('skip to Step 2' with no Step 2, '1b' with no 1a) and destructive proxy/action operations lack result verification, so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	Headers give reasonable structure, but everything is inlined in one ~140-line file with no separate reference files, and bulkier content (nested clientAction fields, the proxy flags table) that could live in a reference is inline, matching 'some structure but content that should be separate is inline'; not a 4 because no one-level-deep references are signaled.	3 / 5
	Total	13 / 20 Passed

Description

62%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 functional and includes an explicit 'Use when' trigger plus a named domain, but its action language is generic ('manage data, records, and automate workflows') rather than concrete. It is clearly distinguishable as a Prisma-specific skill yet could be sharper.

Suggestions

Replace generic verbs with concrete Prisma capabilities, e.g. 'Query and mutate database records, run migrations, and inspect schema models.'

Add natural trigger synonyms users actually say, such as 'Prisma ORM', 'Prisma client', 'schema', 'migrations', or '.prisma files'.

Tighten the 'when' clause to specific intents, e.g. 'Use when the user wants to query or modify data through Prisma, work with the Prisma schema, or run migrations.'

Dimension	Reasoning	Score
Specificity	Names the Prisma domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 2 because multiple actions are listed, not a 4 because they lack specificity.	3 / 5
Completeness	It states what it does ('Manage data, records, and automate workflows') and gives an explicit 'Use when the user wants to interact with Prisma data' trigger, satisfying both what and when; not a 5 because the 'what' is generic and the trigger phrase is less concrete than the anchor examples.	4 / 5
Trigger Term Quality	Relevant keywords appear ('Prisma', 'data', 'records', 'interact with Prisma data') but common variations or synonyms a user might say are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Prisma is a specific named tool with a distinct trigger ('interact with Prisma data'), giving a clear niche with only minor overlap risk; not a 5 because the surrounding 'manage data, records' language is generic enough to bleed into adjacent data skills.	4 / 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: membranedev/application-skills
Path: skills/prisma/SKILL.md
Commit: f484c82

Reviewed: 5 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.