CtrlK
BlogDocsLog inGet started
Tessl Logo

4drawio

数学建模非数据型图示绘制阶段。根据 ANALYSIS_MODELING_REPORT.md、RESULTS_REPORT.md 和已有 figures/ 生成技术路线图、子问题求解流程图、模型结构图、数据处理流程图等 DrawIO 图,并导出论文可引用 PDF。

73

Quality

91%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is tight, actionable, and well-sequenced with concrete executable bash, a validation feedback loop, and clean sectioning. It is a strong, copy-paste-ready workflow with no real conciseness or actionability weaknesses.

DimensionReasoningScore

Conciseness

The body is lean and instruction-oriented — stage boundaries, required outputs, a 6-step workflow, a figure-type table, a self-check checklist, and a report template — with no filler explaining concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready bash (heredoc XML generation, a DrawIO export command with command-v fallback), a checklist template, a figure-selection table, a report markdown template, and concrete self-check criteria; the XML skeleton is an explicitly justified structural template rather than vague pseudocode.

3 / 3

Workflow Clarity

Six clearly sequenced steps with an explicit self-check/validation checkpoint in Step 5 and a fix-and-re-export feedback loop ('发现问题要修 .drawio 并重新导出'), plus an export-failure fallback in Step 4 — matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and one clearly-signaled one-level-deep external reference (../_references/math_modeling_norms.md); no bundle directories exist, so per the simple-skills note well-organized sections justify a 3.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 specific and distinct, naming concrete diagram types and input artifacts, but lacks an explicit 'Use when...' trigger clause so completeness is capped at 2. Adding an explicit usage trigger would lift it to a full 3 across the board.

Suggestions

Add an explicit trigger clause such as 'Use when the math-modeling pipeline needs non-data figures (roadmaps, flow diagrams, model-structure diagrams) for the paper, after 3coding-visual produces data charts.'

Surface a few more natural user phrasings (e.g. '技术路线图', '流程图', 'DrawIO 导出 PDF') as explicit triggers to reinforce when this skill applies.

Clarify that this skill is invoked only when non-data diagrams are needed, to sharpen the boundary against the data-plotting skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions tied to specific inputs — '生成技术路线图、子问题求解流程图、模型结构图、数据处理流程图等 DrawIO 图' and '导出论文可引用 PDF' from ANALYSIS_MODELING_REPORT.md / RESULTS_REPORT.md / figures/ — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Clearly answers 'what' (generate non-data DrawIO diagrams and export PDFs) but the 'when' is only implied through pipeline-stage framing with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Includes natural terms a user would say in this domain — '数学建模', '技术路线图', '求解流程图', '模型结构图', 'DrawIO', 'PDF' — giving good coverage of natural keywords rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — non-data diagrams via DrawIO in math modeling, explicitly scoped away from data charts — making it unlikely to trigger the wrong skill; not score 2 because the niche and triggers are genuinely distinct.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
jihe520/MathModelAgent
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.