Upload demo videos, screenshots, and log bundles to a public R2 bucket for PR linking.
npx skills add https://github.com/dxos/dxos --skill hosting-artifacts
Please help me install this Agent Skill. Skill: hosting-artifacts Source: https://github.com/dxos/dxos/tree/main/.agents/skills/hosting-artifacts Command: npx skills add https://github.com/dxos/dxos --skill hosting-artifacts
Large binary artifacts like demo videos and screenshots cannot be committed to git or attached to GitHub PRs by an automated agent, leaving reviewers with no way to see visual evidence of a change. This Skill publishes those files to a public Cloudflare R2 bucket over HTTPS and produces a verified link you can embed in a PR body, issue, or Linear ticket.
Upload my demo video /tmp/demo/demo.webm to the shared R2 artifacts bucket and give me the verified public URL to paste into my pull request.
High-intent search queries and answers about installing and using this skill.
Run the upload-artifact.mjs script with the file path and a slug; it uploads to the agent-artifacts R2 bucket, verifies the public URL, and prints the link. Embed it in the PR body as a labelled markdown link with duration and file size.
Use a Node.js script that signs S3 requests with SigV4 using the built-in crypto module. It needs only the R2_ACCESS_KEY_ID and R2_SECRET_ACCESS_KEY environment variables, so it works in sandboxes with no installed tooling.
No. GitHub only rewrites user-attachments asset URLs into video players, and those require a browser drag-and-drop session. The practical convention is a labelled plain link to the video hosted on R2, or an embedded image for stills.
The 403 comes from rclone's bucket preflight check, not the data operation, when using scoped R2 API tokens. Add --s3-no-check-bucket or set no_check_bucket = true in the remote configuration to bypass it.
R2 serves back the exact content type stored at upload time, and wrangler infers nothing. Re-upload with the correct --content-type flag, such as video/webm, so browsers render it inline instead of downloading.
Never upload credentials visible on screen, real user data, feedback logs containing user content, or anything from secrets files. Public R2 URLs are unauthenticated and may be cached or indexed even after deletion.
civitaiCapture live feature screenshots and assemble them into a shareable walkthrough page.
kvnxiaoCreate per-ticket git worktrees and generate GitHub PRs for Linear tickets.
gmanch94Run Bandit, pip-audit, and detect-secrets scans for vulnerabilities and credential leaks.
cavit99Authenticate GitHub CLI workflows for accessing GitHub data and repositories.
