CtrlK
BlogDocsLog inGet started
Tessl Logo

baoyu-infographic

Infographics: 21 layouts x 21 styles (信息图, 可视化).

52

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/creative/baoyu-infographic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, table-driven overview that delegates all deep material to real, one-level-deep reference files and gives a fully concrete seven-step workflow with exact filenames, tool calls, and mapping rules. Its only weaknesses are minor: some duplicated reference pointers and no post-generation verification checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanation of concepts Claude already knows — layout and style galleries use one-line entries, and the workflow uses terse imperative steps. Minor trimming is possible: the "Full definitions: references/..." pointers appear twice (once after each gallery, again in the References section), and the References section largely restates paths already given inline. This matches anchor 4 rather than 5 because of that duplication; it is well above anchor 3 since there is no padded explanation.

4 / 5

Actionability

The guidance is concrete throughout: exact filenames (source.md, analysis.md, structured-content.md, prompts/infographic.md), specific tools (write_file, clarify, image_generate), explicit mappings (landscape→16:9, 16:9→landscape), backup naming with timestamp patterns, and slug rules. It falls short of anchor 5 only because the actual prompt-assembly mechanics (how layout/style definitions are merged into base-prompt.md) are delegated to reference files rather than shown — acceptable, but leaves a minor gap versus copy-paste-ready completeness.

4 / 5

Workflow Clarity

Seven clearly sequenced steps each state their inputs and outputs, with decision points (keyword shortcut check, language question conditional on source≠user language) and an explicit failure recovery (auto-retry once on image generation failure). It matches anchor 4 rather than 5 because there are no verification checkpoints after generation — e.g., no step to check the output image or prompt file before reporting success.

4 / 5

Progressive Disclosure

The body is an overview with well-signaled one-level-deep references, all of which exist in the bundle: 21 verified files in references/layouts/, 21 in references/styles/, plus analysis-framework.md, structured-content-template.md, and base-prompt.md. Detailed material is properly split out, each reference is named with its purpose, and navigation (galleries → per-layout/style files → step-specific references) is easy.

5 / 5

Total

17

/

20

Passed

Description

40%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 communicates a distinctive niche (infographics with a layout×style matrix) and includes natural Chinese trigger terms, but it omits any action verb describing what the skill does and has no 'use when' trigger guidance. It reads more like a catalog subtitle than a capability statement, leaving both 'what' and 'when' underspecified.

Suggestions

Add explicit trigger guidance, e.g. append "Use when the user asks to create an infographic, visual summary, or 信息图/可视化大图." — this alone lifts the completeness cap.

State the concrete action up front, e.g. "Generates infographic images from user-provided content..." instead of the noun-phrase catalog form "Infographics: 21 layouts x 21 styles".

Broaden English trigger coverage with synonyms such as "visual summary", "information graphic", and "high-density info image" to complement the existing Chinese terms.

DimensionReasoningScore

Specificity

The description "Infographics: 21 layouts x 21 styles" names the domain and quantifies its two dimensions, but contains no concrete action verbs — it never says whether the skill creates, generates, or analyzes infographics. This matches 'names the domain but actions are minimal or generic' rather than score 3, which requires 1-2 concrete actions; it is above score 1 because the layout/style counts are concrete rather than pure abstraction.

2 / 5

Completeness

The description has a vague 'what' — "Infographics: 21 layouts x 21 styles" describes the option space but not what the skill does with it — and there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 by the rubric guidelines. Score 2 fits: vague 'what' and no 'when'; it does not reach score 3 because the 'what' never states an action to be considered clear.

2 / 5

Trigger Term Quality

Trigger terms are "Infographics", "信息图", and "可视化" — the natural Chinese phrases a user would say, plus the core English noun. However, common variations are missing: no English synonyms like "visual summary", "information graphic", or "infographic image". This sits between anchor 3 (some relevant keywords, missing variations) and anchor 4 (good coverage, a few missing), closer to 3 because English trigger coverage is thin.

3 / 5

Distinctiveness Conflict Risk

"Infographics" is a clear niche with distinct triggers, but "可视化" (visualization) is a broad term that overlaps with general dataviz/charting skills, creating minor conflict risk with closely related skills. This matches anchor 4 rather than 5, and is well above anchor 3 since the layout×style framing is unmistakably this skill's.

4 / 5

Total

11

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.