CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-explainer

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

71

Quality

87%

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

78%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.

A well-structured, actionable template skill: the mandated article structure, quantified content thresholds, and diagram specifications give Claude everything needed to execute in one pass. Main gaps are the absence of a worked example (especially a sample SVG/Mermaid block) and the lack of any fact-checking or fix-and-retry step around the generation workflow.

Suggestions

Add a short worked example — one completed section (e.g., 直觉理解) with an actual SVG and Mermaid snippet — so the diagram conventions are demonstrated, not just specified; this would raise actionability to the top anchor.

Insert a verification step into 执行步骤 (e.g., 'before writing, verify the derivation and dates against reliable sources; if uncertain, mark claims as tentative') and pair the quality checklist with an explicit fix-and-retry loop.

Fold the soft 写作风格要求 guidance into the template's inline section hints to trim redundancy and tighten conciseness.

DimensionReasoningScore

Conciseness

The body is efficient: every section carries instructions Claude does not already know (the mandated article template, file naming, SVG viewBox specs, Mermaid node limits, count thresholds), with no padding that explains known concepts. It falls short of the 'every token earns its place' level-5 anchor because sections like 写作风格要求 ("通俗优先", "有温度") are soft guidance that could be tightened into the template itself.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: an exact article skeleton in a copyable code block, filename convention (`{主题拼音或英文}.md`), save path, diagram-spec table, and quantified content floors (正例 ≥ 3, 反例 ≥ 2, 问题 ≥ 3, 图表 ≥ 2 种). It misses level 5 because no sample output is shown — e.g., one filled-in section with an actual SVG or Mermaid snippet — so the diagram conventions are specified but never demonstrated.

4 / 5

Workflow Clarity

The 执行步骤 section gives a clear 7-step sequence from input classification through `mkdir -p markdown` to saving and presenting the file, and the final 质量检查清单 acts as an explicit validation checkpoint. It does not reach level 5 because the checklist is stated as post-hoc confirmation with no fix-and-retry loop, and there is no step to verify factual accuracy of the derivation before writing.

4 / 5

Progressive Disclosure

The bundle is a single SKILL.md (no references/, scripts/, or assets/ directories exist, and the body references no external files), yet nothing here clearly belongs in a separate file — the template, diagram rules, and checklist all need to be in view at generation time. Sections are well-organized with clear headers and a navigable structure, matching the well-organized single-file ideal.

5 / 5

Total

17

/

20

Passed

Description

96%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.

A strong description: it explicitly states what the skill produces, where output goes, and when to use it, with an unusually rich set of natural-language trigger phrases. The only weakness is that broad trigger words like "解释"/"原理" create some overlap risk with general explanation skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "生成面向学生的公理/定理深度讲解文案" (generate illustrated explainer articles), "输出保存到项目 markdown/ 目录" (save to a specific directory), a mandated three-section structure ("求真讲法、求存讲法、思考"), and required chart types ("SVG/Mermaid/ASCII 图表"). It stays in third person, so no voice penalty applies; it exceeds the 'several specific actions' level-4 anchor by covering the full pipeline from generation to file placement.

5 / 5

Completeness

Both 'what' and 'when' are answered explicitly and concretely: the 'what' is the illustrated Markdown explainer with its defined structure and save location, and the 'when' is an explicit trigger clause ("触发条件:用户输入一个观点、公理、定理…并希望获得系统性讲解文章") reinforced with example trigger phrases. This mirrors the level-5 good_overall_example pattern of capability list followed by an explicit 'Use when…' equivalent.

5 / 5

Trigger Term Quality

Keyword coverage is comprehensive and natural, including synonyms and colloquial phrasings users would actually say: "讲解", "解释", "推导", "怎么来的", "有什么用", plus explicit example utterances "帮我讲讲XX定理" and "解释一下XX原理". This matches the top anchor's standard of natural terms plus variations, rather than merely 'good coverage with a few missing' (level 4).

5 / 5

Distinctiveness Conflict Risk

The niche is clear (axiom/theorem/proposition explainers with a signature three-section structure) and mostly distinct from other skills. However, generic triggers like "解释" and "解释一下XX原理" could pull in general concept-explanation or tutoring requests that overlap with other explanation-style skills — minor overlap risk, fitting the level-4 anchor rather than the minimal-conflict level-5 anchor.

4 / 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.

Validation — 16 / 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.