CD record-browser-gif
Record browser or Web UI interaction demos as optimized GIFs using the available browser-control workflow, optional Playwright Videos for higher capture frame rates, and deterministic encoding, then attach the GIF to a pull request with `gh --attach`, falling back to a dedicated assets branch where attach cannot apply. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and model flow.
The skill promises to automate browser interaction GIF recording with Playwright optimization and deterministic encoding, then attach results to pull requests. The archive contains three files and two scripts, but encode_gif.py won't run—it requires mandatory input and output arguments that the skill doesn't provide. Code quality scores 72%, process execution 44%. No critical errors, but broken references indicate missing dependencies.
In practice, the skill can record GIFs via available browser control, but the encoding stage will fail. The fallback to assets branch works, but the main feature—PR attachment—won't complete. Install only if you're prepared to patch the scripts yourself or need just the recording part.
Record browser or Web UI interaction demos as optimized GIFs using the available browser-control workflow, optional Playwright Videos for higher capture frame…
As a process D 44/100 · Unfinished process — References files that are not bundled: ../../notes/archived/process/2026-08-08-browser-gif-evidence-chain.md, <path/to/demo.gif>
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../notes/archived/process/2026-08-08-browser-gif-evidence-chain.md - warning
missing-refreference to a missing file: <path/to/demo.gif>
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: ../../notes/archived/process/2026-08-08-browser-gif-evidence-chain.md, <path/to/demo.gif>
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 28 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4041 tokens
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 569: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
In the sandbox Скрипты не запустились
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 1 скрипт; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
Ни один не дошёл до работы — им не хватило зависимостей, аргументов или файлов. Это не отзыв о поведении: наблюдать было не за чем.
scripts/encode_gif.py | не запустился: encode_gif.py: error: the following arguments are required: input, output |
11 Oct 2026