daytona-recording-artifacts — Claude Code and Codex skill: screenshots
daytona-recording-artifacts turns a Daytona UI run into reviewable proof: numbered PNG frames per step, a browsable HTML index, and an MP4 only where motion matters.
LicenseRef-Proprietary ★ 7,523 updated 2026-10-29
npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a claude-codeWhat daytona-recording-artifacts does
Hand the skill a UI flow running inside a Daytona sandbox and it assembles the evidence pack. Every key state becomes a numbered PNG such as 01-auth-landing.png, and the frames land on a single index.html with labels, next to the branch, commit and sandbox name. A python3 -m http.server 8090 inside the sandbox serves that folder, and daytona preview-url gives you a link you can paste into a pull request.
Video stays reserved for motion: streamed chat text, spinners that resolve, transitions, drag-and-drop. Stop the capture with .devcontainer/stop-daytona-recording.sh, since killing the process hard corrupts the MP4, then read the duration with ffprobe before treating the clip as evidence. The wrapper .devcontainer/test-on-daytona.sh takes [branch-or-commit] --artifacts-volume for screenshots alone or --record-video to add the clip, writing into ipollowork-eval-artifacts:/daytona-artifacts.
Preview links do not outlive the sandbox. Files remain under /daytona-artifacts while the old daytonaproxy address fails, so start the sandbox again and request a fresh URL. Look at the PNG yourself before linking it: a native picker or a toast sitting over the frame kills the proof.
What it helps with
- attach per-step screenshots to a pull request
- turn loose PNGs into one browsable proof page
- capture a short clip of streamed text or animations
- confirm an MP4 has real duration before sharing it
- rebuild the proof page after the sandbox restarts
Example prompts for the agent
- Run the login flow in the Daytona sandbox and give me frame-by-frame proof with screenshots.
- Record the onboarding walkthrough as video and embed the clip next to the frames in
index.html. - Check the recording with
ffprobeand hand me the proof link for the PR.
How to install daytona-recording-artifacts
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a claude-code2Manually: put the files in place
~/.claude/skills/daytona-recording-artifacts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/daytona-recording-artifacts/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a codex2Manually: put the files in place
.agents/skills/daytona-recording-artifacts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a cursor2Manually: put the files in place
.cursor/skills/daytona-recording-artifacts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Devin-AXIS/iPolloWork .opencode/skills/daytona-recording-artifacts2Manually: put the files in place
.github/skills/daytona-recording-artifacts/SKILL.md1Skills CLI (Vercel)
npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a gemini-cli2Platform CLI
gemini skills install https://github.com/Devin-AXIS/iPolloWork --path .opencode/skills/daytona-recording-artifactsManually: put the files in place
.devin/skills/daytona-recording-artifacts/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about daytona-recording-artifacts
How do I install daytona-recording-artifacts in Claude Code?
Run npx skills add Devin-AXIS/iPolloWork --skill daytona-recording-artifacts -a claude-code. The skill file lands at ~/.claude/skills/daytona-recording-artifacts/SKILL.md.
What does daytona-recording-artifacts do?
It gathers proof that a Daytona UI flow actually worked: numbered PNGs per step, an index.html page collecting them, and a short video in the same folder when the step involves motion.
Why did the artifact URL stop working?
Proxy addresses are not permanent. Once the sandbox stops, the old daytonaproxy URL fails even though the files sit in /daytona-artifacts, so restart the sandbox and artifact server and generate a new address.