Agent skill

Verification

by 0xsline in 0xsline/OpenChatCut

A skill your agent uses when checking whether agent edits are reflected in the OpenChatCut project and editor.

AGPL-3.0Auto-check passedMedia & Creative

Install Verification

skills CLI
$ npx skills add 0xsline/OpenChatCut --skill verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 0xsline/OpenChatCut verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/0xsline/OpenChatCut.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/agent/skills/verification .claude/skills/verification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verification
GitHub stars
2.2k
Token cost
~1.3k tokens
SKILL.md length
678 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when checking whether agent edits are reflected in the OpenChatCut project and editor.

  • Works in 2 steps: read_project for structure: assets,… → A visual capture path for rendered…
  • Checking whether agent edits are reflected in the OpenChatCut project and editor
  • Calls npx
  • Tasks that involve Video production

What it does

Verification is an agent skill from 0xsline/OpenChatCut. Use when checking whether agent edits are reflected in the OpenChatCut project and editor.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Media & Creative, covering Video production. The repository describes itself as: Open-source, local-first conversational AI video editor with a professional multi-track timeline, Agent Skills, MCP integration, and Remotion rendering. The licence is AGPL-3.0.

When your agent uses it

  • Checking whether agent edits are reflected in the OpenChatCut project and editor
  • Tasks that involve Video production

Example prompts

  • “/verification”

Requirements

  • Node.js

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. read_project for structure: assets, tracks, items, frame placement, timeline duration.
  2. A visual capture path for rendered evidence at exact frames.

What it can do on your machine

Read from SKILL.md and the folder at commit 2e6f4a2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verification loads about 1.3k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 678 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 0xsline/OpenChatCut at commit 2e6f4a2, republished under its AGPL-3.0 licence (© 0xsline). 678 words, ~1,264 tokens.

Download SKILL.mdSave it as .claude/skills/verification/SKILL.md (or your agent's skills folder).
name
verification
description
Use when checking whether agent edits are reflected in the OpenChatCut project and editor.

Verification

Use the lowest verification level that proves the requested result:

LevelRequired evidence
L0Static checks such as the focused verification script, npx tsc --noEmit, tests, and build.
L1A real Agent run against the editor at localhost:5199, followed by structural and rendered evidence.
L2The packaged desktop app completing the user scenario, including human visual review where automation is insufficient.

Runtime behavior changes require L0 + L1. Release and desktop-only changes also require L2 when the packaged app is the behavior under test.

Prefer two signals:

  1. read_project for structure: assets, tracks, items, frame placement, timeline duration.
  2. A visual capture path for rendered evidence at exact frames.

Use view_timeline_frames for composed timeline proof. This verifies the edited OpenChatCut timeline: trims, layers, captions, effects, markers, placeholders, crops, transitions, and layout.

For raw source-asset frame inspection, choose the cheapest path based on where the bytes live:

  • The agent in this build has no local filesystem access; all source bytes live in the project media store (/media/uploads/). Use view_asset_frames with the project asset id — the server takes an ffmpeg contact-sheet fast path automatically, so it is already the cheapest source-frame route.
  • view_timeline_frames renders the composed timeline (the editor-truth check); view_asset_frames samples raw source frames. Pick by what you are verifying.
  • There is no separate get_contact_sheet tool in this build — the contact sheet is what view_asset_frames / view_timeline_frames already return.

Use local/remote source-frame artifacts only for source understanding, moment selection, and rough trim decisions, not as edited output or timeline proof.

For local-only or upload-in-progress media, composed timeline proof may be blocked until the asset has bytes available to the renderer. Source-frame inspection via view_asset_frames still works as long as the asset's bytes are on disk (/media/uploads/).

If both visual proof paths are blocked, ask the user to inspect the OpenChatCut editor directly and note the blocker explicitly.

Useful checks:

  • After import: read_project({ "view": "assets", "assetId": "<prefix>" })
  • After move/trim: read_project({ "view": "timeline" })
  • After visual overlay or MG on any timeline media: view_timeline_frames({ "frames": [30, 45, 75] }), then look at the returned frames.
  • For user-requested source selection or visual moment picking: sample stills with view_asset_frames and inspect them. Use that only to choose source files, moments, and rough trims. Build the visible edit as OpenChatCut timeline items. Do not treat raw source inspection as timeline verification or as permission to produce the edited video elsewhere.
  • For source-frame inspection: call view_asset_frames({"assetId":"...","sourceTimesMs":[...]}) after read_project({"view":"assets"}) confirms the asset id/type. Prefer this over asking the user to reattach the file.
  • For local-only visual verification: upload/register cloud-readable media before relying on connector visual proof.
  • For no-source validation: confirm the tool manifest exposed the parameters you used, then record the visible proof in the trace log.
Show full SKILL.md (232 more words)Show less

When talking about seconds, verify the fps from read_project or use adapter tools that resolve fps internally.

When reporting a timeline item location, use only the latest read_project structure for track alias, item id, start, duration, and asset id. Do not report planned/default tracks or tool-call intent as verified placement.

Do not treat a command-line JSON response alone as sufficient when the user asks whether the editor reflects the result. Use the editor URL or visual proof when practical.

Real Agent transcript check

After every L1 Agent run, inspect the complete chat record before reporting success:

  1. Read the final assistant response and every tool row created by the run.
  2. Expand failed or warning rows and record the exact error.
  3. Check for aborted turns, repeated retries, stale proposals, incomplete jobs, and tool results that the final response incorrectly describes as successful.
  4. Compare the latest read_project result with the visible timeline.
  5. For visual edits, inspect returned timeline frames rather than trusting the assistant summary.

A run with a correct-looking timeline but an unreported tool error is not a clean pass. Fix the cause or report the remaining error explicitly.

If verification fails, classify the gap before changing tools:

  • tool description or schema was insufficient
  • skill instructions were missing a step
  • read_project did not expose enough state
  • editor authorization did not complete
  • media/transcription pipeline failed
  • cloud render/editor observation was blocked

© 0xsline, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/agent/skills/verification of 0xsline/OpenChatCut.

Open the folder on GitHubat commit 2e6f4a2

Compare with similar skills

Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verification this skill0xsline/OpenChatCut2.2k—~1.3kAutomated safety check: PassAGPL-3.0
HyperFrames Animationheygen-com/hyperframes59k3 repos~2.1kAutomated safety check: PassApache-2.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.4k6 repos~3.2kAutomated safety check: NotesApache-2.0
Faceless Explainer Videoheygen-com/hyperframes59k3 repos~7.7kAutomated safety check: NotesApache-2.0
Video Understandcalesthio/OpenMontage65k—~841Automated safety check: PassAGPL-3.0
Video ShotcraftVincentwei1021/video-shotcraft11k—~2.6kAutomated safety check: PassApache-2.0

Similar skills

  • HyperFrames Animation

    heygen-com/hyperframes

    Collects motion rules, scene blueprints, transitions and runtime adapters for HyperFrames video compositions, with GSAP as the default animation runtime.

    59k GitHub starsUsed in 3 repos~2.1k tokens
    Media & CreativeAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.4k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • Faceless Explainer Video

    heygen-com/hyperframes

    Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.

    59k GitHub starsUsed in 3 repos~7.7k tokens
    Media & CreativeAuto-check: notes
  • Video Understand

    calesthio/OpenMontage

    Understand video content locally using ffmpeg frame extraction and Whisper transcription.

    65k GitHub stars~841 tokensUpdated 5 days ago
    Media & CreativeAuto-check passed
  • Video Shotcraft

    Vincentwei1021/video-shotcraft

    Makes cinematic product videos with Remotion from shot recipe cards, a ready template, real page screenshots, camera moves and sound design, or builds a single animated shot.

    11k GitHub stars~2.6k tokensUpdated 3 days ago
    Media & CreativeAuto-check passed
  • Figma to HyperFrames

    heygen-com/hyperframes

    Imports Figma assets, brand tokens, components and motion into a HyperFrames video composition, using the Figma REST API with a connector or native export for shaders.

    59k GitHub starsUsed in 3 repos~4.5k tokens
    Media & CreativeAuto-check: notes

More from 0xsline/OpenChatCut

All 31 skills in this repo
  • OpenChatCut Video Editing

    0xsline/OpenChatCut

    Connects an MCP-capable agent to the local OpenChatCut video editor to inspect and edit projects through draft edit sessions, with manual approval by default.

    2.2k GitHub starsUsed in 1 repo~655 tokens
    Auto-check passed
  • Video Shader Generator

    0xsline/OpenChatCut

    Generates WebGL shaders for video effects, transitions, masks and color grades in the OpenChatCut editor, trying built-in catalog effects such as zoom before making anything new.

    2.2k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • AI Image Generation

    0xsline/OpenChatCut

    Generates still images through the submit_image tool, choosing among Fal.ai, gpt-image-2, nano-banana, MiniMax image-01 and Grok Imagine by configured keys.

    2.2k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Livestream to Clips

    0xsline/OpenChatCut

    Cuts a livestream recording into evidence-backed, platform-ready clips by combining transcript, visual, audio and genre-specific signals.

    2.2k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Music Generation

    0xsline/OpenChatCut

    Generates instrumentals, songs, soundtracks and covers through Mureka, MiniMax, Atlas Cloud or Sonilo using the `submit_music` tool.

    2.2k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • AI Video Generation

    0xsline/OpenChatCut

    Submits AI video generation jobs to Fal.ai, Seedance, Kling, MiniMax Hailuo, xAI Grok Imagine or OFox for text-to-video, image-to-video, transitions and clip extension.

    2.2k GitHub stars~4.3k tokensUpdated yesterday
    Auto-check passed

Questions about Verification

What does Verification do?

A skill your agent uses when checking whether agent edits are reflected in the OpenChatCut project and editor. Verification is an agent skill from 0xsline/OpenChatCut. Use when checking whether agent edits are reflected in the OpenChatCut project and editor.

When should I use Verification?

Verification fits situations like: checking whether agent edits are reflected in the OpenChatCut project and editor; tasks that involve Video production.

How do I install Verification in Claude Code?

Run `npx skills add 0xsline/OpenChatCut --skill verification -a claude-code`. Or copy the skill folder (src/agent/skills/verification in 0xsline/OpenChatCut) into .claude/skills/verification in your project. Claude Code loads it when a task matches its description.

How do I install Verification in Codex?

Run `npx skills add 0xsline/OpenChatCut --skill verification -a codex`. Or copy the skill folder (src/agent/skills/verification in 0xsline/OpenChatCut) into .agents/skills/verification in your project. Codex loads it when a task matches its description.

Can I use Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 0xsline/OpenChatCut --skill verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification, .gemini/skills/verification, .github/skills/verification and .opencode/skills/verification in your project.

What does Verification need to run?

Going by SKILL.md and its folder, Verification needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Verification access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verification use?

Verification is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verification use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verification?

Skills that share tags, products or a category with Verification: HyperFrames Animation (heygen-com/hyperframes, 59k stars), Stitch to Remotion Walkthrough Videos (google-labs-code/stitch-skills, 8.4k stars), Faceless Explainer Video (heygen-com/hyperframes, 59k stars) and Video Understand (calesthio/OpenMontage, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verification?

0xsline (a GitHub user) maintains it in 0xsline/OpenChatCut, which has 2,178 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.

Source: 0xsline/OpenChatCut on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.