Agent skill

Choruz Record Demo

by inclusionAI in inclusionAI/Choruz

Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.

Apache-2.0Auto-check passedDevelopment

Install Choruz Record Demo

skills CLI
$ npx skills add inclusionAI/Choruz --skill choruz-record-demo -a claude-code

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

GitHub CLI
$ gh skill install inclusionAI/Choruz choruz-record-demo --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/inclusionAI/Choruz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/choruz-record-demo .claude/skills/choruz-record-demo && 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
choruz-record-demo
GitHub stars
1k
Token cost
~1.1k tokens
SKILL.md length
570 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.

  • Requested recordings
  • SKILL.md covers Establish the demonstrated build, Plan and capture, Encode and verify and Publication is separate
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Not as an automatic media requirement for every GUI pull request

What it does

Choruz Record Demo is an agent skill from inclusionAI/Choruz. Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions. Use for requested recordings, not as an automatic media requirement for every GUI pull request.

Its SKILL.md is about 1.1k 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 Development, covering Pull requests. The licence is Apache-2.0.

When your agent uses it

  • Requested recordings
  • Not as an automatic media requirement for every GUI pull request

Example prompts

  • “/choruz-record-demo”

What it can do on your machine

Read from SKILL.md and the folder at commit 7509c40. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Choruz Record Demo loads about 1.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 570 words of instructions outside code blocks.

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

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 inclusionAI/Choruz at commit 7509c40, republished under its Apache-2.0 licence (© inclusionAI). 570 words, ~1,085 tokens.

Download SKILL.mdSave it as .claude/skills/choruz-record-demo/SKILL.md (or your agent's skills folder).
name
choruz-record-demo
description
Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions. Use for requested recordings, not as an automatic media requirement for every GUI pull request.

Record a Choruz demo

Produce a local, watchable demonstration of verified product behaviour. The evidence-chain decision owns the provenance and publication boundaries.

Establish the demonstrated build

Record the exact commit, checkout, serving origin, runtime mode and device revisions before capture. Use the repository's existing startup workflow after inspecting its configuration; do not improvise a second stack or overwrite a user's running workspace. A remote demonstration identifies both ends and the actual transport.

Use dedicated demonstration groups, workspaces and benign prompts. Prefer isolated browser state; when the user requests an existing authenticated browser, preserve it and record that exception. Never clear unrelated cookies, sessions or data to stage a demo.

Complete functional acceptance before recording a polished walkthrough. Real-product claims require real servers, transports and model rounds, not fixture agents, injected events or mocked responses. Keep failures visible in acceptance evidence even when the final showcase uses a subsequent successful run.

Plan and capture

Choose a compact story at the user's requested duration. For a two-minute overview, give each feature enough time to show an action and its observable result; omit features that cannot be demonstrated honestly. Keep a fixed, readable viewport and capture only the intended application region.

Discover the available browser or native recording capability and read its instructions before using it. Use the supported CUA surface for user interaction. Prefer continuous capture for terminal output and animation. State-based screenshot encoding is suitable for a short edited walkthrough, but label it as such rather than claiming real-time video.

Each scenario's frames must come from one causal run. Do not splice an old successful response into a newer failed interaction. Separate scenarios may become explicitly separated chapters, with their provenance retained. Wait for concrete, uniquely identified UI results rather than using elapsed time or an echoed prompt as proof. To demonstrate an Agent tool action, show its identity, status and result; a spinner or final chat sentence alone is insufficient.

Keep credentials, pairing codes, private conversations, unrelated browser tabs and notifications outside the recording. Stage safe demo content instead of editing the product's rendered content. Stop capture before entering authentication material. Retakes, omitted waits, speed changes and chapter transitions are editorial changes, not evidence that the original operation was faster.

Show full SKILL.md (200 more words)Show less

Encode and verify

Store raw captures and output outside tracked source paths. Use the available media encoder for the requested format; MP4 is appropriate for a two-minute video, while GIF suits short loops. Preserve readable text and enough final-state hold time. Do not replace an existing artifact without resolving its exact path.

Inspect the encoded artifact itself: verify duration, dimensions, frame count and file size with media probing, then play it or decode representative frames from its beginning, every chapter transition and its ending. Check crop, ordering, text legibility and sensitive content. Source screenshots alone do not verify the encoded result.

Deliver the absolute local artifact path with a concise provenance summary: demonstrated commits, local/remote setup, actual model execution, and any cuts or state-based capture. A demo supports only the scenarios it shows; it does not replace automated tests or the separate acceptance report.

Publication is separate

Recording does not authorize uploading media or editing a PR. Publish only when requested, verify the uploaded bytes and access path, and ensure the destination still refers to the demonstrated revision. Never commit recordings to main or a feature branch that will merge into main. Keep source-controlled skill instructions separate from generated media.

© inclusionAI, Apache-2.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 .agents/skills/choruz-record-demo of inclusionAI/Choruz.

Open the folder on GitHubat commit 7509c40

Compare with similar skills

Choruz Record Demo 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.

Choruz Record Demo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Choruz Record Demo this skillinclusionAI/Choruz1k—~1.1kAutomated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from inclusionAI/Choruz

All 11 skills in this repo
  • Choruz Archive Agent Notes

    inclusionAI/Choruz

    A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, classifies implemented…

    1k GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed
  • Choruz Merging Stacked PRs

    inclusionAI/Choruz

    A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…

    1k GitHub stars~866 tokensUpdated 4 days ago
    Auto-check passed
  • Choruz CI Test Reliability

    inclusionAI/Choruz

    Design, review, and diagnose Choruz tests and fixtures that can fail nondeterministically under CI concurrency: parallel Playwright workers sharing one PostgreSQL and one API, vitest workers, cargo…

    1k GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed
  • Choruz Code Review

    inclusionAI/Choruz

    A skill your agent uses when reviewing a pull request in this repository; orients the reviewer to Choruz's standards (AGENTS.md conventions, the PR test policy, Agent Notes, the CI gates) and the…

    1k GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed
  • Choruz Doc

    inclusionAI/Choruz

    Create, restructure, review, audit, or migrate Choruz Markdown documentation (docs/, README, AGENTS.md, the in-app docs pages) using one owner per fact, tier placement, executed-operation…

    1k GitHub stars~1.6k tokensUpdated 4 days ago
    Auto-check passed
  • Choruz Find Simplifications

    inclusionAI/Choruz

    A skill your agent uses when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or…

    1k GitHub stars~1.6k tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Choruz Record Demo

What does Choruz Record Demo do?

Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions. Choruz Record Demo is an agent skill from inclusionAI/Choruz. Record and verify a truthful Choruz product demo or browser workflow video, including real local and remote Agent interactions.

When should I use Choruz Record Demo?

Choruz Record Demo fits situations like: requested recordings; not as an automatic media requirement for every GUI pull request.

How do I install Choruz Record Demo in Claude Code?

Run `npx skills add inclusionAI/Choruz --skill choruz-record-demo -a claude-code`. Or copy the skill folder (.agents/skills/choruz-record-demo in inclusionAI/Choruz) into .claude/skills/choruz-record-demo in your project. Claude Code loads it when a task matches its description.

How do I install Choruz Record Demo in Codex?

Run `npx skills add inclusionAI/Choruz --skill choruz-record-demo -a codex`. Or copy the skill folder (.agents/skills/choruz-record-demo in inclusionAI/Choruz) into .agents/skills/choruz-record-demo in your project. Codex loads it when a task matches its description.

Can I use Choruz Record Demo 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 inclusionAI/Choruz --skill choruz-record-demo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/choruz-record-demo, .gemini/skills/choruz-record-demo, .github/skills/choruz-record-demo and .opencode/skills/choruz-record-demo in your project.

What does Choruz Record Demo need to run?

SKILL.md names no scripts, command-line tools or credentials: Choruz Record Demo is instructions for the agent only.

Does Choruz Record Demo access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Choruz Record Demo 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 Choruz Record Demo use?

Choruz Record Demo is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Choruz Record Demo use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Choruz Record Demo?

Skills that share tags, products or a category with Choruz Record Demo: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Choruz Record Demo?

inclusionAI (a GitHub organization) maintains it in inclusionAI/Choruz, which has 1,017 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

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