CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baoyu-diagram

Create professional diagrams with configurable dark/light theme via CSS custom properties. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system, process flow, data flow, component relationship, network topology, decision tree, org chart, state machine, or any visual representation of structure/logic/process. Also trigger when the user says "画个图" "画一个架构图" "diagram" "flowchart" "sequence diagram" "draw me a ..." or uploads content and asks to visualize it. Outputs a dark-theme SVG, a light-theme SVG, and a @2x PNG of each.

Quality

85%

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

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.

A well-engineered, highly actionable skill body: concrete templates, exact commands, a layered drawing model, and a clean reference split for diagram-type specifics. Its main defects are the missing built-in themes/ directory that breaks the documented theme-switch/PNG pipeline as shipped, and heavyweight inline design-system material that inflates the token cost of every invocation.

Suggestions

Ship the promised themes/dark.json and themes/light.json (or state that the :root block and the CSS Custom Properties table are the source of truth and generate theme files on demand) — as delivered, `theme-switch.ts <name>.svg --theme=light` fails with 'Theme not found'.

Move the Component Patterns and marker SVG templates into a reference file (e.g. references/patterns.md) and keep only the layering order, spacing rules, and one exemplar box in SKILL.md, cutting ~100 lines from the always-loaded body.

Add a post-generation validation step to the Process (e.g. re-read the generated SVGs to confirm no var() is unresolvable and both PNGs were written), mirroring the existing spacing-verification checkpoint.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific, load-bearing content (layering order, spacing rules, the 24-row theme variable table, exact script commands) and contains no explanations of concepts Claude already knows. It sits at 4 rather than 5 because the custom-theme JSON example partly duplicates the variable table and ~80 lines of inline SVG component templates add token weight that could be trimmed or moved out.

4 / 5

Actionability

Guidance is concrete and copy-paste ready: exact script invocations with flags and defaults, complete SVG snippets, save-path rules, BUN_X resolution, and an error path for missing sharp. The gap keeping it from 5: the documented pipeline depends on built-in themes ("Theme values live in {baseDir}/themes/<name>.json ... Built-in: dark.json, light.json") but no themes/ directory ships in the bundle, so `theme-switch.ts --theme=light` and `main.ts --theme light` fail as delivered.

4 / 5

Workflow Clarity

The 9-step Process is clearly sequenced with an explicit pre-save verification checkpoint ("Verify spacing rules — no overlaps, legends outside boundaries, viewBox large enough") and dependency error-recovery guidance. It does not reach 5 because there is no post-generation validation of the produced light SVG or PNG outputs, though the operation is not destructive or batch so the level-3 cap does not apply.

4 / 5

Progressive Disclosure

Bundle structure is good: the four diagram-type references (architecture.md, flowchart.md, sequence.md, structural.md) all exist, are one level deep, and are clearly signaled in the Diagram Types table with an instruction to read them before layout; all referenced scripts exist. It is not 5 because the promised built-in themes/dark.json and light.json are missing from the bundle (a broken reference), and the ~150-line design-system reference (variable table plus component patterns) is inlined in SKILL.md rather than split out.

4 / 5

Total

16

/

20

Passed

Description

91%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.

A strong description: it explicitly covers what the skill does, when to use it, and what files it produces, with unusually thorough natural trigger terms in both English and Chinese. The only real risks are minor overlap with charting/visualization skills and a capability list that is one action deep despite the long type enumeration.

DimensionReasoningScore

Specificity

States concrete capabilities — "Create professional diagrams with configurable dark/light theme via CSS custom properties" and "Outputs a dark-theme SVG, a light-theme SVG, and a @2x PNG of each" — with a broad enumeration of diagram types. It stays at 4 rather than 5 because the capability list is essentially one create action plus output formats, not multiple distinct concrete operations, and it is well above the 1-2-actions level of a 3.

4 / 5

Completeness

Explicitly answers both questions: what ("Create professional diagrams ... Outputs a dark-theme SVG, a light-theme SVG, and a @2x PNG of each") and when ("Use this skill whenever the user asks for any kind of technical or conceptual diagram ... Also trigger when the user says ..."), with concrete trigger phrases. This is the anchor-5 pattern, clearly above anchor 4 where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: "diagram", "flowchart", "sequence diagram", "draw me a ...", "画个图", "画一个架构图", "uploads content and asks to visualize it", plus type keywords (process flow, data flow, org chart, state machine, network topology, decision tree). Matches the comprehensive-with-synonyms anchor; only trivial terms like "chart" are absent, so it does not fall to 4.

5 / 5

Distinctiveness Conflict Risk

The diagram/SVG generation niche is well-defined with distinct triggers, but broad phrases like "visualization of a system" and "asks to visualize it" could also match charting/dataviz skills. Mostly distinct with minor overlap risk fits anchor 4; it is not the minimal-conflict clarity of anchor 5.

4 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

JimLiu/baoyu-skills

Path

skills/baoyu-diagram/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.