CodexBar Live QA
steipete/CodexBar
Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.
Produces a browsable screenshot index, and video when motion matters, from a Daytona UI journey as presentation material next to a PR's test evidence.
Install Daytona Recording Artifacts
$ npx skills add different-ai/openwork --skill record-a-demo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai/openwork record-a-demo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/record-a-demo .claude/skills/record-a-demo && rm -rf skills-srcUse ~/.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/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .claude/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add different-ai/openwork --skill record-a-demo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai/openwork record-a-demo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/record-a-demo .agents/skills/record-a-demo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .agents/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill record-a-demo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai/openwork record-a-demo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/record-a-demo .cursor/skills/record-a-demo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .cursor/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/different-ai/openwork.git --path .opencode/skills/record-a-demo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add different-ai/openwork --skill record-a-demo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai/openwork record-a-demo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/record-a-demo .gemini/skills/record-a-demo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .gemini/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install different-ai/openwork record-a-demoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add different-ai/openwork --skill record-a-demo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/record-a-demo .github/skills/record-a-demo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .github/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add different-ai/openwork --skill record-a-demo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai/openwork record-a-demo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/record-a-demo .opencode/skills/record-a-demo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "record-a-demo" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/record-a-demo into .opencode/skills/record-a-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "record-a-demo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
record-a-demo- GitHub stars
- 24k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 892 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Produces a browsable screenshot index, and video when motion matters, from a Daytona UI journey as presentation material next to a PR's test evidence.
- Works in 5 steps: Serve a directory from the sandbox on… → At each important state, capture a… → Generate a browseable index.html with… → …
- Adding screenshots of a UI journey to a pull request
- SKILL.md covers Default supplementary format:…, Recording Standard (video,…, The Volume and Start With Artifacts, plus 5 more sections
- Calls python3, bash and curl
What it does
These artifacts supplement the pass or fail evidence from an `@openwork/testkit` spec run through `run-tests` and never replace it. The default format is an HTML page of named PNG screenshots, one per step, which is easy to review on any device. MP4 video is used only when the proof needs motion, such as streaming text, spinners, animations or drag-and-drop, and then it is embedded in the same page next to the still frames.
The steps: serve a proof-frames folder from the sandbox on port 8090 with a Python HTTP server, capture a `browser_screenshot` at each important state and upload it under a numbered name like `01-auth-landing.png`, generate an `index.html` as a responsive grid showing branch, commit and sandbox name, get the public URL with `daytona preview-url`, and post the index link in the PR body. If the preferred `/daytona-artifacts` volume is unavailable or not writable, `/workspace/proof-frames` is the fallback.
When your agent uses it
- Adding screenshots of a UI journey to a pull request
- Showing a streaming or animated interaction that a still frame cannot capture
- Publishing a browsable frame index from a Daytona sandbox
Example prompts
- “Capture each step of the sign-up flow and build a screenshot index for the PR.”
- “Record a short video of the streaming chat reply and embed it with the frames.”
- “Post the proof-frames URL in the PR description.”
Requirements
- A Daytona sandbox and the `daytona` CLI
- An `@openwork/testkit` spec that has already been run
- `python3` in the sandbox to serve the frames
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Serve a directory from the sandbox on port 8090
- At each important state, capture a browser_screenshot locally and upload
- Generate a browseable index.html with all frames as labeled images in a
- Get the public URL
- Post the index URL in the PR body. Individual frame PNGs are also directly
What it can do on your machine
Read from SKILL.md and the folder at commit 4ccc9e9. 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:
python3bashcurlgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl and git, 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
Daytona Recording Artifacts loads about 2.2k tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 892 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 892 words (~2,207 tokens).
“Use this skill to collect supplementary presentation artifacts for a Daytona UI journey. Pass/fail evidence comes from an @openwork/testkit spec and its ambient test evidence; use run-tests before declaring a verdict. Custom screenshots or recordings never replace the test run…”
- name
- record-a-demo
Files
Just SKILL.md in .opencode/skills/record-a-demo of different-ai/openwork.
Open the folder on GitHubat commit 4ccc9e9
Compare with similar skills
Daytona Recording Artifacts 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Daytona Recording Artifacts this skilldifferent-ai/openwork | 24k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| CodexBar Live QAsteipete/CodexBar | 22k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Senior QAnicepkg/auto-company | 194 | 3 repos | ~1.1k | Automated safety check: Notes | None | |
| Senpi Agent QA Harnesscode-yeongyu/senpi | 472 | — | ~2.7k | Automated safety check: Notes | MIT | |
| tmux Real User TestingQwenLM/qwen-code | 28k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Senior QA
nicepkg/auto-company
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.
Senpi Agent QA Harness
code-yeongyu/senpi
Checks changes to the senpi coding agent by driving the real CLI from source in an isolated sandbox, over RPC, terminal UI, mock model and CLI smoke channels.
tmux Real User Testing
QwenLM/qwen-code
Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
More from different-ai/openwork
All 33 skills in this repoOpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
OpenWork Model Alias Manager
different-ai/openwork
Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.
Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Daytona Sandbox Operations
different-ai/openwork
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Related
Categories
Questions about Daytona Recording Artifacts
What does Daytona Recording Artifacts do?
Produces a browsable screenshot index, and video when motion matters, from a Daytona UI journey as presentation material next to a PR's test evidence. These artifacts supplement the pass or fail evidence from an `@openwork/testkit` spec run through `run-tests` and never replace it. The default format is an HTML page of named PNG screenshots, one per step, which is easy to review on any device.
When should I use Daytona Recording Artifacts?
Daytona Recording Artifacts fits situations like: adding screenshots of a UI journey to a pull request; showing a streaming or animated interaction that a still frame cannot capture; publishing a browsable frame index from a Daytona sandbox.
How do I install Daytona Recording Artifacts in Claude Code?
Run `npx skills add different-ai/openwork --skill record-a-demo -a claude-code`. Or copy the skill folder (.opencode/skills/record-a-demo in different-ai/openwork) into .claude/skills/record-a-demo in your project. Claude Code loads it when a task matches its description.
How do I install Daytona Recording Artifacts in Codex?
Run `npx skills add different-ai/openwork --skill record-a-demo -a codex`. Or copy the skill folder (.opencode/skills/record-a-demo in different-ai/openwork) into .agents/skills/record-a-demo in your project. Codex loads it when a task matches its description.
Can I use Daytona Recording Artifacts 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 different-ai/openwork --skill record-a-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/record-a-demo, .gemini/skills/record-a-demo, .github/skills/record-a-demo and .opencode/skills/record-a-demo in your project.
What does Daytona Recording Artifacts need to run?
Going by SKILL.md and its folder, Daytona Recording Artifacts needs the command-line tools its instructions call (python3, bash, curl and git). Our summary lists: A Daytona sandbox and the `daytona` CLI; An `@openwork/testkit` spec that has already been run; `python3` in the sandbox to serve the frames.
Does Daytona Recording Artifacts access the network?
SKILL.md contains no URLs. Its commands use curl and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Daytona Recording Artifacts 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 Daytona Recording Artifacts use?
Daytona Recording Artifacts has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Daytona Recording Artifacts use?
About 2.2k tokens (SKILL.md is roughly 8.8k 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 Daytona Recording Artifacts?
Skills that share tags, products or a category with Daytona Recording Artifacts: CodexBar Live QA (steipete/CodexBar, 22k stars), Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars), Senior QA (nicepkg/auto-company, 194 stars) and Senpi Agent QA Harness (code-yeongyu/senpi, 472 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Daytona Recording Artifacts?
different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,967 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.
Source: different-ai/openwork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.