CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-explainer

生成面向学生的公理/定理深度讲解文案,输出图文并茂的 Markdown 文章。触发条件:用户输入一个观点、公理、定理或数学/科学/哲学命题,并希望获得系统性讲解文章。关键词包括:"讲解"、"解释"、"公理"、"定理"、"原理"、"推导"、"怎么来的"、"有什么用"、"证明"等。即使用户只说"帮我讲讲XX定理"或"解释一下XX原理",也应使用本 skill。输出保存到项目 markdown/ 目录,文章结构涵盖求真讲法、求存讲法、思考三大核心板块,并包含 SVG/Mermaid/ASCII 图表辅助理解。

68

Quality

83%

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

72%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 well-structured, actionable instruction skill with concrete templates, chart specs, and a checklist, all reasonably token-efficient. Its main weakness is workflow_clarity: the steps lack an explicit validation gate between article generation and file save.

Suggestions

Add an explicit validation checkpoint between 生成文章 and 保存文件 — e.g., '4. 生成文章 … 5. 校验:对照质量检查清单逐项确认后再保存' — turning the post-hoc checklist into an inline validate-then-proceed loop.

Include one short worked example (a few lines of a finished article for a simple theorem like 勾股定理) so the template and chart requirements are concretely imitable.

Tighten the parenthetical coaching asides in the template (e.g., '讲故事,有温度', '你有没有想过……') into a single style note to reduce token overhead.

DimensionReasoningScore

Conciseness

Largely efficient and task-focused without explaining concepts Claude already knows, though parenthetical coaching asides (讲故事,有温度; 你有没有想过……) and the inline template guidance could be trimmed slightly.

4 / 5

Actionability

Provides a literal article template, file-naming rule, save path with mkdir, concrete SVG viewBox and Mermaid syntax specs, and a quantified checklist; minor gap is the absence of a fully worked example article to imitate.

4 / 5

Workflow Clarity

A clear numbered 7-step sequence and a post-hoc checklist exist, but there is no explicit validation checkpoint between generation and save, and verification is implicit rather than an inline validate-then-proceed loop.

3 / 5

Progressive Disclosure

Self-contained in SKILL.md with well-organized, clearly labeled sections (目标/输入/输出规格/模板/图表指南/风格/步骤/检查清单) and no bundle files needed, so the single-file structure is appropriate and navigable.

5 / 5

Total

16

/

20

Passed

Description

95%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 concrete capabilities, provides a rich set of natural trigger keywords with colloquial variants, and explicitly covers both what the skill does and when to use it, in third-person voice. Minor room to sharpen the 'what' from a single article type toward a broader action catalog.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions (生成 Markdown 文章, 三大核心板块, SVG/Mermaid/ASCII 图表, 保存到 markdown/ 目录), but it is one output type rather than a comprehensive catalog of distinct actions.

4 / 5

Completeness

Explicitly answers both 'what' (生成图文并茂 Markdown 文章,涵盖求真/求存/思考板块及图表) and 'when' (触发条件:用户输入公理/定理/命题并希望系统性讲解) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user terms including synonyms and colloquial phrasings (讲解, 解释, 公理, 定理, 推导, 怎么来的, 帮我讲讲XX定理, 解释一下XX原理), going well beyond a few keywords.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (axiom/theorem deep-explanation articles with a three-section structure) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
digoal/blog
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.