CtrlK
BlogDocsLog inGet started
Tessl Logo

baoyu-comic

Knowledge comics (知识漫画): educational, biography, tutorial.

52

Quality

60%

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

Quality

Content

81%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 strong operational document: fully actionable commands, a well-sequenced workflow with genuine validation and error-recovery gates, and a clean one-level reference bundle. Its weaknesses are redundancy (the image_generate constraint and character-sheet caveat each repeated several times, plus a narrative incident anecdote) and a small amount of detail-section content inlined into the overview.

Suggestions

State the prompt-only constraint of image_generate and the character-sheet-as-artifact caveat once (in the Reference Images section) and reference it from Step 7 and Pitfalls instead of restating each three to four times.

Move the timeout-handling narrative and the 'Incident Apr 2026' CWD anecdote into references/workflow.md, keeping only the absolute-path rule and the one-line default-surfacing requirement in SKILL.md.

Link or remove the orphaned references/base-prompt.md so every bundle file is reachable from the overview's navigation.

DimensionReasoningScore

Conciseness

Mostly efficient — dense option tables, a step summary, and a checklist — but with real redundancy: the prompt-only nature of image_generate is explained four separate times (Reference Images, Step 7, 7.1, and Pitfalls), the character-sheet clarification is repeated three times, and the 'Incident Apr 2026' anecdote plus the CWD paragraph restate the same absolute-path rule twice. Not a 4 because these repetitions and the narrative incident story are clearly trimmable.

3 / 5

Actionability

Concrete, copy-paste-ready guidance throughout: the exact curl command with absolute path (`curl -fsSL "<url>" -o /abs/path/...png`), explicit aspect-ratio mapping table, exact file-naming patterns (`NN-{cover|page}-[slug].md`), a backup-rename suffix format, and per-page verification steps. Not a 4 because the common cases are covered with specific executable commands rather than hints.

5 / 5

Workflow Clarity

The 8-step workflow has an explicit progress checklist, conditional review gates (Steps 4/6), a required confirmation gate (Step 2) with per-question timeout handling, per-image validation ('verify the file exists and is non-empty at that exact path before proceeding'), auto-retry, and a backup-before-regenerate rule — a full feedback loop for a batch image-generation operation. Not a 4 because validation checkpoints are explicit at every risky stage.

5 / 5

Progressive Disclosure

Good structure: detailed art/tone/preset/layout definitions are split into per-file references one level deep, clearly signaled and loaded on demand ('Full definitions at references/art-styles/<style>.md', 'load the file when a preset is picked'), and all referenced paths exist. Not a 5 because references/base-prompt.md exists in the bundle but is never linked from SKILL.md (orphaned navigation), and the lengthy timeout-handling and CWD-incident prose belongs in references/workflow.md rather than the overview.

4 / 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 identifies a distinct niche with useful bilingual keywords but fails to state any concrete capability or any usage trigger. It reads as a genre label rather than a skill description; the rich trigger terms that exist in the body's 'When to Use' section were never surfaced into the frontmatter.

Suggestions

State at least one concrete action, e.g. "Creates original knowledge/educational comics (storyboard, prompts, and generated images) from user-provided content or a topic."

Add an explicit 'when' clause mirroring the body's trigger list: "Use when the user asks for a knowledge/educational comic, biography comic, tutorial comic, or uses terms like 知识漫画, 教育漫画, or Logicomix-style."

Include natural synonyms users would actually say (comic strip, how-to comic, explain X as a comic) so the skill triggers on phrasing beyond the two Chinese terms.

DimensionReasoningScore

Specificity

The description names the domain ("Knowledge comics (知识漫画)") but lists only content categories ("educational, biography, tutorial") — no concrete actions or verbs at all, matching the 'names the domain but actions are minimal or generic' anchor. It is not a 3 because there is no named action (nothing like 'create', 'generate', or 'adapt'), and not a 1 because the domain itself is concrete rather than pure abstraction.

2 / 5

Completeness

There is only a vague 'what' (a genre list with no stated capability) and no 'when' clause whatsoever — no 'Use when...' or equivalent trigger guidance, which per the judging guidelines caps this dimension at 3 and pushes it to the 'vague what and no when' anchor. Not a 3 because even the 'what' never states what the skill actually does (create/generate comics).

2 / 5

Trigger Term Quality

It includes some genuinely natural keywords — "Knowledge comics", "教育/educational", "biography", "tutorial", plus the Chinese "知识漫画" — but misses common variations users would say, such as "comic strip", "how-to comic", "Logicomix-style", or "make a comic about X". Not a 4 because several natural trigger phrases (which the body's own 'When to Use' section lists) are absent from the description.

3 / 5

Distinctiveness Conflict Risk

"Knowledge comics (知识漫画)" is a fairly clear niche with bilingual triggers, unlikely to fire for unrelated skills; only minor overlap risk with generic image-generation or drawing skills. Not a 5 because without a 'when' clause, a request like "make an educational comic" relying on generic comic wording could collide with a plain comic/drawing skill.

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.