verification
GitHub验证 ChatCut 插件编辑结果是否准确反映在项目结构和时间线输出中。通过读取项目结构、检查资产及查看合成时间线帧,结合视觉证据确认渲染或修改效果,确保用户看到的最终画面与预期一致,避免虚假成功报告。
Trigger Scenarios
Install
npx skills add ChatCut-Inc/agent-plugin --skill verification -g -y
SKILL.md
Frontmatter
{
"name": "verification",
"description": "Hosted ChatCut plugin sessions only (the `chatcut` MCP server). If the conversation is driving ChatCut Desktop (a `chatcut_desktop*` MCP server), load this skill only when the user explicitly chooses the plugin\/web surface — desktop sessions otherwise ship their own instructions and tools. Verify that ChatCut plugin edits are reflected in project structure and visible timeline output before reporting success."
}
Verification
Use both structural and visual evidence when the requested result is visible:
- Re-read the affected scope with
read_project,preview_timeline,inspect_item,browse_assets, orinspect_assetas appropriate. Use the latest response for ids, tracks, timing, and readiness. - 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.
Hosted viewer capture needs the target project open in a connected ChatCut editor tab. If the tool reports that no editor is available, open the clean editor URL or ask the user to open it, then retry the same frame. This connector does not silently render viewer frames in the cloud.
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.
Version History
- e8ebd99 Current 2026-11-02 11:55
- 0dd9c5e 2026-09-22 02:33


