CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visualizations-config

Configure visualization location, style presets, and output preferences

Quality

69%

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/visualizations-config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, executable configuration workflow with concrete commands, a complete config schema example, and a clear step sequence. Its main weaknesses are the absence of any validation/verification step and the lack of a README template or definition of custom style input.

Suggestions

Add a validation step after Step 3, e.g. 'Verify the JSON parses: python -c "import json; json.load(open('.devflow/visualizations.json'))"' and confirm the config takes effect before scaffolding folders.

Provide a concrete README.md template (or reference file) for Step 5 instead of just a bullet list of contents.

Specify what 'custom' style requires (e.g. the classDef color keys the user must provide) so the interactive path is fully actionable.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — flags, options, and commands are given without padding — but minor spots could be trimmed, e.g. the 'Format is independent of style' explanation in 2d repeats what the option bullets already convey.

4 / 5

Actionability

Provides copy-paste-ready guidance: a complete JSON config example, concrete 'mkdir -p <path>/{<categories>}' and 'touch <path>/<category>/.gitkeep' commands, and an explicit flag list. Minor gaps: the README section lists contents but gives no template, and 'custom' style/color input is undefined.

4 / 5

Workflow Clarity

Steps 1-7 form a clear sequence covering config detection, argument parsing, interactive fallback, writing config, and scaffolding folders/README. However, there is no validation checkpoint (e.g. verifying the JSON parses or the folders were created), which keeps it below 5; the operations are low-risk so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

A well-organized single-file skill with clean section structure and no bundle files; no nested or buried references. The ~25-line inline config example and preset definitions could live in a separate reference file, which is the minor gap keeping it from 5.

4 / 5

Total

16

/

20

Passed

Description

50%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 clearly states what the skill configures but stops there: it has no 'when to use' trigger guidance, no natural synonyms (diagrams, charts, mermaid), and only one action verb. It is serviceable but sits at the midpoint on every dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up or changing where project diagrams are stored, which diagram style to use, or the output format.'

Include natural trigger terms users would actually say: 'diagrams', 'charts', 'mermaid', 'excalidraw', 'visualization folder', 'style preset'.

Enumerate the concrete actions more fully: 'Set the visualization directory, choose a style preset and diagram format (mermaid/excalidraw), and create category folders.'

DimensionReasoningScore

Specificity

Names the domain and concrete config targets ('visualization location, style presets, and output preferences') but relies on a single generic action verb ('Configure') and 'output preferences' is vague, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (configure location, style presets, output preferences), but there is no 'Use when...' clause or any trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'visualization' and 'style presets', but misses natural terms users would say such as 'diagrams', 'charts', 'mermaid', or 'excalidraw'.

3 / 5

Distinctiveness Conflict Risk

The visualization-config niche is somewhat specific, but 'visualization' broadly overlaps with general diagramming/charting skills and the description lacks distinct trigger phrases.

3 / 5

Total

12

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

AndreJorgeLopes/devflow

Path

skills/visualizations-config/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.