agentleFS
st0012st0012/cctop/.agents/skills/video-assets/SKILL.md

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.

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
  1. Very specific:

    Default release tag: media-assets.

    line 12
  2. Very specific:

    Default release title: Media assets.

    line 13
  3. Very specific:

    Always create media-only releases with --latest=false.

    line 14
  4. Very specific:

    Do not use a v* tag for media-only work.

    line 15
  5. Very specific:

    Keep full MP4s and other large rendered video out of git.

    line 17
  6. Distinctive:

    Commit a small animated README preview only when the user explicitly chooses that route and the file is intentionally small.

    line 18
  7. Very specific:

    Prefer stable purpose-based asset names over dates: cctop-launch.mp4, cctop-launch-720p.mp4, cctop-launch-preview.avif.

    line 19
  8. Very specific:

    Check existence and size with ls -lh.

    line 26
  9. Very specific:

    Check duration/codec with ffprobe when available.

    line 27
  10. Very specific:

    Use media-assets for reusable README/demo/launch assets.

    line 30
  11. Very specific:

    Use an existing app release such as v0.18.4 only with explicit user direction.

    line 31
  12. Distinctive:

    Use a new asset name when history matters or two variants should coexist.

    line 36
  13. Distinctive:

    Default launch asset set:

    line 38
  14. Very specific:

    Before creating a release, uploading, or replacing assets, state: release tag, source file, asset name, whether --clobber will be used, and …

    line 44
  15. Distinctive:

    Wait for explicit approval unless the user's latest request already clearly authorizes the upload/update.

    line 45
  16. Distinctive:

    Never publish a media release as latest.

    line 46
  17. Very specific:

    Use --dry-run first when checking paths or explaining what will happen:

    line 54
  18. Very specific:

    Use cctop-launch-preview.avif from the same media-assets release as the MP4s unless the user explicitly wants a committed preview file.

    line 100
  19. Very specific:

    Avoid releases/latest/download/...

    line 102

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Identify the source files.
    • Launch defaults: video/projects/launch/.video-build/launch.mp4 and video/projects/launch/.video-build/launch-720p.mp4.
    • Check existence and size with ls -lh.
    • Check duration/codec with ffprobe when available.
  2. Pick the release target.
    • Use media-assets for reusable README/demo/launch assets.
    • Use an existing app release such as v0.18.4 only with explicit user direction.
    • Inspect before mutating: gh release view media-assets --repo st0012/cctop.
  3. Pick stable asset names.
    • Reusing the same asset name plus --clobber keeps the download URL stable.
    • Use a new asset name when history matters or two variants should coexist.
    • Remember: gh release upload file.mp4#Label sets 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.mp4 from launch.mp4
      • cctop-launch-720p.mp4 from launch-720p.mp4
      • cctop-launch-preview.avif generated from launch-720p.mp4
  4. Gate public mutations.
    • Before creating a release, uploading, or replacing assets, state: release tag, source file, asset name, whether --clobber will 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.
  5. Publish launch assets with the wrapper script. This is the default path for launch renders.
.agents/skills/video-assets/scripts/publish-launch-assets.sh --clobber

Use --dry-run first when checking paths or explaining what will happen:

.agents/skills/video-assets/scripts/publish-launch-assets.sh --clobber --dry-run

The 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.
  1. 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 \
  --clobber

For another video:

.agents/skills/video-assets/scripts/upload-video-asset.sh \
  --file path/to/other-video.mp4 \
  --name cctop-other-video.mp4

The 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.mp4

README/Site Links

  • For an inline README animation, prefer the release-hosted AVIF preview and an <img> tag.
  • Use cctop-launch-preview.avif from the same media-assets release 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 use releases/latest for 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.