CD visualize
Create visualizations and interactive tools directly in conversation. Proactively use to show how something works; explore 'what happens when', 'what changes', or 'help me understand'; compare or inspect; create simulations, maps, charts, graphs, and mockups. Use standard tools for static scientific figures.
The skill promises to render visualizations, interactive graphs, and simulations directly in chat during conversations. The files contain instructions to use them proactively for explanations, comparisons, and hypothesis testing. Quality score sits at 73 out of 100, but the process score dropped to 44—a red flag for execution issues.
Tests found broken references and no model runs. Sandbox testing didn't happen. It supports many platforms, but that doesn't confirm the skill actually works. Install if you need a reminder that AI should draw charts—just expect results to depend on your model and its configuration.
Create visualizations and interactive tools directly in conversation.
As a process D 44/100 · Unfinished process — References files that are not bundled: examples/calendar.html
The same skill appears in 1 more place: system_prompts_leaks
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 · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8651 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: examples/calendar.html
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: examples/calendar.html
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 14 mutating operations with no state check
- 40Execution cost. Instruction body is 8651 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 157 steps
- 100When it triggers. States when to use and when not to
- 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 (13 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 309: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 157 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.