mcpField
V
verification

verification

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

About verification

A ChatCut skill for checking editing results with structural and visual evidence. It describes cost-conscious verification methods and how to report blockers without claiming unverified success.

Key features

  1. 01Re-read affected project scope
  2. 02Inspect composed timeline frames
  3. 03Check audio and motion with exports
  4. 04Report verification blockers

Use cases

  1. 01Verify trims, layers, captions, or effects
  2. 02Check audio in an edited timeline
  3. 03Investigate a renderer or readiness issue

Install

Copy the command and run it in a terminal.

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

After installing, type/verificationin Claude Code to confirm it loaded.

Details

From the project README

Verification

Use both structural and visual evidence when the requested result is visible:

  1. Re-read the affected scope with read_project, preview_timeline, inspect_item, browse_assets, or inspect_asset as appropriate. Use the latest response for ids, tracks, timing, and readiness.
  2. Inspect composed timeline frames through the visual tool exposed by the current manifest. Successful rendering or mutation metadata is not visual proof until the returned pixels are inspected.

Check your own work the cheapest way that answers the question: preview_timeline frames for the picture, a format:"audio" export to hear audio, and a local 480p range export to watch motion. Never make a full-resolution or cloud export for a self-check.

Use local source bytes for raw source understanding when the original path is available. Use inspect_asset when the original is not locally available. Source frames help select moments but do not prove timeline composition; use composed timeline frames for trims, layers, captions, effects, crops, transitions, and Motion Graphics.

If signed frame URLs are returned and the host cannot inspect them directly, download the complete shell-quoted URLs into a temporary directory and inspect those files. Do not report visual success from URLs alone.

If visual proof is blocked by upload/readiness or renderer state, report the blocker explicitly and ask the user to inspect the live editor when appropriate. Never convert a failed verification into an unsupported tool fallback or a false completion claim.

Comments

Markdown supported