CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visual-explainer

Create self-contained HTML visual explainers from technical material. Use this skill when diagrams, matrices, timelines, or browser artifacts beat plain text.

Quality

59%

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/content-publishing/visual-explainer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 a policy-style document: well-sectioned and safety-conscious, but with duplicated sections, no executable guidance (no code, commands, or templates), and a reference layer that neither resolves its own cited paths nor surfaces the real bundle files. It reads as a routing/contract summary rather than an actionable skill.

Suggestions

Merge the verbatim-duplicated 'Avoid' and 'Anti-Patterns' sections and consolidate the five restatements of the secrets/redaction policy into one, freeing tokens for real guidance.

Add executable specifics: a minimal self-contained HTML artifact skeleton or template reference, and the concrete commands behind 'Plugin Eval', 'strict skill audit', and local rendering/verification checks.

Fix the reference layer: replace the non-existent 'Infrastructure/references/...' paths with the actual bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) or move that detail into real files, and define or link the 'context-disposition policy'.

DimensionReasoningScore

Conciseness

The "Avoid" and "Anti-Patterns" sections are verbatim duplicates of the same three bullets, and the secrets/redaction policy is restated across five sections ("Do not render secrets...", "Redact secrets and sensitive data by default", "If the source contains sensitive text, redact or summarize", etc.). This is noticeably padded rather than the minor trimming of anchor 4.

2 / 5

Actionability

No code, commands, templates, or example HTML structure appear anywhere; steps like "Render responsive HTML" and "Run Plugin Eval and strict skill audit" are high-level hints without executable specifics. A few concrete directives (redact labels, include schema_version, report output path) keep it above the entirely-vague anchor 1.

2 / 5

Workflow Clarity

The 6-step workflow has a real sequence and explicit fail-fast language ("stop at the first failed gate, fix it, and rerun") plus a Failure Mode section with revise-and-rerun loops. However, checkpoints are abstract — no validation step can be executed as written — so it does not meet anchor 4's 'concrete code or commands' bar.

3 / 5

Progressive Disclosure

The body's only reference paths ("Infrastructure/references/openai-cookbook-expert-lens-pack.md", "Infrastructure/references/deferred-skill-context/content-publishing-visual-explainer/") do not exist in the bundle, while the actual bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) are never cited. Navigation is broken in both directions, and an undefined "context-disposition policy" is invoked without a pointer.

2 / 5

Total

9

/

20

Passed

Description

70%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 is well-constructed: it uses third person, states a concrete capability, and includes an explicit 'Use when' clause. Its main weaknesses are a single-action capability statement and a comparative rather than utterance-based trigger clause.

DimensionReasoningScore

Specificity

"Create self-contained HTML visual explainers from technical material" names the domain and a single concrete action, but offers no broader action list. It is more concrete than anchor 2 ('Processes PDF files' generic action) yet lacks the several specific actions needed for a 4.

3 / 5

Completeness

Both 'what' ("Create self-contained HTML visual explainers from technical material") and an explicit 'when' ("Use this skill when diagrams, matrices, timelines, or browser artifacts beat plain text") are present. The when-clause is comparative rather than concrete user trigger phrases, so it does not reach anchor 5's 'concrete trigger phrases' bar.

4 / 5

Trigger Term Quality

Trigger terms include "diagrams", "matrices", "timelines", "browser artifacts", "HTML", and "visual explainers" — good natural keyword coverage. Common variations like "chart", "visualization", or "slides" are missing, so it falls just short of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"self-contained HTML visual explainers" carves a clear niche with mostly distinct triggers. Minor overlap risk remains with general charting/dataviz skills via shared terms like "diagrams" and "timelines", keeping it below anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/content-publishing/visual-explainer/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.