CD open-design-homepage
A pixel-faithful, self-contained mirror of the live open-design.ai homepage — an interactive React Three Fiber / Next.js hero with a real-time 3D wordmark, sticker collage, variable fonts, and scroll-driven motion. First-party showcase of the visual ceiling for interactive web marketing surfaces.
A pixel-faithful, self-contained mirror of the live open-design.ai homepage — an interactive React Three Fiber / Next.js hero with a real-time 3D wordmark…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "title"
Process rating: all ten parameters 43/100
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 576 tokens
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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 297: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
In the sandbox The scripts kept to themselves
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.
Запущено 10 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
assets/_next/static/chunks/1552c7742c37f06d.js | ничего за пределами своей папки |
assets/_next/static/chunks/56b0d8f9f2c1e441.js | ничего за пределами своей папки |
assets/_next/static/chunks/7cc1924554447827.js | ничего за пределами своей папки |
assets/_next/static/chunks/83f95f6c165018c5.js | ничего за пределами своей папки |
assets/_next/static/chunks/8c2d1abc8462562b.js | ничего за пределами своей папки |
assets/_next/static/chunks/8f06fe72571f37b9.js | ничего за пределами своей папки |
assets/_next/static/chunks/a6dad97d9634a72d.js | ничего за пределами своей папки |
assets/_next/static/chunks/d59f7a97fb1c563f.js | ничего за пределами своей папки |
assets/_next/static/chunks/e553ef8ae208a000.js | ничего за пределами своей папки |
assets/_next/static/chunks/turbopack-425288158aa66df2.js | ничего за пределами своей папки |
16 Oct 2026