AB research-visualizer
Generate interactive HTML research reports from AI research context. After completing a multi-step research task (web search, API calls, analysis), use this skill to create a visual report showing the research process, data visualizations, and conclusions. The report is uploaded to a2ui.me and returned as a clickable link card. Use when: research complete, analysis done, investigation finished, deep research, multi-step research, show my work, explain research process, visualize research.
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Obfuscation
obf-base64-blobdemo/test-encrypted.html:37Long base64-looking blob (test fixture / example file; quoted — discussed, not commanded)var ct=Uint…rom(atob('qLjT…XaF+AkD9…XMs+vMn9…gFefixturequoted -
low Secrets in code
secret-high-entropy-tokendemo/test-encrypted.html:37High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)var ct=Uint…rom(atob('qLjT…XaF+AkD9…XMs+vMn9…gFefixturequoted
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 67/100
- 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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1549 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
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 493: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.