video-artifact-publish

Publish rendered video outputs as GitHub Actions artifacts with traceable run links.

11|3|Updated Feb 2, 2026

Search Tags:#workflow #CI/CD #video #traceability #github-actions #artifact #manim

Ready to run

npx skills add https://github.com/gqy20/IssueLab --skill video-artifact-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: video-artifact-publish
Source: https://github.com/gqy20/IssueLab/tree/main/agents/video_manim/.claude/skills/video-artifact-publish
Command: npx skills add https://github.com/gqy20/IssueLab --skill video-artifact-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures video render outputs are stored as accessible, verifiable artifacts, enabling reproducibility and easy sharing.

Core Features & Use Cases

Artifact collection: gathers artifacts from outputs/manim/** and media/videos/** after rendering.
Artifact publishing: uploads artifacts using actions/upload-artifact@v4 with explicit retention days.
Traceable results: includes run URL and artifact name in the final issue comment, with source URLs for script content.

Quick Start

After a render completes, invoke the video-artifact-publish workflow to upload artifacts and post a traceable summary. Example flow: the workflow collects outputs, uploads them as an artifact, and reports the run URL, artifact name, and video paths back to the issue or PR.

Frequently Asked Questions about video-artifact-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I publish video artifacts with traceable links in GitHub Actions?▼

You can publish video artifacts with traceable links by automating the collection of rendered outputs and uploading them via actions/upload-artifact@v4, which generates an accessible run URL, artifact name, and video path for your issue comments.

How do I collect Manim video outputs for CI/CD traceability?▼

To collect Manim video outputs for CI/CD traceability, the workflow gathers rendered files from outputs/manim/** and media/videos/** directories, uploading them as verifiable artifacts with explicit retention days.

Does actions/upload-artifact@v4 support posting source URLs and video paths to issue comments?▼

Yes, actions/upload-artifact@v4 supports traceability by enabling a workflow that posts a final issue comment containing the run URL, artifact name, video path, and source URLs for script content.

What is the best way to share rendered video outputs from automated workflows?▼

The best way to share rendered video outputs is to package them as GitHub Actions artifacts, ensuring they are stored with accessible run links and verifiable sources for reproducibility and easy sharing.

Can I use this artifact publishing workflow for non-Manim video rendering pipelines?▼

Yes, you can use this artifact publishing workflow for non-Manim pipelines as long as your rendered video outputs are collected from the expected outputs/manim/** and media/videos/** directory paths.

Why include run URLs and source URLs when uploading video artifacts?▼

Including run URLs and source URLs when uploading video artifacts ensures reproducibility and easy sharing by providing verifiable sources and accessible links directly in the final issue comment.