agentmods.dev

troubleshoot-failed-generations

troubleshoot-failed-generations is a skill for Claude Code, Codex from egocen-vivideo/vivideo-toolchain. It costs 44 tokens per session (383 once invoked), scanned A, original, MIT.

A recovery guide for Vivideo AI video jobs that fail, return errors, or stay processing for too long.

In plain words
What is it for?
Use it to read error details, choose valid video settings, retry with a revised request, and check a delayed render later.
Why use it?
It helps identify whether a request needs changed settings, a valid model, more credits, or more time. It also helps avoid retrying a request that is already stuck or failed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 0repo 1mo ago A scan 44 tokens original MIT

Good fit Use it to read error details, choose valid video settings, retry with a revised request, and check a delayed render later.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations
View source ↗ egocen-vivideo/vivideo-toolchain
Install

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.

Any agent
npx skills add egocen-vivideo/vivideo-toolchain --skill troubleshoot-failed-generations
Clone the repo
git clone --depth 1 https://github.com/egocen-vivideo/vivideo-toolchain

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for troubleshoot-failed-generations

README.md
[![agentmods](https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations/github.svg)](https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations)
Your own site
<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations/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.

agentmods 80×15 button for troubleshoot-failed-generations

Your own site · 80×15
<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/troubleshoot-failed-generations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00383
Opus 5 $0.00022 $0.00192
Sonnet 5 $0.00009 $0.00077
Haiku 4.5 $0.00004 $0.00038

Measured 11d ago against content hash f12831a71009, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

troubleshoot-failed-generations scanned grade A with 0 findings 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 11d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/troubleshoot-failed-generations/SKILL.md · 27 lines

What it actually says

Troubleshoot failed generations

A video came back status: "failed"

  • The render failed server-side. error.message explains why; error.credits_refunded is normally true (you weren't charged for a failure).
  • Recovery: adjust the prompt (clearer, less ambiguous, policy-safe) and create again. For manual mode, try a different model or lower resolution/duration.
  • Don't retry the identical failing request expecting a different result.

A create call returned an error (not a video)

  • Read the structured error and follow handle-limits-and-errors:
    • invalid_request → fix the field in details (e.g. an unsupported resolution — details.allowed lists valid values).
    • unknown_model → pick a valid id from list_models.
    • insufficient_credits / upgrade_required → route to the links.* URL.

A render seems stuck (processing for a long time)

  • Use wait_for_video with a timeout instead of polling forever. If it times out, the render is genuinely still going — check again later with get_video.
  • If it never reaches a terminal state after a long time, the API has an internal stuck-render safety net that fails + refunds it; the status will flip to failed and credits return.

Always

  • Keep the request_id from the error for support.
  • Never claim success until get_video/wait_for_video returns completed.
  • Never expose or log the API key while debugging.
Changes

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.

  1. 11d ago First seen · 27 lines · 44 tokens per session scan A f12831a71009

Subscribe to this mod's changes

troubleshoot-failed-generations is a skill published in the GitHub repository egocen-vivideo/vivideo-toolchain (0 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 383 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Creative and media
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens