How do I install the Keris Video Proof skill?

Run npx skillmds@latest add creative-int/keris-video-proof in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Keris Video Proof safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Keris Video Proof?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Keris Video Proof free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Keris Video Proof?

creative-int (@creative-int) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Keris Video Proof by creative-int — Agent Skill

Name: Keris Video Proof
Author: creative-int

Keris Video Proof

Turn what you just shipped into a short, narrated proof video — a receipt, not a recap, with every beat backed by real commits, PRs, and diffs. Use it for demos, walkthroughs, PR recaps, async handoffs, before/after comparisons, or any finished work that is easier to review on video. Also answers to "share-video". Do not use it for trivial answers, active back-and-forth, unfinished work, or anything that would expose secrets or private data.

creative-int 1ecffec 2.5 KB Updated Sep 17, 2026

File contents

Keris — video proof of what you shipped

Keris turns finished agent work into a short, narrated video where every beat is grounded in real commits, PRs, and diffs through the Keris GitHub app. The result is a receipt, not a recap — reviewers can trust what they are watching instead of taking a summary on faith.

Connect to the Keris MCP server at https://mcp.keris.video/mcp.

Use when

The user asks for a video, demo, walkthrough, recap, or async update.
Completed work is easier to review as a short video than as more chat.
You changed or reviewed UI, design, dashboards, charts, or other visual output.
A PR recap, handoff, bug reproduction, or before/after would be clearer on video.
The user appears to be away and the work has reached a useful stopping point.

Don't use when

The answer is short and textual.
The user is actively iterating in chat.
The task is not done.
The video would expose secrets, tokens, credentials, or private customer data.
The user explicitly says not to make a video.

How to use

Resolve the project. Call list_projects and pick the projectSlug that matches the repo or product you worked on. Pass it so Keris can bind the video to the right evidence.
Generate. Call generate_video with that projectSlug. Keris writes the narration, selects the on-screen evidence, and renders with the user's avatar.
Poll. Call get_video until status is completed or failed. The watchUrl is stable and shareable even while the video is still generating.
Share. Return the watch link: https://keris.video/v/{videoId}.

upload_video is only for a polished video you already recorded that does not need Keris narration. Never treat upload_video as proof that work happened — proof comes from generate_video binding to real commit/PR/diff evidence.

Output format

After Keris finishes, reply with:

the Keris watch URL (https://keris.video/v/{videoId})
one sentence on what the video proves

Keep it to those two things. The video carries the detail.

---name: keris-video-proofdescription: Turn what you just shipped into a short, narrated proof video — a receipt, not a recap, with every beat backed by real commits, PRs, and diffs. Use it for demos, walkthroughs, PR recaps, async handoffs, before/after comparisons, or any finished work that is easier to review on video. Also answers to "share-video". Do not use it for trivial answers, active back-and-forth, unfinished work, or anything that would expose secrets or private data.---# Keris — video proof of what you shippedKeris turns finished agent work into a short, narrated video where every beat isgrounded in real commits, PRs, and diffs through the Keris GitHub app. The resultis a **receipt, not a recap** — reviewers can trust what they are watching insteadof taking a summary on faith.Connect to the Keris MCP server at `https://mcp.keris.video/mcp`.## Use when- The user asks for a video, demo, walkthrough, recap, or async update.- Completed work is easier to review as a short video than as more chat.- You changed or reviewed UI, design, dashboards, charts, or other visual output.- A PR recap, handoff, bug reproduction, or before/after would be clearer on video.- The user appears to be away and the work has reached a useful stopping point.## Don't use when- The answer is short and textual.- The user is actively iterating in chat.- The task is not done.- The video would expose secrets, tokens, credentials, or private customer data.- The user explicitly says not to make a video.## How to use1. **Resolve the project.** Call `list_projects` and pick the `projectSlug` that matches the repo or product you worked on. Pass it so Keris can bind the video to the right evidence.2. **Generate.** Call `generate_video` with that `projectSlug`. Keris writes the narration, selects the on-screen evidence, and renders with the user's avatar.3. **Poll.** Call `get_video` until `status` is `completed` or `failed`. The `watchUrl` is stable and shareable even while the video is still generating.4. **Share.** Return the watch link: `https://keris.video/v/{videoId}`.`upload_video` is only for a polished video you already recorded that does notneed Keris narration. **Never treat `upload_video` as proof that work happened** —proof comes from `generate_video` binding to real commit/PR/diff evidence.## Output formatAfter Keris finishes, reply with:- the Keris watch URL (`https://keris.video/v/{videoId}`)- one sentence on what the video provesKeep it to those two things. The video carries the detail.

Frequently asked questions