Capture short Alitu Help Center GIFs or screenshots from product flows using Playwright and ffmpeg. Use when a KB article needs UI visuals, especially when a short state change should be shown with a synthetic cursor and click pulse instead of static screenshots.
Use this when the user wants a reusable Help Center asset workflow, or when a KB article needs a GIF or screenshot sequence taken from the Alitu product.
This skill is for asset capture, not for writing the article copy itself.
Start here:
Default to the smallest useful asset.
static screenshots when the flow is mostly navigation or one stable UI state.GIF only when motion or a visible state change helps the reader.Before capturing anything, confirm:
/tmp./private/tmp/<slug>-assetsChoose the capture surface in this order:
Do not force a GIF if the environment is unstable.
Click to uploadChoose a file from your computer0.8 to 1.2 secondsFor KB GIFs:
960px3 to 5 fpsFor screenshots:
Default outputs:
/private/tmp/<slug>-frames/private/tmp/<slug>-assetsAll finished assets (GIFs, screenshots) for an article go into the article's assets directory at /private/tmp/<slug>-assets/. This directory is the staging area for S3 upload.
If the user wants another location, use that instead.
New images and videos cannot be uploaded to Intercom via API. Instead, upload them to the alitu-knowledge-base-assets S3 bucket.
Use the bundled upload script:
scripts/upload_assets.sh /private/tmp/<slug>-assets <article-slug>
This uploads all files in the assets directory to s3://alitu-knowledge-base-assets/articles/<article-slug>/ and prints the public URLs. Use these URLs in the article HTML.
Public URL pattern: