CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visualize

Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/visualize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an unusually dense, high-signal decision guide: concrete limits, API names, and verification loops with essentially zero filler. Its main weaknesses are structural — no progressive disclosure despite reference-grade inline material — and the absence of one complete worked widget_code example.

Suggestions

Move reference-grade inventories (allowed HTTPS origins list, the openclaw.data/action/cron/state API reference, and the full CSS custom-property list) into a references/ file, keeping SKILL.md as an overview with clearly signaled one-level-deep links.

Add one minimal complete widget_code example (a small HTML/SVG fragment with a scoped root ID and a textContent-based label) so the most common single case is copy-paste ready.

Tighten the verify section by consolidating its distributed checkpoints into a short ordered checklist (fix syntax errors → re-call → verify assets/controls/width → follow result.presentation).

DimensionReasoningScore

Conciseness

Nearly every sentence carries non-obvious platform facts Claude cannot know (262,144-char widget limit, allowed CDN origin list, host CSS tokens, 4,000-char prompt cap) with no explanation of general concepts. It falls short of 5 because a handful of sentences over-qualify or restate and could be trimmed (e.g., the browser-profile sign-in nuance and repeated surface-availability caveats).

4 / 5

Actionability

Concrete, executable guidance throughout: exact API signatures ("openclaw.data.read(bindingId, params?)"), hard limits, a copy-paste D3 script tag, named CSS classes and custom properties, and precise capability declarations. Not 5 because there is no complete minimal widget_code example tying the pieces together, leaving a small gap for the most common case.

4 / 5

Workflow Clarity

A clear sequenced flow (choose surface → author content → libraries/theme → dashboard actions → verify and deliver) with explicit validation and feedback steps ("Fix reported inline-script syntax errors and call the tool again", "Check capabilityState and report pending or rejected access", "exercise the data read in the actual pinned frame"). Not 5 because checkpoints are distributed across prose rather than consolidated into an explicit ordered checklist or recovery loop.

4 / 5

Progressive Disclosure

Sections are well organized, but at ~158 lines everything lives inline in SKILL.md with no reference files at all — reference-grade material such as the full CDN origin list, the host API reference, and the complete theme token inventory is inlined rather than split out. This matches anchor 3 (content that should be separate is inline); not 4 because there is no disclosure structure beyond the single file.

3 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a clear, concrete "what" with a distinctive named tool, but completely lacks any "when to use" trigger guidance and misses the natural synonyms (chart, diagram, graph, plot) users would most likely say. It is serviceable but sits below the good-example bar, which pairs capabilities with an explicit Use-when clause.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for a diagram, chart, visual, dashboard, or mockup of code, data, or results, or when a visual would make an explanation clearer than prose."

Include natural trigger synonyms — chart, graph, diagram, plot, visualization, mockup, dashboard — alongside "inline visuals" so the description matches how users actually phrase these requests.

Enumerate one or two more concrete capabilities (e.g., render architecture/flow diagrams, build metrics/status widgets) to lift specificity from two named actions to a fuller coverage list.

DimensionReasoningScore

Specificity

Names two concrete actions ("Create inline visuals for code and explanations", "author persistent OpenClaw dashboard widgets with show_widget") but does not comprehensively cover capabilities such as charts, diagrams, traces, or simulations. It stays at anchor 3 rather than 4 because the coverage of specific actions is minimal — two verb phrases with no enumeration of what the visuals or widgets encompass.

3 / 5

Completeness

The "what" is clear (create inline visuals; author persistent dashboard widgets with show_widget) but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" half is concrete rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords like "inline visuals", "dashboard widgets", and "show_widget" appear, but common natural variations users would say — "chart", "graph", "diagram", "plot", "visualize" — are missing. This matches anchor 3 (some relevant keywords, missing synonyms); not 4 because several of the most natural trigger terms are absent.

3 / 5

Distinctiveness Conflict Risk

The named tool ("OpenClaw dashboard widgets with show_widget") carves out a distinct niche with minor overlap risk. Not 5 because the broader half — "Create inline visuals for code and explanations" — could overlap with general visualization skills since no sharper triggers distinguish it.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openclaw/openclaw

Path

skills/visualize/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.