CtrlK
BlogDocsLog inGet started
Tessl Logo

3coding-visual

数学建模编程实现与数据图表生成阶段。根据 ANALYSIS_MODELING_REPORT.md 编写可复现代码、运行求解、验证约束、输出 RESULTS_REPORT.md 并生成论文可用的数据驱动图表 PDF。

59

Quality

69%

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/3coding-visual/SKILL.md
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.

The content is a lean, well-structured, actionable instruction set with a clear sequenced workflow and named validation checkpoints; its main gaps are an implicit rather than explicit error-retry loop and an external reference that points to a missing file.

Suggestions

Make the validation feedback loop explicit (e.g. "若约束校验失败,修正后重跑并复校,直到通过再进入下一步").

Verify the ../_references/math_modeling_norms.md path resolves, or move the norms into a bundled references/ file the skill ships with.

Tighten the "典型图表" enumeration into a compact mapping so each problem type maps to one or two chart kinds.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — short intro, stage boundaries, four steps, a compact report skeleton, and chart requirements — with only minor list-heavy prose ("典型图表" enumerations) that could be trimmed.

4 / 5

Actionability

Concrete, specific guidance throughout: named code/ and figures/ directories, a RESULTS_REPORT.md section skeleton, per-problem-type chart lists, and PDF/caption rules; gaps are the deliberately loose "不强制固定脚本名" and the absence of any code stubs.

4 / 5

Workflow Clarity

A clear four-step sequence with a per-subproblem 6-item checklist and named checkpoints (验证约束、校验结果、约束与一致性校验), but the validate→fix→re-run feedback loop is only implicit rather than an explicit retry loop.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level-deep reference to the math_modeling_norms.md knowledge base; minor gaps are that no bundle files exist and the referenced ../_references path does not resolve to a real file.

4 / 5

Total

16

/

20

Passed

Description

63%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 specific and well-scoped to a distinct pipeline stage with clear concrete actions, but it omits any explicit trigger guidance, which caps completeness and leaves minor conflict risk with generic coding skills.

Suggestions

Add a "Use when..." clause naming natural user triggers (e.g. "在数学建模需要编程求解、验证约束并出图时使用").

Replace procedural file names with user-facing trigger phrases and synonyms users actually say.

Keep the concrete action list but pair each with the scenario that calls for it to answer both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named artifacts — "编写可复现代码"、"运行求解"、"验证约束"、"输出 RESULTS_REPORT.md"、"生成论文可用的数据驱动图表 PDF" — covering the full coding-to-figures pipeline comprehensively.

5 / 5

Completeness

The "what" is clear and comprehensive, but there is no "Use when..." clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Domain terms like "数学建模"、"数据图表"、"约束" are relevant, but the description leans on file/procedural names (ANALYSIS_MODELING_REPORT.md, RESULTS_REPORT.md) rather than the natural phrases and synonyms a user would actually say to invoke this skill.

3 / 5

Distinctiveness Conflict Risk

The pipeline-specific niche (承接 2analysis-modeling, 产出 RESULTS_REPORT.md 和 figures) is distinct, but with no explicit "when" clause there is minor overlap risk with general code-and-chart skills.

4 / 5

Total

15

/

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.

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.