SKILLEMALL.ai
GitHub ↗ RU Sign in

CF update-screenshots

Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR. Use when asked to update, accept, or refresh component screenshot baselines from CI. This skill should be run as a subagent.

The skillemall take

Claims to update screenshot hashes in blocks-ci when the check fails or investigate diffs on PRs. Runs as a subagent for accepting and refreshing component baselines.

Broken references in files point nowhere. Quality 72, process 31: documented but poorly structured. No critical issues, minor gaps remain. Never tested on models or sandbox.

Install if you already navigate VSCode screenshot workflows. Otherwise expect trial-and-error with paths and hash meanings. Works for routine baseline updates, though documentation needs tightening.

microsoft/vscode Agent Skills author: microsoft MIT 1 file body ≈ 1 184 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR.

As a process F 31/100 · No process to follow — References files that are not bundled: ../../../test/componentFixtures/blocks-ci-screenshots.md, ../../workflows/component-fixtures.yml, ../../../build/lib/screenshotBlocksCi.ts

ProcedureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
F
31/100
No process to follow
References files that are not bundled: ../../../test/componentFixtures/blocks-ci-screenshots.md, ../../workflows/component-fixtures.yml, ../../../build/lib/screenshotBlocksCi.ts
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../test/componentFixtures/blocks-ci-screenshots.md
  • warning missing-ref reference to a missing file: ../../workflows/component-fixtures.yml
  • warning missing-ref reference to a missing file: ../../../build/lib/screenshotBlocksCi.ts

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: ../../../test/componentFixtures/blocks-ci-screenshots.md, ../../workflows/component-fixtures.yml, ../../../build/lib/screenshotBlocksCi.ts
  • 0Tools and files. 3 referenced file(s) missing: ../../../test/componentFixtures/blocks-ci-screenshots.md, ../../workflows/component-fixtures.yml, ../../../build/lib/screenshotBlocksCi.ts
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 75Steps. 3 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1184 tokens
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 269: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (8 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.