deepgram-debug-bundle
Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. "deepgram diagnostic", "deepgram debug bundle". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deepgram-debug-bundle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Deepgram Debug Bundle ## Current State !`node --version 2>/dev/null || echo 'Node.js not installed'` !`npm list @deepgram/sdk 2>/dev/null | grep deepgram || echo '@deepgram/sdk not found'` !`python3 --version 2>/dev/null || echo 'Python not installed'` ## Overview Collect comprehensive debug information for Deepgram support tickets. Generates a sanitized bundle with environment info, API connect
What does the deepgram-debug-bundle skill do?
Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. "deepgram diagnostic", "deepgram debug bundle". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deepgram-debug-bundle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
