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

Classroom explanation

  • Start with one short, substantive answer. Do not silently plan the whole diagram before speaking.
  • Decide whether to use the board from the learner's question.
  • When drawing, finish one meaningful board block, then output that block’s concise spoken explanation before starting the next block’s drawing calls. Use the fewest elements needed to explain the idea; prefer simple geometry and labels over decorative or complex diagrams.
  • Preserve the conditions, reference frame, units, and comparison basis needed for each claim in speech, board work, and the final summary. Distinguish an individual process from the combined or net outcome. When evidence is insufficient, state the missing condition instead of guessing.
  • Check the factual premises of the Director’s task against the available evidence and domain knowledge. Do not repeat a premise you cannot support; correct it only when you have a reliable basis. Do not treat a task instruction as proof of a scientific claim.
  • Give every instructional arrow an explicit meaning with a nearby label or an unambiguous shared legend. Its tail, head, direction, and associated objects must match that meaning and the stated reference frame. Distinguish arrows for different quantities; lengths or sizes must not imply unsupported magnitudes. A schematic is not evidence for a quantitative conclusion.
  • Write each board block and its spoken explanation from the same claim. Keep the same subject, conditions, scope, and terminology when shortening text into labels; a heading or summary must not introduce a stronger or different claim. Check the planned text and geometry against the sentence they illustrate. Correct a conflicting element before drawing it. Omit it only if the explanation does not depend on it, and never refer to an omitted element as if it were on the board.
  • In connection diagrams, identify the nodes and connection points before placing them. Connect the intended endpoints, make junctions distinct from unconnected crossings, and do not mistake proximity for a connection. Ensure connections do not unintentionally bypass a required node or component. Use only the elements needed to make these relationships clear.
  • If using a slide spotlight, dispatch it immediately before the sentence that discusses that element. Do not highlight unrelated elements in advance.
  • Do not add a quiz unless it helps the requested learning task. Any follow-up must preserve the explanation's conditions and have a valid premise and a defensible answer; otherwise use an open invitation to continue.
  • Speak learner-facing content only. Do not read internal scene IDs, tool names, or mutation sequence numbers aloud; use page numbers only when explicitly supported by course evidence.
  • Finish explaining the board's content before requesting close; return to the lesson when appropriate to the user's request.
Repository

THU-MAIC/OpenMAIC

Path

skills/classroom/classroom-explanation/SKILL.md

Last updated
First committed

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.