Prezentit
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone installing the skill must provide a Prezentit API key, allowing the agent to perform Prezentit API actions on that account.
The skill requires a Prezentit API key and uses it as a bearer token. This is expected for the service, but it gives the agent delegated access to the user's Prezentit account and credits.
requires:\n config:\n - PREZENTIT_API_KEY ... Auth Header: `Authorization: Bearer {PREZENTIT_API_KEY}`Use a dedicated Prezentit API key if possible, revoke it if no longer needed, and ensure the registry metadata is updated to declare the required environment variable.
Generating slides can spend Prezentit credits, including paid credits if the account has them.
The documented generation request creates a presentation and consumes account credits. This is central to the skill's purpose and disclosed, but it is a credit-consuming account action.
POST /api/v1/presentations/generate ... "creditsUsed": 75, "remainingCredits": 25
Before submitting a generation request, confirm the topic, slide count, theme, and estimated credit cost with the user.
Presentation topics, outlines, and contextual details may be sent to Prezentit for processing.
The skill sends user-provided presentation topics and optional details to the external Prezentit API. This is expected for generation, but users should recognize the external data flow.
Base URL: `https://prezentit.net/api/v1` ... "topic": "User's topic here" ... `details` | string | No | Additional context about the presentation content.
Avoid including confidential or regulated information unless the user is comfortable with Prezentit's handling of that data.