video-assets
Skill151 starsChanged 3 months agoMITView on GitHub
Use when publishing, replacing, auditing, or linking cctop promo/demo video assets through GitHub Releases, especially the non-latest media-assets release. Trigger for requests like "upload the launch video", "add another video asset", "replace the README demo video", "where should this video live", "update media-assets", or "generate the README AVIF preview". Covers stable asset names, release selection, AVIF preview generation, README/site links, and avoiding v* product-release tags. Do not use for video narrative/storyboard work; use video-storyboard for that.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cctop-restartSkill
- releaseSkill
- swiftui-debuggingSkill
- video-storyboardSkill
- e2e-session-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 5 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Default release tag: media-assets.
- Very specific: line 13
Default release title: Media assets.
- Very specific: line 14
Always create media-only releases with --latest=false.
- Very specific: line 15
Do not use a v* tag for media-only work.
- Very specific: line 17
Keep full MP4s and other large rendered video out of git.
- Distinctive: line 18
Commit a small animated README preview only when the user explicitly chooses that route and the file is intentionally small.
- Very specific: line 19
Prefer stable purpose-based asset names over dates: cctop-launch.mp4, cctop-launch-720p.mp4, cctop-launch-preview.avif.
- Very specific: line 26
Check existence and size with ls -lh.
- Very specific: line 27
Check duration/codec with ffprobe when available.
- Very specific: line 30
Use media-assets for reusable README/demo/launch assets.
- Very specific: line 31
Use an existing app release such as v0.18.4 only with explicit user direction.
- Distinctive: line 36
Use a new asset name when history matters or two variants should coexist.
- Distinctive: line 38
Default launch asset set:
- Very specific: line 44
Before creating a release, uploading, or replacing assets, state: release tag, source file, asset name, whether --clobber will be used, and …
- Distinctive: line 45
Wait for explicit approval unless the user's latest request already clearly authorizes the upload/update.
- Distinctive: line 46
Never publish a media release as latest.
- Very specific: line 54
Use --dry-run first when checking paths or explaining what will happen:
- Very specific: line 100
Use cctop-launch-preview.avif from the same media-assets release as the MP4s unless the user explicitly wants a committed preview file.
- Very specific: line 102
Avoid releases/latest/download/...
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video Assets
Manage cctop video files as GitHub Release assets, not as committed repo binaries. The default pattern is one non-latest media release that acts as a stable asset bucket.
Rules
- Default release tag:
media-assets. - Default release title:
Media assets. - Always create media-only releases with
--latest=false. - Do not use a
v*tag for media-only work. In cctop,v*tags trigger.github/workflows/release.yml: app builds, notarization, GitHub Release creation, Sparkle appcast, and Homebrew updates. - Attach a video to a real
v*release only when the user explicitly asks and the video truthfully demonstrates that shipped app version. - Keep full MP4s and other large rendered video out of git. Do not commit
video/projects/*/.video-build/. - Commit a small animated README preview only when the user explicitly chooses that route and the file is intentionally small.
- Prefer stable purpose-based asset names over dates:
cctop-launch.mp4,cctop-launch-720p.mp4,cctop-launch-preview.avif. - For launch video uploads, always generate and upload the AVIF preview alongside the MP4s so the README preview and full video stay in sync.
Workflow
- Identify the source files.
- Launch defaults:
video/projects/launch/.video-build/launch.mp4andvideo/projects/launch/.video-build/launch-720p.mp4. - Check existence and size with
ls -lh. - Check duration/codec with
ffprobewhen available.
- Launch defaults:
- Pick the release target.
- Use
media-assetsfor reusable README/demo/launch assets. - Use an existing app release such as
v0.18.4only with explicit user direction. - Inspect before mutating:
gh release view media-assets --repo st0012/cctop.
- Use
- Pick stable asset names.
- Reusing the same asset name plus
--clobberkeeps the download URL stable. - Use a new asset name when history matters or two variants should coexist.
- Remember:
gh release upload file.mp4#Labelsets a display label, not a stable download filename. Stage or copy the file to the intended asset filename before upload. - Default launch asset set:
cctop-launch.mp4fromlaunch.mp4cctop-launch-720p.mp4fromlaunch-720p.mp4cctop-launch-preview.avifgenerated fromlaunch-720p.mp4
- Reusing the same asset name plus
- Gate public mutations.
- Before creating a release, uploading, or replacing assets, state: release tag, source file, asset name, whether
--clobberwill be used, and the resulting download URL. - Wait for explicit approval unless the user's latest request already clearly authorizes the upload/update.
- Never publish a media release as latest.
- Before creating a release, uploading, or replacing assets, state: release tag, source file, asset name, whether
- Publish launch assets with the wrapper script. This is the default path for launch renders.
.agents/skills/video-assets/scripts/publish-launch-assets.sh --clobberUse --dry-run first when checking paths or explaining what will happen:
.agents/skills/video-assets/scripts/publish-launch-assets.sh --clobber --dry-runThe wrapper:
- Verifies both MP4s exist.
- Generates a fresh animated AVIF preview from the 720p MP4 with
ffmpeg. - Uploads all three assets to
media-assets. - Keeps the stable download URLs unchanged by reusing the same asset names.
- Upload individual assets only for non-launch one-offs.
.agents/skills/video-assets/scripts/upload-video-asset.sh \
--file video/projects/launch/.video-build/launch.mp4 \
--name cctop-launch.mp4 \
--clobberFor another video:
.agents/skills/video-assets/scripts/upload-video-asset.sh \
--file path/to/other-video.mp4 \
--name cctop-other-video.mp4The stable download URL shape is:
https://github.com/st0012/cctop/releases/download/media-assets/<asset-name>Launch URLs:
https://github.com/st0012/cctop/releases/download/media-assets/cctop-launch-preview.avif
https://github.com/st0012/cctop/releases/download/media-assets/cctop-launch-720p.mp4
https://github.com/st0012/cctop/releases/download/media-assets/cctop-launch.mp4README/Site Links
- For an inline README animation, prefer the release-hosted AVIF preview and an
<img>tag. - Use
cctop-launch-preview.aviffrom the samemedia-assetsrelease as the MP4s unless the user explicitly wants a committed preview file. - For the full video, link to the release asset URL.
- Avoid
releases/latest/download/...for media assets unless every future product release will carry the same asset name. cctop's README and site already usereleases/latestfor app downloads, so media assets should stay separate.
Helper
scripts/publish-launch-assets.sh is the preferred launcher for cctop launch renders. It creates a fresh AVIF preview and delegates uploads to scripts/upload-video-asset.sh.
scripts/upload-video-asset.sh creates media-assets if needed with --latest=false, stages the file under the intended asset filename, then uploads it. It refuses v* tags unless passed --allow-v-tag.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

