CtrlK
BlogDocsLog inGet started
Tessl Logo

teach

在这个工作区中教用户一个新技能或概念。

40

Quality

40%

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/productivity/teach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 clear, well-organized conceptual skill that gives Claude a coherent teaching model and concrete file-management conventions, but it re-explains some general learning science and lacks executable code or explicit validation checkpoints. Its progressive-disclosure references look good on paper but point to bundle files that are not present.

Suggestions

Trim the Philosophy and Fluency-vs-Storage-Strength exposition to the non-obvious decisions (e.g. why desirable difficulty, how to compute zone of proximal development) and drop lines Claude already knows.

Add one concrete, copy-paste-ready lesson scaffold (HTML skeleton linking the shared stylesheet and one asset) and a sample quiz-widget snippet so the guidance is executable rather than descriptive.

Provide the missing referenced files (MISSION-FORMAT.md, RESOURCES-FORMAT.md, LEARNING-RECORD-FORMAT.md) under the bundle directories, or remove the dead links, so the progressive-disclosure structure is actually navigable.

DimensionReasoningScore

Conciseness

The body is mostly efficient conceptual guidance written for Claude, but sections like Philosophy and the fluency/storage-strength and retrieval/spacing/interleaving exposition re-explain learning science Claude already knows, and some lines ('想想 Tufte', 'Learners 的 working memory 非常小') add gentle padding. It is above 2 (not severely or noticeab ly padded) but below 4 because the conceptual exposition could be trimmed without losing actionability.

3 / 5

Actionability

Guidance is concrete and specific in places (file naming '0001-<dash-case-name>.html', '每个答案都应有完全相同的词数', '通过运行 CLI command 为用户打开 lesson file'), but much of it is descriptive rather than instructional and there is no executable code or command template. For an instruction-only skill this is partly acceptable, yet key actions remain high-level hints (e.g. how exactly to build a lesson, what a quiz widget looks like), so it sits at 3 with minor gaps rather than 4.

3 / 5

Workflow Clarity

The body sequences a clear teaching flow (ground in MISSION.md -> read learning-records -> judge zone of proximal development -> build lesson from ./assets -> cite primary source -> record learning), but it has no explicit validation checkpoints and the 'change mission 前先和用户确认' is the only feedback-loop guard. The destructive/batch cap (validation absent for batch/destructive ops) is not triggered, but checkpoints are mostly implicit, matching the score-3 anchor.

3 / 5

Progressive Disclosure

The SKILL.md is a well-sectioned overview that signals one-level-deep references to format files (MISSION-FORMAT.md, RESOURCES-FORMAT.md, LEARNING-RECORD-FORMAT.md) and asset/lesson/reference directories. However, none of those referenced bundle files actually exist in ./references, ./scripts, or ./assets, so the navigation points to missing files and the structure is partly notional. That gap keeps it at 3 rather than 4 (good structure but references not verifiably backed).

3 / 5

Total

12

/

20

Passed

Description

30%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 concise but too thin: it states a single vague action (teaching a skill or concept) with no 'Use when' trigger guidance and no enumeration of concrete capabilities, leaving Claude little to decide invocation on. It does name a clear niche (a teaching workspace), which prevents it from being entirely generic.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to learn a new skill or concept and expects a multi-session guided lesson plan.'

Enumerate concrete capabilities so the action is not a single generic verb, e.g. 'Builds interactive HTML lessons, maintains learning records, curates reference materials, and tracks a user's zone of proximal development.'

Include natural trigger terms a user would actually say ('我想学', '教我', '学一下', 'learn', 'teach me') and a distinguishing signal so it does not conflict with general explanation skills.

DimensionReasoningScore

Specificity

The description '在这个工作区中教用户一个新技能或概念' names the domain (teaching a skill or concept) but offers only a single minimal action ('教'); no concrete capabilities are enumerated, so it sits at score 2 (names domain but actions minimal/generic). It is below 3 because there is no second concrete action, and above 1 because it does name a clear domain.

2 / 5

Completeness

There is a vague 'what' (teach a skill/concept in this workspace) and no 'when'/'Use when...' clause at all. The rubric caps completeness at 3 for a missing trigger clause, and since 'when' is entirely absent rather than weakly implied, score 2 ('vague what and no when') is the best fit.

2 / 5

Trigger Term Quality

Only the single generic keyword '教' and '技能或概念' appear; the natural phrases a user would say when needing this skill (e.g., '我想学', '学一下', 'tutorial', 'teach me') are absent. This matches the 'one or two generic keywords; missing the natural phrases users say' anchor.

2 / 5

Distinctiveness Conflict Risk

The phrase '在这个工作区中教用户一个新技能或概念' is somewhat specific to a teaching workspace and not entirely generic, but it could still overlap with general tutoring or explanatory skills and offers no distinct trigger. It fits the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

9

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (19 chars), consider making it more detailed

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
vinvcn/mattpocock-skills-zh-CN
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.