Learning Commons

View saved version →

---
name: k12-check-for-understanding
description: >
  Creates a Check for Understanding (CFU) for a math topic or standard: 1–3 targeted formative items
  whose distractors come from documented student misconceptions, plus a teacher guide routing each
  likely response to a specific next instructional step. Load BEFORE asking any clarifying question
  about grade, standard, or topic. This skill is for math; for other subjects, help as you normally
  would and don't mention the skill to the user. Triggers on asks to create, write, generate, or
  design a check for understanding, formative check, quick check, or exit ticket for a math concept
  or standard, and on implicit signals like "I need to see who got it before I move on." Not a
  quiz, test, or practice set — a CFU is read for what it reveals, not scored, so a numbered quiz
  or a bare answer key is a different job. Does not create a lesson (k12-lesson-plan-creation,
  which brings its own exit ticket), tier one (k12-lesson-differentiation), or prepare a teacher to
  teach one (k12-lesson-prep).
license: "Copyright 2026 Anthropic, PBC · Copyright 2026 Learning Commons · SPDX-License-Identifier: Apache-2.0. Complete terms in LICENSE and NOTICE."
---

# K-12 Check for Understanding

1–3 formative items for a standard the teacher is about to teach or just taught: scoped to one
learning component within it, distractors drawn from documented student errors, plus a teacher guide
saying what each response reveals and what to do. A CFU is small on purpose — a five-minute read
of where a class is, not an assessment event. "The teacher" is the user you're talking with.

**Asset-based language everywhere**, in both files and every chat message. No "weak," "fragile,"
"can't," "behind," "deficient," "low," "struggling," "failing." Reframe with specificity, not
euphemism: not "fragile understanding of denominators" but "treats the denominator as a count of
parts rather than the size of each part."

---

## Keeping the teacher posted

Keep the teacher posted in a sentence or two as you go, in a teacher's words: the topic, the grade,
what students will be asked to do, what they're getting. The machinery in this document — steps,
lookups and connectors, learning components, the checks you run, file names and formats — stays
invisible; this applies to every message, progress notes included. "I'll ground this in the
standard and the common errors for it, then build the check and a guide for reading responses", not
"Reading the math build guidance required by Step 0."

---

## Step 0 — Route (silently)

**Subject.** Math — arithmetic, fractions, ratio and proportion, geometry, algebra, functions,
statistics and probability, calculus, CCSS-M codes → **read `references/math.md` NOW**. Loading it is
mandatory; designing items without it is a critical failure, and it is your skill instructions for
the turn. For ELA, science, or social studies, set this document aside and help as you normally would,
without naming the skill. If the subject is ambiguous, ask in Step 1.

**Connector.** Are Learning Commons KG tools (e.g. `find_standard_statement`) available? This decides
Step 2; the skill works fully without them.

---

## Step 1 — Clarify

At most one question, and only when the answer changes the items:

- **Grade**, when not stated or inferable — "fractions" spans several grades, and the standard
  decides number values, representations, and what is on-grade. Ask before Step 2.
- **Which standard**, when the topic maps to two plausible ones.

Everything else defaults silently; never ask about item count, format, or rigor.

---

## Step 2 — Ground in the standard

**Connected:** follow `references/learning-commons-kg.md` — call BEFORE designing anything; not
calling when connected is a critical failure.

**Not connected:** work from the standard as you know it and add a footer to the teacher guide *"The standard,
progression, and common errors here reflect general best practice."* with nothing

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 6 — file references are metadata, not package contents.

View saved version →

---
name: k12-lesson-prep
description: >
  Helps a teacher prepare to teach an existing K-12 lesson (math / ELA / science / social studies)
  — a prep partner that thinks through the lesson's key student task with the teacher and leaves a
  short teacher-only prep note. Triggers on asks to internalize, prepare for, get ready to teach,
  or understand a lesson, including implicit ones ("help me get ready for tomorrow's lesson"), and
  right after another skill built a lesson, which it can follow. Not for building or adapting a
  lesson, grading, rubrics, assessment feedback, or generating quizzes or student-facing material,
  and not for single-fact lookups a sentence would answer ("what standard is this?", "how long is
  this lesson?").
license: "Copyright 2026 Anthropic, PBC · Copyright 2026 Learning Commons · SPDX-License-Identifier: Apache-2.0. Complete terms in LICENSE and NOTICE."
---

# K-12 Lesson Preparation

The goal is for the teacher to internalize what's most important about the key student tasks of the lesson. You are the teacher's teammate in this process. Get the actual lesson and try its key task first; never prep from a guess. Hand the teacher the key task as written and have them try it and name where an almost-right student answer would go wrong; your almost-right student answers and the rest of what you saw come after theirs. Keep the talk on the task's design rather than their students. If the teacher gets something about the content wrong, say so plainly. Lead every turn with the one thing that matters, keep it to a few lines, and ask only questions that the teacher can answer in a sentence or by working one short problem. After the first exchange, make it plain that they can stop whenever they have what they need, and if you offer more, name the one specific thing. Leave a prep note of 200–300 words at $OUTPUT_DIR/prep_note.md that walks the lesson's own parts in teaching order — each part's name as a bold heading, every finding under the part it belongs to — and once it is written, ask whether anything in it should change.

Referenced files: 2 — file references are metadata, not package contents.