Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. Trigger: "deepgram debug", "deepgram support ticket", "collect deepgram logs", "deepgram diagnostic", "deepgram debug bundle".
71
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Security
1 medium severity finding. This skill can be installed but you should review these findings before use.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.70). The skill explicitly accepts and transcribes external audio (e.g., transcribeUrl in Step 4 / debug-logger.ts and the curl POST in Step 2 that posts a user-provided "url"), reads the transcription results into debug logs and summaries, and the support template invites providing audio URLs — meaning untrusted, user-provided third‑party content is fetched and its transcribed text is consumed and could influence subsequent debugging/output.
3022dd3
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.