prisma-next-feedback
Draft Prisma Next Feedback for the Right Channel
Prisma Next feedback can be difficult to classify and prepare for public submission. This skill routes feedback and drafts complete, redacted reports.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "prisma-next-feedback" from https://skillstore.io/skills/prisma-prisma-next-feedback.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-next-feedback/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "prisma-next-feedback". Migration planning exits successfully even when no migration is generated.
Expected outcome:
Recommended channel: GitHub bug report. Draft title: bug(cli): migration plan exits successfully without a generated migration. The body requests version and reproduction details.
Using "prisma-next-feedback". We need guidance for integrating an extension with an evolving Prisma Next API.
Expected outcome:
Recommended channel: Prisma Discord. The draft opening message summarizes the integration, version, relevant API surface, and the specific compatibility question.
Using "prisma-next-feedback". Prisma Next needs a first-party build plugin, and the current workaround is manual.
Expected outcome:
Recommended channel: GitHub feature request. The draft explains the workflow gap, desired plugin behavior, current workaround, package scope, and expected impact.
Security Audit
SafeAll 59 static findings are false positives caused by Markdown formatting, safe documentation links, secret-redaction guidance, or bounded workflow instructions. The skill requires explicit confirmation before GitHub submission and contains no prompt injection, credential access, or unsafe command interpolation.
Risk Factors
⚙️ External commands (40)
🌐 Network access (9)
📁 Filesystem access (1)
🔑 Env variables (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/prisma-prisma-next-feedback?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/prisma-prisma-next-feedback?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-next-feedback/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-next-feedback.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
prisma. (2026). prisma-next-feedback security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1BibTeX citation
@techreport{prisma-prisma-prisma-next-feedback-2026,
author = {prisma},
title = {prisma-next-feedback security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "prisma-next-feedback security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prisma"
date-released: "2026-08-17"
url: "https://skillstore.io/skills/prisma-prisma-next-feedback/audits/1"
identifiers:
- type: other
value: "skillstore:prisma-prisma-next-feedback:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Report a Reproducible Bug
Prepare a redacted issue with versions, steps, expected behavior, and actual behavior.
Request a Missing Capability
Turn a workflow gap into a focused feature request with scope, impact, and alternatives.
Ask the Prisma Team
Route an integration or design question to Discord with a concise opening message.
Try These Prompts
Decide whether this Prisma Next feedback belongs in GitHub, Discord, or another workflow skill: [describe the situation].
Draft a public-safe Prisma Next bug report from these details: [version, environment, command, output, steps, expected result, actual result].
Create a Prisma Next feature request for [missing capability]. Include the problem, proposed behavior, alternatives, affected packages, and current workaround.
Review [feedback details], separate bugs from feature requests, redact confidential content, draft each artifact, and request confirmation before any GitHub submission.
Best Practices
- Provide exact package, Node, package manager, operating system, and database versions.
- Reduce bug reports to minimal steps and only the relevant contract excerpt.
- Review every public artifact and confirm it before submission.
Avoid
- Do not include credentials, customer data, or confidential schema names.
- Do not combine a bug and a feature request in one issue.
- Do not submit an issue automatically or without the user reviewing it.