360 Secure SkillHub
360 安全技能中心

verification

面向 ChatCut 托管插件会话的验证技能:要求先用读取项目、预览时间线、检查条目或素材等工具复核受影响范围,再检查合成后的时间线画面或音频,以结构加视觉双重证据判断编辑是否生效;被阻断时须明确说明原因,不得用降级工具或虚假完成替代。

分类:创作
ChatCut-Inc
热度 0.00
最近更新 2026-10-24 23:16:15

安装

发给 Agent
帮我安装这个技能:npx secure-skills-cli add chatcut-inc/agent-plugin/verification
兼容性
Chatcut 专属
联网要求
需要联网
数据出网
必须出网
Metadata
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:

  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.