CD designer
Read editor.md, editor.json, and analyst.json. Make data-driven creative visual decisions for every section — teaser, charts, images, videos, audio, maps, and interactive demos when they fit the data. Generate selected assets. No HTML. Outputs designer.json with des_xx IDs.
Read editor.md, editor.json, and analyst.json. Make data-driven creative visual decisions for every section — teaser, charts, images, videos, audio, maps, and…
As a process D 46/100 · Unfinished process — References files that are not bundled: ../../frontend-design-pro/, ../../dataviz-craft/references/chart_chooser.json, ../../dataviz-craft/references/encoding_craft.json
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(*)allowed-tools: Bash(*) Read Write Glob
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9193 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../frontend-design-pro/ - warning
missing-refreference to a missing file: ../../dataviz-craft/references/chart_chooser.json - warning
missing-refreference to a missing file: ../../dataviz-craft/references/encoding_craft.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/media_presentation.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/abstract_excellence.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/themes.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/typography.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/finish.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/motion.json - warning
missing-refreference to a missing file: ../../frontend-design-pro/references/quality_rubric.json - warning
missing-refreference to a missing file: assets/teaser.webm
Process rating: all ten parameters 46/100
- 0Tools and files. 11 referenced file(s) missing: ../../frontend-design-pro/, ../../dataviz-craft/references/chart_chooser.json, ../../dataviz-craft/references/encoding_craft.json
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 40Execution cost. Instruction body is 9193 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 27 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 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
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +3Description length 274: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.