AD cc-design
High-fidelity HTML design and prototype skill for landing pages, slide decks, mobile mockups, interactive prototypes, dashboard explorations, design-direction advising, and design review work. Use when Codex needs to design a screen, make an interface look polished, explore multiple visual directions, recommend a style direction before building, adapt an existing brand style, critique a design, or deliver a reviewable HTML-based visual artifact. Also use when the user mentions presentations, design systems, wireframes, UI mockups, motion studies, design philosophy, style selection, or asks to 'make it look good'. Do not trigger for pure content strategy, pure writing, or bitmap image generation alone.
As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/react-babel-setup.md:12High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)<script src="https://unpkg.com/re…@….3.1/umd/react-dom.development.js" integrity="sha3…L9t+IBXm…uAm" crossorigin="anonymous"></script>
quoted
Files scanned: 39. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 47/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
- 40Consistency. Frontmatter name (cc-design) differs from the folder (cell-cc-design)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 139 steps
- 100Execution cost. Instruction body is 1971 tokens
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +3Description length 710: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 139 items
- +4Reference files are cited in the instructions (17 of 17)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.