mcpField
K
known-errors

known-errors

github.com/chatcut-incCreative & media988142 installsUpdated today
Repository

About known-errors

known-errors is a ChatCut skill for agents that provides guidance on handling tool errors and avoiding unsafe retries across editing, media, generation, and export tasks.

Key features

  1. 01Treat current tool schemas as authoritative
  2. 02Resolve timeline conflicts without forced writes
  3. 03Refresh stale IDs before retrying
  4. 04Follow structured media-conversion retries
  5. 05Verify mutations and handle export failures

Use cases

  1. 01Respond to a same-track overlap rejection
  2. 02Recover from stale timeline identifiers
  3. 03Handle an unsupported media conversion
  4. 04Diagnose a failed export or missing output

MCP support

The skill advises agents using ChatCut MCP tools to follow current schemas and structured errors when editing, importing media, generating content, and exporting.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/chatcut-inc/agent-plugin --skill known-errors

After installing, type/known-errorsin Claude Code to confirm it loaded.

Details

From the project README

Known Errors

Treat the active MCP tool schema and returned structured error as authoritative. Do not retry with remembered legacy payloads when the current manifest differs.

Mutation Rejections

  • On same-track overlap, do not force the write or silently delete the conflicting item. Decide whether content is sequential or layered, choose an available track when appropriate, or ask which item should win.
  • On locked-track or stale-id failures, refresh the affected timeline scope and retry only with current ids and state.
  • On validation errors, change only the rejected field or transaction shape; preserve unrelated project state.

Import And Media

  • Hosted plugin surfaces use the asset-import adapter and import_media; do not substitute backend-only push_asset or download_media calls when they are absent.
  • If media conversion fails, use the helper's structured retry when provided. Otherwise explain the unsupported source and ask for a compatible replacement; do not repeat the same failing editor import path.
  • Wait for upload only before byte-dependent operations. A known asset id can be used for metadata and timeline placement while bytes continue uploading.

Generation And Motion Graphics

  • Use only generation tools visible on the current host. Codex and Claude Code plugins direct-author Motion Graphics with create_motion_graphic_from_code; the built-in ChatCut Agent may expose submit_motion_graphic.
  • Preserve the original provider or content-policy failure. Do not spend credits on repeated identical retries or silently switch models.

Verification And Export

  • A successful mutation is not visual proof; load verification when the result must be seen.
  • Use track_export for render jobs. A failed local export is not by itself a reason to switch to cloud: fix the reported browser or timeline issue and retry locally. A blocked local export, or a completed one whose file is missing, follows the export fallback order: cloud only with the user's agreement, and ChatCut Desktop only when cloud cannot do it. If a cloud render cannot read an asset, resolve remote readiness through asset-import only with user permission, or report the limitation.

On auth or project-access errors, verify the exact project id and that the editor and plugin use the same ChatCut account before attempting code or infrastructure debugging.

Comments

Markdown supported