CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

classroom-explanation

Explain a classroom question with concise speech and optional simple board work.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/classroom/classroom-explanation/SKILL.md
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.

The body is a lean, well-ordered behavioral instruction set that assumes Claude's competence and gives unusually specific pacing and sequencing directives for speech-plus-board-work interaction. Its main weakness is density: several bullets fuse multiple rules into single overloaded sentences, and a couple of abstract rules would land better with a one-line good/bad example.

Suggestions

Split the overloaded multi-rule bullets (arrow semantics, claim consistency) into shorter one-rule lines so each instruction is independently checkable.

Add a one-line good/bad example for the abstract rules, e.g. a label that weakens a claim vs. one that preserves its conditions.

Make the pre-close verification explicit (a final check that every drawn element was explained and no omitted element is referenced) to complete the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is ~13 dense bullets with zero padding and no explanations of concepts Claude already knows — every bullet encodes non-obvious policy such as "Do not silently plan the whole diagram before speaking". It falls short of a 5 because several bullets (the arrow-semantics and claim-consistency rules) each pack 4-5 distinct rules into one overloaded sentence that could be split or trimmed.

4 / 5

Actionability

Most rules are concrete, executable directives: "finish one meaningful board block, then output that block's concise spoken explanation before starting the next block's drawing calls", "identify the nodes and connection points before placing them", "dispatch it immediately before the sentence that discusses that element". As an instruction-only skill this is appropriately code-free, but a few bullets remain abstract ("Preserve the conditions, reference frame, units, and comparison basis needed for each claim") with no example of a compliant vs. non-compliant board block, keeping it below 5.

4 / 5

Workflow Clarity

A clear sequence is present: answer aloud first, decide on board use, loop draw-block-then-explain per block, time spotlights to sentences, finish the board before requesting close. Checkpoints exist ("Check the planned text and geometry against the sentence they illustrate. Correct a conflicting element before drawing it"; premise-checking before repeating a Director's task), matching 'clear sequence with most checkpoints present'. Not a 5 because a couple of checkpoints are implicit — e.g., no explicit final verification pass before close beyond the one-line reminder.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no need for external references; the flat, logically ordered bullet list is well-organized with each bullet covering one concern. Per the rubric's simple-skill guidance, this earns a 5 — nothing here belongs in a separate reference file, and there are no nested or buried references.

5 / 5

Total

17

/

20

Passed

Description

50%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 states a clear, compact 'what' with domain-appropriate vocabulary, but completely omits any trigger guidance ('when to use'), which caps completeness and weakens trigger quality. Adding an explicit 'Use when...' clause with natural trigger phrases would raise most dimensions at once.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. "Use when asked to explain a classroom/lesson question aloud, walk through a problem at the board, or teach a concept to learners."

Enumerate the skill's main capabilities more specifically (spoken explanation paced to board blocks, simple labeled diagrams, slide spotlights, optional follow-ups) instead of the single generic action "explain".

Include natural synonyms users would say — teach, lesson, lecture, student question, diagram, board — to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Explain a classroom question with concise speech and optional simple board work" names the domain and 1-2 concrete actions (spoken explanation, simple board work), but coverage is not comprehensive — none of the body's other capabilities (diagrams, spotlights, follow-ups) are reflected. It is more concrete than the score-2 anchor ('names the domain but actions are minimal') but does not list several specific actions, so it is not a 4.

3 / 5

Completeness

The 'what' is clearly stated (explain a classroom question via concise speech with optional board work), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not a 4 because the when is not even weakly implied.

3 / 5

Trigger Term Quality

Terms like "classroom", "question", "speech", and "board work" are natural and relevant, but common variations a user would actually say — "teach", "lesson", "lecture", "student question", "diagram" — are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The classroom/board-work framing gives it a recognizable niche, but "Explain a classroom question" is phrased broadly enough to overlap with general explanation, presentation, and diagramming skills. It fits 'somewhat specific but could still overlap with similar skills' better than the mostly-distinct score-4 anchor.

3 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

THU-MAIC/OpenMAIC

Path

skills/classroom/classroom-explanation/SKILL.md

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.