[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718H9E71NBT9CAAGEJW209P":3,"skill-same:01M718H9E71NBT9CAAGEJW209P":149},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":24,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M718H9E71NBT9CAAGEJW209P","k12-lesson-differentiation",null,"Adapts an existing K-12 lesson (math, ELA, science, or social studies) for students at different proficiency levels (below \u002F at \u002F above grade level). Load this skill BEFORE asking the teacher any clarifying question about the lesson, tiers, or student levels. Triggers on explicit asks to differentiate, tier, or scaffold a lesson, and on implicit signals like \"my students are at different levels\". Produces 1 teacher-facing differentiation plan + 3 student-ready tier documents as editable, printable documents in a single output turn (shared content is written once, so tiers cannot drift). Uses the Learning Commons Knowledge Graph when connected; works without it. This skill adapts a lesson the teacher brings or names. Not for creating a new lesson from scratch — a new-lesson request that asks for differentiated or leveled materials is k12-lesson-plan-creation's job, one package. Not for grading, rubrics, assessment feedback, or quizzes.","anthropics\u002Fk12-teacher-skills","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718H0EV54ST8TETYE3MRSCB",630,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"k12 lesson differentiation","differentiation","lesson","drift","new","when","teacher","student","creation","shared","signals","documents","social","ready","question","math","plan","knowledge","knowledge graph","assessment","2026-11-10 10:12:30",false,"---\nname: k12-lesson-differentiation\ndescription: Adapts an existing K-12 lesson (math, ELA, science, or social studies) for students at different proficiency levels (below \u002F at \u002F above grade level). Load this skill BEFORE asking the teacher any clarifying question about the lesson, tiers, or student levels. Triggers on explicit asks to differentiate, tier, or scaffold a lesson, and on implicit signals like \"my students are at different levels\". Produces 1 teacher-facing differentiation plan + 3 student-ready tier documents as editable, printable documents in a single output turn (shared content is written once, so tiers cannot drift). Uses the Learning Commons Knowledge Graph when connected; works without it. This skill adapts a lesson the teacher brings or names. Not for creating a new lesson from scratch — a new-lesson request that asks for differentiated or leveled materials is k12-lesson-plan-creation's job, one package. Not for grading, rubrics, assessment feedback, or quizzes.\nlicense: \"Copyright 2026 Anthropic, PBC · Copyright 2026 Learning Commons · SPDX-License-Identifier: Apache-2.0. Complete terms in LICENSE and NOTICE.\"\n---\n\n# K-12 Lesson Differentiation\n\nPaths here (`references\u002F…`, `rendering\u002F…`) are relative to this SKILL.md's folder; use absolute\npaths.\n\nAdapts an existing K-12 lesson for below \u002F at \u002F above grade-level proficiency using\nresearch-based differentiation principles (Tomlinson framework + subject-specific access\ndesign). Works with or without the Learning Commons Knowledge Graph connector.\n\n\"The teacher\" throughout this skill is the user you are talking with — the same person, never\na third party. \"Teacher-facing\" names a document's audience: that user, as opposed to their\nstudents.\n\n---\n\n## Keeping the teacher posted\n\nOnce the teacher's path is set (the draft offer answered), say in one or two sentences\nwhat you're about to do (e.g. *\"I'll read your lesson, ground it in the standard and\ncurriculum materials, design the three tiers, and build the worksheets.\"*).\n\nWhen a task-list or to-do tool is available, also outline this skill's steps there so the\nteacher can watch them check off; the only reason to skip this is that no such tool exists\nin this conversation.\n\nThe teacher reads every line you write, the ones beside tool calls included. Between tool calls say\nnothing, or speak in teacher language: name what the teacher is getting — the differentiation plan\nand the three tier documents — never tool names, file names, \"JSON\", \"artboards\" or \"rendering\". Say\n\"Word document\" only on the Word path; otherwise \"your documents\" or \"pages\". The same goes for\nerrors: say the documents couldn't be made, not that a script or JSON failed.\n\n---\n\n## Step 0 — Route (silent, before anything else)\n\n1. **Subject.** Detect math \u002F ELA \u002F science \u002F social studies from the source lesson or the\n   request, then read the matching reference file NOW:\n\n   - math → `references\u002Fmath.md`\n   - ELA → `references\u002Fela.md`\n   - science → `references\u002Fscience.md`\n   - social studies → `references\u002Fsocial_studies.md`\n\n   **Loading the matching reference file is mandatory.** It carries the pedagogy for Steps 1\n   and 3 (source-lesson identification, curriculum detection, the eight differentiation rules\n   R1–R8, the document content templates, and the differentiation.json mapping).\n2. **Curriculum.** The subject file's \"Identify the source lesson\" section includes curriculum\n   detection (Illustrative Mathematics \u002F OpenSciEd). When confirmed, use that\n   curriculum's discourse language and structures in the teacher plan, per the subject file.\n\n   **Curriculum is confirmed when:** the teacher explicitly names it, OR the uploaded source\n   lesson references it (the upload is implicit confirmation).\n\n   **If curriculum is NOT confirmed** (not detectable from upload or link, no explicit mention):\n   never name a specific module, unit number, lesson number, or proprietary routine name anywhere\n   in the output OR in any chat message — even if you recognize the routine from training.\n   Describe the instructional move in your own generic terms (\"a compare-strategies\n   discussion\", not the routine's trademarked name). This is a hard rule; violating it fails P9,\n   and chat messages count. See **Copyright guardrail** (after Step 3) for the companion rule on\n   verbatim reproduction.\n3. **Connector.** Check whether the Learning Commons Knowledge Graph tools (e.g.\n   `find_standard_statement`) are available in this conversation. This decides which path\n   Step 2 takes. The skill is fully functional without the connector.\n\n4. **State.** Before any KG call, scan the conversation and any uploaded source lesson for\nstate signals and store as `state`:\n   - Teacher says \"I teach in [state],\" \"I'm in [state],\" or \"We're in [state]\"\n   - Standard codes follow a state-specific format (TEKS, SOL, OAS\u002FPASS, MA, CA\u002FHSS or\n     CA\u002FCCSS; other state-prefixed codes → check state)\n   - Source lesson URL includes a state agency domain (tea.texas.gov, etc.)\n\n   If state found: store `state = [state name]`. Pass as `jurisdiction=\"\u003Cstate>\"` in every\n   `find_standard_statement` call in Step 2. Use state framework codes (not national proxies)\n   in all output.\n\n   If state not found:\n   - for science, math, or ELA, proceed with national defaults (CCSS for math\u002FELA, NGSS for science). Add this single footer line to the teacher plan:\n   *\"Standards applied using [CCSS \u002F NGSS] — if you're in Texas, Virginia,\n   Oklahoma, or another state with a distinct framework, share your state and I'll re-anchor.\"*\n   - for social studies, ask the teacher what state they teach in before proceeding.\n\n---\n\n## Step 1 — Identify the source lesson\n\nFollow the subject file's source-lesson section: Scenario A (lesson exists earlier in this\nconversation — use it directly, do not re-ask), Scenario B (teacher uploads a lesson — read it\nfirst; if unreadable, say so and ask to re-share, never silently fabricate), Scenario B2\n(teacher links a lesson by URL — fetch and read it; if the fetch fails,\nask them to paste or upload), Scenario B3 (math or science only — teacher names a curriculum lesson by position or title —\ne.g. \"IM Grade 6, Unit 2, Lesson 3\" or \"the OpenSciEd lesson on ecosystem dynamics\" — Step 1\nis complete; proceed directly to Step 2 where `find_curriculum_lessons` will retrieve the\nlesson materials; do NOT ask the teacher to upload or link the lesson), or Scenario C (no source lesson present —\nask the subject file's clarifying question before proceeding).\n\nA fetched link lands in the conversation whole, so a document bigger than one lesson\n(a module or unit teacher edition) will not fit. When a link points at one, work from\nwhat the request itself tells you about the lesson and confirm the specifics with the\nteacher — topic, grade, and standard carry enough to build from, the same way Scenario C\nproceeds after its clarify.\n\n**Learner needs check (silent, runs every time):** Before generating, scan the conversation\nfor any mention of ELL levels, WIDA levels, IEP goal areas, 504 accommodations, or specific\nstudent needs. If found, incorporate into the tier design — especially the Below tier.\nSay \"home language,\" not a specific language, unless the teacher names one.\n\nIf no learner needs are mentioned AND the pre-generation R8 ask hasn't fired (scope was already\nspecified), add one sentence to the FIRST response: \"No specific learner needs were provided —\nI've applied UDL defaults (sentence supports and vocabulary across all tiers). Share any ELL\nlevels, IEP goals, or specific student data and I'll adjust.\"\n\nThis check runs even when scope is already specified.\n\n\n---\n\n## Step 2 — Ground in standards\n\n**If the LC Knowledge Graph is connected:** follow the subject's section in\n`references\u002Flearning-commons-kg.md` — call BEFORE drafting; not calling when connected is a\ncritical failure, no matter how the source lesson was obtained — retrieving\nthe lesson never satisfies this step.\n\n**If not connected:** proceed from best knowledge and add this footer to the teacher plan:\n*\"Generated without the Learning Commons KG. Standard text, prerequisite grounding, and\nmisconceptions reflect general best practice.\"* Do not invent KG citations.\n\n---\n\n## Step 3 — The differentiation rules\n\nApply **all eight rules (R1–R8)** from the subject file to every differentiated lesson. The\nrules are subject-specific (scaffold types, tier entry points, extension quality tests differ\nby subject) but their structure is shared: output structure (R1), standard scope preservation\n(R2), tier entry points (R3), below-level scaffolds with a density cap (R4), required\npedagogical infrastructure (R5), invisible modifications (R6), within-level progressive\nscaffolding (R7), and scope\u002Fdefaults (R8).\n\n---\n\n## Copyright guardrail\n\nAlways write original content. When the source lesson draws from a named curriculum (IM,\nOpenSciEd), use it to understand structure, scope, task context, and standards\nalignment only — never reproduce student-facing text, activity narratives, investigation\nprompts, comprehension questions, or problem contexts verbatim from curriculum materials.\nEach subject reference file carries a **Copyright** line with subject-specific details.\n\nIf curriculum is NOT confirmed (see Step 0.2 detection rules), never name a specific\ncurriculum, module, unit number, lesson number, or proprietary routine name anywhere in the\noutput or in any chat message — even if recognizable from training. The source lesson and\nKG data inform the design without being cited. See Step 0.2 for the full rule (P9).\n\n---\n\n## Step 4 — The draft offer\n\nThe teacher gets the choice of a fast draft before the build. The offer rides with\nwhatever you ask before Step 2 (state, source lesson, learner needs — structured question\ntool when available, chat otherwise) as its own separate question, and is asked on its\nown when nothing else needs asking. Its two sides are always the set and the draft. The\nwording below lives in the question itself:\n\n- Question: *Should I build a full classroom-ready set (teacher plan + three tier documents, as\n  editable, printable documents), or do you want to see a quick draft first?*\n- Options: **Go ahead and build it** · **Quick draft first** — what changes for each\n  tier, right here in chat\n\n**The full set is the default.** A reply that selects the draft option or asks to see\nthe draft gets the draft; every other reply runs Steps 2–3 and goes straight to Step 5.\n\n**The draft (on a yes) is built on Steps 2–3, never instead of them.** Run Step 2 in full — every KG\ncall, exactly as written — and Step 3 before sketching anything. A draft sketched without the Step 2\ngrounding is a critical failure. Then present the design in chat — the draft is chat text only; the\ndocuments are made at Step 5 once the teacher approves. Show:\n\n- one line reading back the source lesson, standard, and grade;\n- for each tier (below \u002F at \u002F above), 2–3 bullets on what changes and why;\n- the student work at a glance — each tier's actual tasks, enough for the teacher to\n  skim and judge coverage;\n- one line on what every tier shares — the essential question or core task — and the\n  regroup rule\n\nThe draft borrows its names from the documents it previews — phases, tasks, tiers,\nand sections are called what the plan will call them.\n\nAfterwards, ask what's next in plain chat — a typed reply can carry the changes themselves, which a\npicked option cannot: *\"Want anything different? Tell me here — or tell me to go ahead and I'll\ncreate the materials (teacher plan and the three tier documents, as editable, printable\ndocuments).\"*\n\nApply change requests to the draft in chat and re-present it — changes are quick at this\nstage. Step 5 runs in the turn the teacher gives the go-ahead.\n\n---\n\n## Step 5 — Output (one turn)\n\nRuns immediately when the teacher chose the full set, or in the turn the draft is\napproved.\n\n### 5a. Read references and make the common JSON\n\n1. Read `references\u002Foutput.md` in full first: the hard requirements for every document's content.\n2. Then read `references\u002Fdifferentiation-json.md` and write ONE complete **`differentiation.json`**,\n   the set's common baseline. Every path makes its documents from it; it fixes WHAT each document\n   carries, not how a page looks.\n\n### 5b. Make every document — same turn\n\nCheck whether your artifact tool can create an artifact from a published type; if it can, look at\nits type list. Take the first row that applies and read its file:\n\n| What you have | Read |\n|---|---|\n| **Design** is in the type list | `rendering\u002Fclaude-artifact.md` |\n| Design isn't listed, or there is no such tool | `rendering\u002Fdocx.md` |\n\nIf making the documents fails entirely, say so — don't silently fall back to chat.\n\n### 5c. The close (every output turn)\n\nThe chat message that delivers artifacts ends with three things, in order. Each must appear in\nthe chat message itself — saying it only inside the printed plan does not count. When the\nmessage mentions the sheets, use their group names with the association noted once\n(Group A = below grade level, etc.).\n\n1. **Learner-variability statement (first output turn, when you didn't ask).** If you never\n   asked about specific learner needs in this conversation (the R8 question), state in chat\n   that UDL defaults were applied and invite specifics — e.g. *\"I didn't have details on\n   specific learner needs, so I applied UDL defaults — sentence stems and a vocabulary\n   glossary on all three tier sheets. Tell me about any multilingual learners or students\n   with IEPs or 504 plans and I'll tailor further.\"* Skip this only when the teacher already\n   gave learner information (then reflect it instead: \"the Below sheet builds in the sentence\n   frames for your newcomer ELLs\").\n2. **Three lesson-specific next steps (first output turn).** Offer 3–4 iteration options in\n   chat, one short line each, specific to THIS lesson (e.g., a tiered ELD layer with\n   WIDA-banded sentence supports; IEP-goal-specific scaffolds for a named goal area; a fourth\n   intervention tier below the prerequisite; tightening scope to the exit ticket only). The\n   subject reference's FA follow-up prompt must be one of them.\n3. **The satisfaction ask.** Ask whether the teacher is satisfied with **all four artifacts**\n   or wants changes. Do not skip the ask — on every output turn, including revisions.\n\n### 5d. Revisions — one change, every document stays in sync\n\nRe-read `references\u002Foutput.md` before any revision turn. Make **targeted edits to\n`differentiation.json` first**: shared content is edited in `shared`, once, and every document that\npulls it follows identically. Then re-read every document and fix every sentence that still mentions\nthe old context, names, or numbers — stale prose is the most common consistency failure. A change\naimed at one tier goes in that tier document's blocks, never by forking shared content, and keeps\nthe subject file's R4 rules and R7 fade pattern. Then carry it into the documents the way your\npath's file says (Docs and canvas: only the parts and pages whose content changed; Word: re-render).\n\n## Step 6 — Complete\n\nThe skill is complete when the teacher has confirmed they are satisfied with all four documents\n(5c).\n","# K-12 Lesson Differentiation\n\nPaths here (`references\u002F…`, `rendering\u002F…`) are relative to this SKILL.md's folder; use absolute\npaths.\n\nAdapts an existing K-12 lesson for below \u002F at \u002F above grade-level proficiency using\nresearch-based differentiation principles (Tomlinson framework + subject-specific access\ndesign). Works with or without the Learning Commons Knowledge Graph connector.\n\n\"The teacher\" throughout this skill is the user you are talking with — the same person, never\na third party. \"Teacher-facing\" names a document's audience: that user, as opposed to their\nstudents.\n\n---\n\n## Keeping the teacher posted\n\nOnce the teacher's path is set (the draft offer answered), say in one or two sentences\nwhat you're about to do (e.g. *\"I'll read your lesson, ground it in the standard and\ncurriculum materials, design the three tiers, and build the worksheets.\"*).\n\nWhen a task-list or to-do tool is available, also outline this skill's steps there so the\nteacher can watch them check off; the only reason to skip this is that no such tool exists\nin this conversation.\n\nThe teacher reads every line you write, the ones beside tool calls included. Between tool calls say\nnothing, or speak in teacher language: name what the teacher is getting — the differentiation plan\nand the three tier documents — never tool names, file names, \"JSON\", \"artboards\" or \"rendering\". Say\n\"Word document\" only on the Word path; otherwise \"your documents\" or \"pages\". The same goes for\nerrors: say the documents couldn't be made, not that a script or JSON failed.\n\n---\n\n## Step 0 — Route (silent, before anything else)\n\n1. **Subject.** Detect math \u002F ELA \u002F science \u002F social studies from the source lesson or the\n   request, then read the matching reference file NOW:\n\n   - math → `references\u002Fmath.md`\n   - ELA → `references\u002Fela.md`\n   - science → `references\u002Fscience.md`\n   - social studies → `references\u002Fsocial_studies.md`\n\n   **Loading the matching reference file is mandatory.** It carries the pedagogy for Steps 1\n   and 3 (source-lesson identification, curriculum detection, the eight differentiation rules\n   R1–R8, the document content templates, and the differentiation.json mapping).\n2. **Curriculum.** The subject file's \"Identify the source lesson\" section includes curriculum\n   detection (Illustrative Mathematics \u002F OpenSciEd). When confirmed, use that\n   curriculum's discourse language and structures in the teacher plan, per the subject file.\n\n   **Curriculum is confirmed when:** the teacher explicitly names it, OR the uploaded source\n   lesson references it (the upload is implicit confirmation).\n\n   **If curriculum is NOT confirmed** (not detectable from upload or link, no explicit mention):\n   never name a specific module, unit number, lesson number, or proprietary routine name anywhere\n   in the output OR in any chat message — even if you recognize the routine from training.\n   Describe the instructional move in your own generic terms (\"a compare-strategies\n   discussion\", not the routine's trademarked name). This is a hard rule; violating it fails P9,\n   and chat messages count. See **Copyright guardrail** (after Step 3) for the companion rule on\n   verbatim reproduction.\n3. **Connector.** Check whether the Learning Commons Knowledge Graph tools (e.g.\n   `find_standard_statement`) are available in this conversation. This decides which path\n   Step 2 takes. The skill is fully functional without the connector.\n\n4. **State.** Before any KG call, scan the conversation and any uploaded source lesson for\nstate signals and store as `state`:\n   - Teacher says \"I teach in [state],\" \"I'm in [state],\" or \"We're in [state]\"\n   - Standard codes follow a state-specific format (TEKS, SOL, OAS\u002FPASS, MA, CA\u002FHSS or\n     CA\u002FCCSS; other state-prefixed codes → check state)\n   - Source lesson URL includes a state agency domain (tea.texas.gov, etc.)\n\n   If state found: store `state = [state name]`. Pass as `jurisdiction=\"\u003Cstate>\"` in every\n   `find_standard_statement` call in Step 2. Use state framework codes (not national proxies)\n   in all output.\n\n   If state not found:\n   - for science, math, or ELA, proceed with national defaults (CCSS for math\u002FELA, NGSS for science). Add this single footer line to the teacher plan:\n   *\"Standards applied using [CCSS \u002F NGSS] — if you're in Texas, Virginia,\n   Oklahoma, or another state with a distinct framework, share your state and I'll re-anchor.\"*\n   - for social studies, ask the teacher what state they teach in before proceeding.\n\n---\n\n## Step 1 — Identify the source lesson\n\nFollow the subject file's source-lesson section: Scenario A (lesson exists earlier in this\nconversation — use it directly, do not re-ask), Scenario B (teacher uploads a lesson — read it\nfirst; if unreadable, say so and ask to re-share, never silently fabricate), Scenario B2\n(teacher links a lesson by URL — fetch and read it; if the fetch fails,\nask them to paste or upload), Scenario B3 (math or science only — teacher names a curriculum lesson by position or title —\ne.g. \"IM Grade 6, Unit 2, Lesson 3\" or \"the OpenSciEd lesson on ecosystem dynamics\" — Step 1\nis complete; proceed directly to Step 2 where `find_curriculum_lessons` will retrieve the\nlesson materials; do NOT ask the teacher to upload or link the lesson), or Scenario C (no source lesson present —\nask the subject file's clarifying question before proceeding).\n\nA fetched link lands in the conversation whole, so a document bigger than one lesson\n(a module or unit teacher edition) will not fit. When a link points at one, work from\nwhat the request itself tells you about the lesson and confirm the specifics with the\nteacher — topic, grade, and standard carry enough to build from, the same way Scenario C\nproceeds after its clarify.\n\n**Learner needs check (silent, runs every time):** Before generating, scan the conversation\nfor any mention of ELL levels, WIDA levels, IEP goal areas, 504 accommodations, or specific\nstudent needs. If found, incorporate into the tier design — especially the Below tier.\nSay \"home language,\" not a specific language, unless the teacher names one.\n\nIf no learner needs are mentioned AND the pre-generation R8 ask hasn't fired (scope was already\nspecified), add one sentence to the FIRST response: \"No specific learner needs were provided —\nI've applied UDL defaults (sentence supports and vocabulary across all tiers). Share any ELL\nlevels, IEP goals, or specific student data and I'll adjust.\"\n\nThis check runs even when scope is already specified.\n\n\n---\n\n## Step 2 — Ground in standards\n\n**If the LC Knowledge Graph is connected:** follow the subject's section in\n`references\u002Flearning-commons-kg.md` — call BEFORE drafting; not calling when connected is a\ncritical failure, no matter how the source lesson was obtained — retrieving\nthe lesson never satisfies this step.\n\n**If not connected:** proceed from best knowledge and add this footer to the teacher plan:\n*\"Generated without the Learning Commons KG. Standard text, prerequisite grounding, and\nmisconceptions reflect general best practice.\"* Do not invent KG citations.\n\n---\n\n## Step 3 — The differentiation rules\n\nApply **all eight rules (R1–R8)** from the subject file to every differentiated lesson. The\nrules are subject-specific (scaffold types, tier entry points, extension quality tests differ\nby subject) but their structure is shared: output structure (R1), standard scope preservation\n(R2), tier entry points (R3), below-level scaffolds with a density cap (R4), required\npedagogical infrastructure (R5), invisible modifications (R6), within-level progressive\nscaffolding (R7), and scope\u002Fdefaults (R8).\n\n---\n\n## Copyright guardrail\n\nAlways write original content. When the source lesson draws from a named curriculum (IM,\nOpenSciEd), use it to understand structure, scope, task context, and standards\nalignment only — never reproduce student-facing text, activity narratives, investigation\nprompts, comprehension questions, or problem contexts verbatim from curriculum materials.\nEach subject reference file carries a **Copyright** line with subject-specific details.\n\nIf curriculum is NOT confirmed (see Step 0.2 detection rules), never name a specific\ncurriculum, module, unit number, lesson number, or proprietary routine name anywhere in the\noutput or in any chat message — even if recognizable from training. The source lesson and\nKG data inform the design without being cited. See Step 0.2 for the full rule (P9).\n\n---\n\n## Step 4 — The draft offer\n\nThe teacher gets the choice of a fast draft before the build. The offer rides with\nwhatever you ask before Step 2 (state, source lesson, learner needs — structured question\ntool when available, chat otherwise) as its own separate question, and is asked on its\nown when nothing else needs asking. Its two sides are always the set and the draft. The\nwording below lives in the question itself:\n\n- Question: *Should I build a full classroom-ready set (teacher plan + three tier documents, as\n  editable, printable documents), or do you want to see a quick draft first?*\n- Options: **Go ahead and build it** · **Quick draft first** — what changes for each\n  tier, right here in chat\n\n**The full set is the default.** A reply that selects the draft option or asks to see\nthe draft gets the draft; every other reply runs Steps 2–3 and goes straight to Step 5.\n\n**The draft (on a yes) is built on Steps 2–3, never instead of them.** Run Step 2 in full — every KG\ncall, exactly as written — and Step 3 before sketching anything. A draft sketched without the Step 2\ngrounding is a critical failure. Then present the design in chat — the draft is chat text only; the\ndocuments are made at Step 5 once the teacher approves. Show:\n\n- one line reading back the source lesson, standard, and grade;\n- for each tier (below \u002F at \u002F above), 2–3 bullets on what changes and why;\n- the student work at a glance — each tier's actual tasks, enough for the teacher to\n  skim and judge coverage;\n- one line on what every tier shares — the essential question or core task — and the\n  regroup rule\n\nThe draft borrows its names from the documents it previews — phases, tasks, tiers,\nand sections are called what the plan will call them.\n\nAfterwards, ask what's next in plain chat — a typed reply can carry the changes themselves, which a\npicked option cannot: *\"Want anything different? Tell me here — or tell me to go ahead and I'll\ncreate the materials (teacher plan and the three tier documents, as editable, printable\ndocuments).\"*\n\nApply change requests to the draft in chat and re-present it — changes are quick at this\nstage. Step 5 runs in the turn the teacher gives the go-ahead.\n\n---\n\n## Step 5 — Output (one turn)\n\nRuns immediately when the teacher chose the full set, or in the turn the draft is\napproved.\n\n### 5a. Read references and make the common JSON\n\n1. Read `references\u002Foutput.md` in full first: the hard requirements for every document's content.\n2. Then read `references\u002Fdifferentiation-json.md` and write ONE complete **`differentiation.json`**,\n   the set's common baseline. Every path makes its documents from it; it fixes WHAT each document\n   carries, not how a page looks.\n\n### 5b. Make every document — same turn\n\nCheck whether your artifact tool can create an artifact from a published type; if it can, look at\nits type list. Take the first row that applies and read its file:\n\n| What you have | Read |\n|---|---|\n| **Design** is in the type list | `rendering\u002Fclaude-artifact.md` |\n| Design isn't listed, or there is no such tool | `rendering\u002Fdocx.md` |\n\nIf making the documents fails entirely, say so — don't silently fall back to chat.\n\n### 5c. The close (every output turn)\n\nThe chat message that delivers artifacts ends with three things, in order. Each must appear in\nthe chat message itself — saying it only inside the printed plan does not count. When the\nmessage mentions the sheets, use their group names with the association noted once\n(Group A = below grade level, etc.).\n\n1. **Learner-variability statement (first output turn, when you didn't ask).** If you never\n   asked about specific learner needs in this conversation (the R8 question), state in chat\n   that UDL defaults were applied and invite specifics — e.g. *\"I didn't have details on\n   specific learner needs, so I applied UDL defaults — sentence stems and a vocabulary\n   glossary on all three tier sheets. Tell me about any multilingual learners or students\n   with IEPs or 504 plans and I'll tailor further.\"* Skip this only when the teacher already\n   gave learner information (then reflect it instead: \"the Below sheet builds in the sentence\n   frames for your newcomer ELLs\").\n2. **Three lesson-specific next steps (first output turn).** Offer 3–4 iteration options in\n   chat, one short line each, specific to THIS lesson (e.g., a tiered ELD layer with\n   WIDA-banded sentence supports; IEP-goal-specific scaffolds for a named goal area; a fourth\n   intervention tier below the prerequisite; tightening scope to the exit ticket only). The\n   subject reference's FA follow-up prompt must be one of them.\n3. **The satisfaction ask.** Ask whether the teacher is satisfied with **all four artifacts**\n   or wants changes. Do not skip the ask — on every output turn, including revisions.\n\n### 5d. Revisions — one change, every document stays in sync\n\nRe-read `references\u002Foutput.md` before any revision turn. Make **targeted edits to\n`differentiation.json` first**: shared content is edited in `shared`, once, and every document that\npulls it follows identically. Then re-read every document and fix every sentence that still mentions\nthe old context, names, or numbers — stale prose is the most common consistency failure. A change\naimed at one tier goes in that tier document's blocks, never by forking shared content, and keeps\nthe subject file's R4 rules and R7 fade pattern. Then carry it into the documents the way your\npath's file says (Docs and canvas: only the parts and pages whose content changed; Word: re-render).\n\n## Step 6 — Complete\n\nThe skill is complete when the teacher has confirmed they are satisfied with all four documents\n(5c).\n",{"name":5,"license":50,"description":7},"Copyright 2026 Anthropic, PBC · Copyright 2026 Learning Commons · SPDX-License-Identifier: Apache-2.0. Complete terms in LICENSE and NOTICE.","main","31fd6dbb0c07cb50bb3ce7f62a4135a393bd0e8c","plugin\u002Fskills\u002Fk12-lesson-differentiation",113,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-10-14 08:54:44",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add anthropics\u002Fk12-teacher-skills --skill k12-lesson-differentiation",{"tool":65,"command":66},"bunx","bunx skills add anthropics\u002Fk12-teacher-skills --skill k12-lesson-differentiation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add anthropics\u002Fk12-teacher-skills --skill k12-lesson-differentiation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002FSKILL.md",true,[73,77,83,87,91,95,99,103,107,111,115,119,123,129,133,137,141,145],{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11357,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fdifferentiation-json.md","REFERENCE","参考文档",11747,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fdifferentiation-json.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fela.md",26744,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fela.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fexample_differentiation.json",15460,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fexample_differentiation.json",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Flearning-commons-kg.md",12867,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Flearning-commons-kg.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fmath.md",20400,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fmath.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002FNOTICE",294,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002FNOTICE",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Foutput.md",6922,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Foutput.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fscience.md",23796,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fscience.md",{"path":112,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fsocial_studies.md",22979,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Freferences\u002Fsocial_studies.md",{"path":116,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":117,"sourceHtmlUrl":118},"rendering\u002Fclaude-artifact.md",9764,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Frendering\u002Fclaude-artifact.md",{"path":120,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":121,"sourceHtmlUrl":122},"rendering\u002Fdocx.md",2032,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Frendering\u002Fdocx.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Flesson_common.py","SCRIPT","脚本",33326,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Flesson_common.py",{"path":130,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Frender_all.sh",2132,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Frender_all.sh",{"path":134,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":135,"sourceHtmlUrl":136},"scripts\u002Frender_documents.py",4677,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Frender_documents.py",{"path":138,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":139,"sourceHtmlUrl":140},"scripts\u002Frender_lesson_docx.py",25982,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Frender_lesson_docx.py",{"path":142,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":143,"sourceHtmlUrl":144},"scripts\u002Frender_lesson_html.py",17148,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Frender_lesson_html.py",{"path":146,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":147,"sourceHtmlUrl":148},"scripts\u002Ftheme.css",5293,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-differentiation\u002Fscripts\u002Ftheme.css",[150,174,191],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":45},"01M718HPHTBBS2FWA0N99HJAJV","k12-lesson-prep","Helps a teacher prepare to teach an existing K-12 lesson (math \u002F ELA \u002F science \u002F 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?\").","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-prep\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-prep\u002FSKILL.md",[157],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[159,160,27,32,38,161,162,163,164,165,166,167,37,168,44,169,170,171,172,173],"k12 lesson prep","prep","which","feedback","get","for","answer","short","long","triggers","science","single","material","only","Existing",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":45},"01M718HFVVF7J9XNRSTC2Q9ST8","k12-lesson-plan-creation","Creates a lesson plan, student-facing materials, and observation template. Load this skill BEFORE asking the teacher any clarifying question about grade, subject, topic, standard, or timing. Use when a K-12 teacher needs a math, ELA, science, or social studies lesson built from scratch — even if grade, subject, or topic isn't yet stated. Do NOT load for grading, a rubric, assessment feedback, a quiz, or a standards lookup — answer those directly. Triggers on explicit requests (lesson plan, mini-lesson, unit plan, daily plan) and implicit teacher intent: \"I'm teaching long division to 5th graders,\" \"need to teach photosynthesis tomorrow.\" Core signal: teacher needs new instructional content created. A new lesson that asks for differentiated, tiered, or leveled materials is still ONE planning request — this skill produces those materials inside the lesson package; do not also invoke k12-lesson-differentiation. Not for differentiating an existing lesson (use k12-lesson-differentiation) or passage rewrites.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-plan-creation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-lesson-plan-creation\u002FSKILL.md",[181],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[27,33,183,41,184,185,186,40,31,26,32,187,188,189,37,44,29,39,190,30],"lesson plan","plan creation","k12 lesson plan creation","intent","teaching","unit","daily plan","invoke",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":45},"01M718H2EGRYX63MKHBXQFVER3","k12-check-for-understanding","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).","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-check-for-understanding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fk12-teacher-skills\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fk12-check-for-understanding\u002FSKILL.md",[198],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[200,164,201,26,202,203,27,204,161,33,205,206,207,39,208,32,31,209,41,40],"check","k12 check for understanding","SET","bare","quick","move","ticket","design","you","create"]