Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Poppify/poppify-claude-plugin --skill poppify-troubleshootgit clone --depth 1 https://github.com/Poppify/poppify-claude-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/poppify/poppify-claude-plugin/poppify-troubleshoot)<a href="https://agentmods.dev/skills/poppify/poppify-claude-plugin/poppify-troubleshoot"><img src="https://agentmods.dev/badge/skills/poppify/poppify-claude-plugin/poppify-troubleshoot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/poppify/poppify-claude-plugin/poppify-troubleshoot"><img src="https://agentmods.dev/badge/skills/poppify/poppify-claude-plugin/poppify-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00150 | $0.02633 |
| Opus 5 | $0.00075 | $0.01316 |
| Sonnet 5 | $0.00030 | $0.00527 |
| Haiku 4.5 | $0.00015 | $0.00263 |
Grade A, and why
poppify-troubleshoot scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If `videoUrl` returned but the URL doesn't open: the URL has expired and Poppify doesn't persist videos beyond the ~7-day TTL (cost-control). Re-`confirm` charges seeds again. Tell the user to save the file within the wi How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Poppify render troubleshooting
Find the symptom that matches, then take the suggested action. Most root causes here trace to schema drift, library-asset state, or text/duration mismatches — not random renderer failures.
Symptom → Root cause → Action
"The live-motion slide has no sound"
Most likely: the clip genuinely has no audio stream. Veo 3.1 always generates audio, but Seedance and Kling are video-only — check which provider rendered it (set_model / get_capabilities.live_motion.availableModels). A video-only provider falls back to the ElevenLabs path, so that slide is silent unless you attach narration.
Also check: in a same-image run, several slides share one clip at different offsets and the audio is taken once, from the slide that starts the run. Later slides in that run are silent by design.
Not the cause any more: the composer used to strip the track with -an. It no longer does — VideoGenerator extracts the clip's audio and mixes it through the voiceover path.
"Two voices are talking over each other on one slide"
Root cause: a live clip's audio now REPLACES a generated voiceover on the same slide, so this shouldn't happen — if it does, the voiceover was attached to a different slide number than the live clip.
Action: get_slide_plan and confirm the voiceoverSlides index matches the slide carrying motionMode:"live". Never budget add_narration for a live slide; its audio is already there.
"No audio in the finished video"
"No audio in the finished video"
Most likely: library audio asset was attached but resolvedUrl ended up empty (renderer can only download URLs, not asset IDs).
Action: call get_result and check session.selectedAudio.resolvedUrl. If null/empty:
get_music_library({ apiKey }) // get fresh assetIds
apply_session_patch({ sessionId, audio: { source: "library", assetId: <new id> } })
confirm({ sessionId, apiKey }) // re-render (seeds re-charged)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 149 lines · 0 tokens per session scan A 9637c7939c70
poppify-troubleshoot is a skill published in the GitHub repository Poppify/poppify-claude-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 150 tokens to every session and 2,633 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
de-vibe
Audit and fix the tells that software was vibe-coded / AI-generated, then give it a small distinctive identity, so it ships looking handcrafted and professional. Use whenever the user says "de-vibe", "does this look AI-generated / vibe coded?", "make this look shippable / handcrafted / professional", "remove the AI…
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…