CtrlK
BlogDocsLog inGet started
Tessl Logo

1start-mathmodel

数学建模竞赛工作流入口。用于启动完整建模流程:询问用户偏好,生成 plan.md 和 todo.md,并按阶段调用赛题分析、建模、代码与图表、流程图、论文撰写、验证验收等 skills。

60

Quality

70%

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/1start-mathmodel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 skill body is highly actionable with concrete templates, commands, and code, and uses progressive disclosure cleanly. Workflow clarity is the main gap: inter-stage validation is delegated to the end rather than checkpointed between stages.

Suggestions

Add an explicit validation checkpoint after each stage (e.g. 'Before advancing, confirm the expected report file exists and is non-empty') instead of deferring all validation to 6verity.

De-duplicate the stage list — keep the authoritative table and trim the repeated prose enumeration to reduce token cost.

Note that ../_references/math_modeling_norms.md is an external reference outside the bundle; confirm the path resolves or move it under references/.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes competence, but the stage list is restated across prose, a workflow code block, a table, and the todo template, which could be tightened.

2 / 3

Actionability

Provides copy-paste-ready plan.md/todo.md templates, a concrete directory skeleton, engine commands (typst/xelatex), and exact figure-insertion code for both Typst and LaTeX.

3 / 3

Workflow Clarity

Stages are clearly sequenced with stage-boundary rules and a per-stage todo update, but there is no explicit inter-stage validation checkpoint before the final 6verity stage — only an implicit handoff.

2 / 3

Progressive Disclosure

A single one-level-deep reference (../_references/math_modeling_norms.md) is clearly signaled and scoped, and the body is organized into well-delineated sections.

3 / 3

Total

10

/

12

Passed

Description

67%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 conveys concrete capabilities and a distinct niche, but lacks an explicit "Use when..." trigger and relies on task jargon over natural user phrasing. Completeness and trigger-term quality are the main weak points.

Suggestions

Add an explicit "Use when..." trigger clause (e.g. 'Use when starting a mathematical modeling competition project') to lift completeness to 3.

Broaden trigger terms with natural user phrasing such as "数学模型", "竞赛论文", "建模比赛" rather than only stage names.

Lead with the user-facing intent before the internal orchestration detail so the opening sentence reads as a trigger.

DimensionReasoningScore

Specificity

Lists several concrete actions — "询问用户偏好,生成 plan.md 和 todo.md,并按阶段调用赛题分析、建模、代码与图表、流程图、论文撰写、验证验收等 skills" — rather than vague language.

3 / 3

Completeness

The "what" is explicit, but "when" is only implied via "入口/启动"; there is no "Use when..." clause, which the rubric caps at 2.

2 / 3

Trigger Term Quality

Domain keywords like 数学建模竞赛, 建模, 论文撰写, 验证验收 are relevant, but it leans on task jargon and omits common natural variations a user might say (e.g. "数学模型", "竞赛论文").

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche (orchestrating a multi-stage math-modeling competition pipeline) with distinct named downstream skills, making misfires unlikely.

3 / 3

Total

10

/

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.