CtrlK
BlogDocsLog inGet started
Tessl Logo

teacher-style-clone

工作台会话挂载了教师课堂录像/讲义材料时使用。

58

Quality

73%

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/agent-runtime/teacher-style-clone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 an excellent procedural skill: lean, fully actionable with concrete tool calls and field-level placement instructions, and a well-validated five-step workflow with explicit error-recovery branches and evidence-gating hard rules. The only structural note is that at its current length a small reference file could keep SKILL.md closer to overview size.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout ('Call `list_materials` before drawing conclusions', 'Do not sample only the beginning') with no explanation of concepts Claude already knows and no padded sentences — every token earns its place, matching anchor 5.

5 / 5

Actionability

Although instruction-only (no code, which is not penalized here), the guidance is fully executable: exact tool names, explicit branching on extraction state (idle/pending/failed), exact output field placement (`## 讲课风格` in `brief`, `generate_scene.materialFacts`), and copy-ready example values like 「以复习上节课的问题开场」.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation checkpoints and feedback loops: Step 1 verifies extraction completeness and handles each failure state, Step 4 verifies hypotheses with `search_material` and drops unsupported ones, and 'Hard rules' gates the final output — matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and the ~77-line body is well organized into Step sections plus Hard rules, so nothing is misplaced; however it exceeds the under-50-line simple-skill guideline and the Step 2 style-profile checklist / example brief content are plausible candidates for a reference file, matching anchor 4 rather than 5.

4 / 5

Total

19

/

20

Passed

Description

40%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 gives a clear, specific trigger condition but completely omits what the skill does, leaving both capability discovery and trigger precision weakened. It reads as a domain fragment rather than a capability statement.

Suggestions

Add a 'what' clause describing the actions, e.g. 「从挂载的教师课堂录像/讲义中提取讲课风格,并以该风格讲授用户指定的主题。工作台会话挂载教师课堂录像/讲义材料时使用。」

Include natural trigger synonyms such as 名师风格、讲课视频、课堂录像 so the description matches the learner-facing vocabulary already used in the body.

Keep the third-person declarative form and avoid the internal terms 'clone'/'style transfer' that the body deliberately hides from learners.

DimensionReasoningScore

Specificity

The description names the domain ("教师课堂录像/讲义材料" mounted in a workbench session) but states no actions at all — it matches the anchor 'Names the domain but actions are minimal or generic' rather than anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Only a 'when' clause is present ('时使用') with no 'what' — the skill's actual capability (extracting the teacher's style and teaching a requested topic in it) is absent, exactly matching anchor 2's 'only when is present without what'.

2 / 5

Trigger Term Quality

Terms like 教师课堂录像, 讲义材料, and 挂载 are relevant domain keywords, but no synonyms or variations (e.g. 名师, 讲课视频, 课件) are covered, matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The trigger condition (teacher classroom recordings/handouts mounted) is a narrow, distinct niche with minimal conflict risk, but the missing capability statement means it could fire for any task touching those materials, matching 'Mostly distinct; minor overlap risk'.

4 / 5

Total

11

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
THU-MAIC/OpenMAIC
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.