codegen-diagram

基于当前项目/代码生成 Draw.io 图表，支持技术栈图、系统架构图、数据结构图、E-R 图四种类型。输出符合 Draw.io 语法的 .drawio 文件（mxGraph XML），可直接导入 Draw.io 编辑。当用户提到技术栈、系统架构、数据结构、E-R 图时使用。

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/codegen-diagram/SKILL.md

Quality

Content

57%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 clean, well-structured overview with specific style guidance, but it lacks any executable XML example and relies on four reference files that are missing from the bundle. Validation checkpoints for the generated .drawio output are also absent.

Suggestions

Provide the referenced bundle files (reference/tech-stack.md, system-arch.md, data-structure.md, er-diagram.md) or inline the per-type generation guidance so the skill is self-contained.

Add a minimal copy-paste mxGraph XML skeleton showing node and edge structure so the output is executable rather than attribute-only.

Insert a validation checkpoint—e.g., 'open the .drawio in Draw.io to confirm it renders, or validate the XML is well-formed before delivering'—into the output workflow.

Dimension	Reasoning	Score
Conciseness	The body is table-driven and lean with no padding about what Draw.io is, but the opening sentence restates the frontmatter description and the '使用时机' section repeats the trigger keywords, giving minor over-explanation that could be trimmed.	4 / 5
Actionability	It gives concrete attribute values (specific hex colors, Helvetica 11–13, endArrow=classicBlockThin/blockThin) but provides no executable mxGraph XML skeleton or node/edge template, and the per-type reference files that would carry the detailed how-to are absent, leaving key details missing.	3 / 5
Workflow Clarity	A sequence is present (Step 0 task identification → common specs → four-part output requirements), but there are no validation checkpoints—e.g., verifying the mxGraph XML is well-formed or that the diagram opens in Draw.io—so checkpoints are missing.	3 / 5
Progressive Disclosure	Structure is well-organized with a clear table mapping each task type to a one-level-deep reference file, but the four referenced files (reference/tech-stack.md, system-arch.md, data-structure.md, er-diagram.md) do not exist in the bundle, so the signaled navigation does not actually resolve.	3 / 5
	Total	13 / 20 Passed

Description

87%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 strong: it states a concrete capability, lists four specific diagram types and a precise output format, and gives an explicit 'use when' trigger clause. Minor gaps are limited to synonym/extension coverage and the action being singular across subtypes.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete specifics—generating Draw.io diagrams for four named types and outputting .drawio (mxGraph XML) files—but the core action is essentially singular (generate diagrams) across subtypes rather than multiple distinct actions, leaving a minor coverage gap.	4 / 5
Completeness	It explicitly answers both 'what' ('基于当前项目/代码生成 Draw.io 图表…输出… .drawio 文件') and 'when' ('当用户提到…时使用') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The clause '当用户提到技术栈、系统架构、数据结构、E-R 图时使用' supplies four natural trigger phrases a user would actually say, but it omits common synonyms and file-extension variants (.drawio appears only as output, not as a trigger).	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche—project/code-based Draw.io diagrams in four specific types with explicit triggers and a distinctive output format—minimizing overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: xstongxue/best-skills
Path: skills/codegen-diagram/SKILL.md
Commit: 88a38bb

Reviewed: ~1 hour ago

Table of Contents

Discovery Implementation Validation

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.