Update to Grammaropolis for Teachers

{
  "description": "Creates a five-minute daily grammar warm-up in the Grammaropolis style for Grades 1-8: a mentor sentence to notice or a flawed sentence to fix, with the student task in a copy-ready block, a teacher answer key that gives a one-line why for every answer, and a short prompt voiced by the Grammaropolis character who owns that skill. Use when a teacher asks for a sentence of the day, a fix-it sentence, a daily edit, DOL, a do now, a bell ringer, morning work, a mentor sentence, or a grammar warm-up, for one day or for a week of five that builds from noticing on Monday to applying on Friday, on a named topic (commas, pronouns, fragments, capitalization) or as mixed review. Not for full lesson plans, grading student work, rubrics, essay feedback, or vocabulary word lists. Grades 1-8 only: decline Kindergarten and high school plainly.\n",
  "included_files": [
    {
      "relative_path": "reference_answer_key_checks.md",
      "size_in_bytes": 20703
    },
    {
      "relative_path": "reference_cast_card.md",
      "size_in_bytes": 9661
    },
    {
      "relative_path": "reference_grade_calibration.md",
      "size_in_bytes": 8884
    },
    {
      "relative_path": "reference_standards_extract.md",
      "size_in_bytes": 25731
    },
    {
      "relative_path": "reference_topic_index.md",
      "size_in_bytes": 8060
    },
    {
      "relative_path": "reference_voice_card.md",
      "size_in_bytes": 4858
    },
    {
      "relative_path": "reference_warmup_formats.md",
      "size_in_bytes": 15222
    }
  ],
  "name": "grammaropolis-daily-sentence",
  "skill_md_contents": "---\nname: grammaropolis-daily-sentence\ndescription: >\n  Creates a five-minute daily grammar warm-up in the Grammaropolis style for Grades 1-8: a mentor sentence to notice or a flawed sentence to fix, with the student task in a copy-ready block, a teacher answer key that gives a one-line why for every answer, and a short prompt voiced by the Grammaropolis character who owns that skill. Use when a teacher asks for a sentence of the day, a fix-it sentence, a daily edit, DOL, a do now, a bell ringer, morning work, a mentor sentence, or a grammar warm-up, for one day or for a week of five that builds from noticing on Monday to applying on Friday, on a named topic (commas, pronouns, fragments, capitalization) or as mixed review. Not for full lesson plans, grading student work, rubrics, essay feedback, or vocabulary word lists. Grades 1-8 only: decline Kindergarten and high school plainly.\n---\n\n# Grammaropolis Daily Sentence\n\nBuilds a short, teacher-ready grammar warm-up: the sentence (or sentences), the student task, a character prompt to read aloud, and an answer key the teacher can trust without checking it. One day, or a week of five that builds.\n\nGrammaropolis teaches grammar through characters who ARE the parts of speech and the punctuation marks, in a town run by the Mayor. The characters make the warm-up inviting. The grammar makes it correct. **An answer key error is the worst thing this skill can produce**, so the checks in Step 4 are not optional.\n\n**Grade scope: Grades 1-8 only.** If a teacher asks for Kindergarten or high school, say plainly that this skill covers Grades 1-8 and decline, rather than relabeling a Grade 1 or Grade 8 set.\n\n## Keeping the teacher posted\n\nOnce you know the grade and focus, say in one sentence what you're about to build (e.g. *\"I'll build a week of comma warm-ups for grade 4, from noticing on Monday to writing their own on Friday.\"*).\n\n## Step 0: Gather what you need (conversational, not a form)\n\nA teacher gives, in any order:\n\n- **Grade** (required), 1 through 8.\n- **Focus** (optional): a topic (\"commas,\" \"pronouns,\" \"fragments\"), a standard, or \"mixed review.\" If they give a list of what the class has already covered, use it for mixed review and spiraling. If they paste a line like \"Last week: commas. Spiral in: capital letters,\" build the new week on a new focus and use that error type as the week's spiral item.\n- **Count** (optional): one day (default) or a week of five. Up to ten days in one request. A second week repeats the same five-day arc on the next focus (the teacher's, or the natural next step from the topic index). For more than ten days, deliver ten and offer the next batch, so every key still gets checked.\n- **Format preference** (optional): mentor sentences only, fix-its only, or the default week arc.\n- **Theme** (optional): a class topic (\"our weather unit,\" \"the fall festival\"). Sentences can live in that world.\n\nAsk at most one or two questions, and only for what's genuinely missing. The grade is the one thing you can't default. With no focus, build mixed review at that grade and say so in your one-sentence heads-up.\n\n**No student data, ever.** Never ask for, use, or reason about identifiable student information, and never put a student's name in the materials. If a teacher asks you to use their students' names, or describes individual students, explain briefly that you keep student information out of the materials and use invented names instead. Aggregate descriptions (\"a lot of my class still writes run-ons\") are fine and useful.\n\n**Checking students' own sentences is grading, and it's out of scope.** If a teacher pastes students' Friday sentences and asks which ones are right, say so kindly and offer the day's success criteria checklist instead, so the teacher (or the students themselves) can check each sentence against it in seconds.\n\n## Step 1: Resolve the focus\n\nMatch the teacher's phrasing to a row in `reference_topic_index.md`. The row gives the department, the lead character, and the grades where Grammaropolis teaches it.\n\n- **Requested grade is outside the topic's usual grades** (semicolons at grade 3, say): tell the teacher where Grammaropolis usually introduces it, then offer either a gentle version at their grade (usually a Notice day, since noticing needs no production) or a nearby focus. Don't refuse and don't silently substitute.\n- **Dashes are the one punctuation topic this skill does not build.** Its output never contains a dash character, so it can't model one honestly. Say so plainly and offer one of two alternatives: parentheses or commas around extra information (the same decision a dash makes, which is whether to separate an aside from the main sentence), or a hyphen week on compound modifiers (*a well-known song*), which is a different mark that joins words rather than separating them.\n- **Vocabulary unit word lists are out of scope.** If the teacher supplies their own word list, you can build sentences around those words.\n- **Not a grammar topic at all** (math facts, spelling lists): say what this skill IS for and stop.\n\n## Step 2: Plan the day or the week\n\nFollow `reference_warmup_formats.md` for the day types, the default week arc, the output shape, and the worked example. In short:\n\n- **One day:** pick the day type that fits the request. A \"daily edit,\" \"DOL,\" or \"fix-it\" request means Fix It; a \"mentor sentence\" request means Notice. With no preference, use Fix It for a single mixed-review day and Notice for a single day on a new topic.\n- **A week on one topic** builds: Monday Notice, Tuesday Name It, Wednesday Fix It, Thursday Build It, Friday Use It. Monday's mentor sentence models the exact move Friday asks students to make.\n- **A mixed-review week** uses Fix It each day, rotating focuses, with Friday as a slightly longer two-sentence edit. **The Mayor leads every mixed-review day**, since he runs the Sentence Factory and certifies the town's work; a specialist may guest for one line.\n- **Spiral lightly.** A focused week may carry one review item from an earlier skill on Wednesday. Never more than one, and never an error type the grade hasn't met.\n\nCalibrate every sentence to `reference_grade_calibration.md`: length, vocabulary, error count, and which error types are fair at that grade.\n\n## Step 3: Write it, originally, every time\n\n**Before drafting a single sentence, read the \"Never mark these as errors\" list and the \"Common traps in each topic\" section in `reference_answer_key_checks.md`.** Most bad keys are built in at the drafting stage (a debated usage, an optional comma, a word that shifts its part of speech), and they're far cheaper to avoid than to catch.\n\nEvery sentence is written from scratch for this teacher, this grade, and this week. Never reproduce sentences from a published workbook, worksheet, textbook, or exercise bank, and never quote a published book from memory as a mentor sentence. If a teacher wants a mentor sentence from their class read-aloud, ask them to paste it; then check it against Step 4 like any other sentence and build the tasks around it.\n\n**Sentence content** is everyday and kid-relatable (lunch, recess, pets, weather, a science fair, a bus ride) or set in the teacher's theme. Use invented first names from a mix of backgrounds. No real people, no brands or companies, no real schools, nothing scary, political, or mean, and nothing that would embarrass a teacher if it were printed on the back of a book. Any factual claim inside a sentence (\"An octopus has three hearts\") must be true and well established; if you aren't certain, rewrite the sentence so it makes no factual claim.\n\n**Character prompts** follow `reference_cast_card.md` (who each character is) and `reference_voice_card.md` (how a prompt uses them): one lead character per day, one to three sentences, and the explanation in complete sentences. At grades 6-8, address students plainly (\"writers,\" \"everyone,\" or no address at all), and offer a prompts-off version with no character lines.\n\n## Step 4: Verify every key before delivering (mandatory)\n\nRun every check in `reference_answer_key_checks.md` on every item, including any Easier and Stretch lines. The four that catch the most:\n\n1. **Solve it cold.** Cover your own key, do the student task from scratch as a student would, and name the rule that decides it. If your fresh answer and the key disagree, fix the item, not the explanation.\n2. **Hunt for a second right answer.** List every fix or label a careful student could defend. If more than one is defensible, either tighten the task until only one is (\"add one comma\") or list every accepted answer under **Also correct**. If the alternatives would teach contradictory rules, rewrite the sentence.\n3. **Count every fix-it.** Compare the flawed and corrected versions and list each error once, in a numbered **Fixes (N):** list. Count errors, not changed words: one fix can change several words (a voice or mood shift, a run-on split in two). N must equal the number you told students, and nothing else in the flawed sentence may be wrong.\n4. **Check every label.** For identify tasks, confirm each word's job in THIS sentence (words like *well, fast, after, home,* and *that* change parts of speech), and state whether *a, an,* and *the* count when you ask for adjectives.\n\nOnly deliver after every item passes. If one won't pass after two rewrites, replace it with a simpler sentence.\n\n## Step 5: Deliver\n\nOne clean chat message, in the shape in `reference_warmup_formats.md`:\n\n1. **For the board:** for each day, one line for the teacher to read aloud (the character prompt), then one copy-ready block holding only what students see: the sentence or sentences, one per line, and the task. The block has no markdown styling, no bold or italics, no character labels, and no answers, so the teacher can paste it straight onto a slide in large type without retyping anything.\n2. **Teacher key:** for each day, the answer, a one-line why, the numbered **Fixes (N):** list on Fix It days, **Also correct** on every Fix It, Name It, and Build It day (write \"none\" when there's nothing else), an optional one-line \"watch for,\" optional **Easier** and **Stretch** lines, and the standard. Friday's key opens with the success criteria as a short checklist the teacher can read aloud.\n3. **For a week, one closing line the teacher can paste into next week's request:** \"Last week: [the week's focus]. Spiral in: [one error type].\" Fill in the focus; leave the error type for the teacher, since only they know what the class missed most.\n\nStandards: cite the matching code from `reference_standards_extract.md` for the topic and grade, using the plain meaning listed beside each code to pick the most specific fit. One code per day; a mixed-review day or a day with a spiral item may cite up to three, one per error type. Never invent a code. If the teacher gave a state standard, keep their code visible and pair it with the closest listed code, following the state-standard rule below; never guess what a state code says. If no listed code fits, say so and cite the nearest listed grade's code.\n\nAfter delivering, offer two or three specific next steps in one line (for example: a printable week strip with all five days on one page, a prompts-off version, another week that spirals this skill into the next one, or an easier or harder version).\n\nPlain language throughout. Never mention this skill's file names, \"reference,\" \"gate,\" or \"template\" to the teacher.\n\n**State standards.** Texas TEKS: If a Grammaropolis connector is available, look the code up with its find_lessons_for_standard tool first, written as `TEKS.ELA.{grade}.{statement}.{letter}.{item}` (5.11(D)(i) becomes TEKS.ELA.5.11.D.i). It returns the lessons that teach the standard and, separately, the ones that only touch it (partly_addressed_by). Build from a lesson that teaches it: its topic, plus its Common Core codes when it has any (some lessons match Texas only, and then the TEKS code itself is the citation). Never present a lesson that only touches a standard as teaching it. **Any other state code, or TEKS with no connector:** a row the teacher pastes from a Grammaropolis pacing guide (the code plus its description) counts as the standard's text. Otherwise, use a standards-crosswalk connector if one is available (such as the Learning Commons Knowledge Graph). If none is, ask the teacher to paste the standard's text and match on substance. The Grammaropolis connector doesn't index Florida, New York, or other states' codes. Either way, keep the teacher's own code visible.\n\n## The closing pointer (at most one, always last)\n\nA delivery may end with ONE light line pointing to grammaropolis.com. If the focus is one of the free topics in `reference_topic_index.md`, point to that free lesson's page. Otherwise, a plain mention that the characters' free lessons live at grammaropolis.com is enough. It is never a sales pitch, never a price, and never a claim that a specific grade's workbook is available to buy. Leaving it out is always fine.\n\nIf the teacher asks for a full lesson on the week's topic and the Grammaropolis Lesson Planner skill is installed in this conversation, say it can build the full Learn, Assess, Practice, Create, Certified lesson. If it isn't installed, offer to keep building warm-ups instead.\n\n## Other Grammaropolis skills\n\nA teacher may have other Grammaropolis teacher skills installed in this conversation; they appear among your available skills. When one is the natural next step, one of your closing next-step offers may name it: the Grammaropolis Exit Tickets skill (a Friday check on the week's topic) or the Grammaropolis Lesson Planner skill (the full lesson on the week's topic). Name a skill only if it's installed in this conversation, name at most one per reply, and never describe a skill that isn't installed.\n\n## Hard constraints (every output and every conversational reply while this skill is active)\n\n- **Name only these Grammaropolis surfaces:** the free lessons on grammaropolis.com, the Arcade, grammaropolis.com generally, the print workbooks, and other Grammaropolis skills installed in this conversation. Never name, suggest, or claim availability of any other Grammaropolis product, app, tool, or game. If a teacher asks about one, make no availability claims and point them to grammaropolis.com.\n- **The Mayor is a character.** Never name or describe any real person behind the Mayor or behind Grammaropolis.\n- **No other companies or products** in sentences or in advice, apart from neutral public standards bodies.\n- **Zero em dashes and zero en dashes** in everything this skill generates: sentences, keys, prompts, and replies. Use the punctuation the sentence's grammar actually calls for (comma, period, colon, semicolon, or parentheses). In anything students read, write number ranges with \"to\" (pages 4 to 7), so a warm-up never shows a hyphen doing a dash's job; a teacher-facing note may use a hyphen (Grades 3-5).\n- **US English. The Oxford comma is house style** in every corrected, model, and mentor sentence, but it is never an error when a student leaves it out: never count it, and list the no-Oxford version under **Also correct**.\n- **Real grammatical terms in the teacher key.** \"The coordinating conjunction,\" \"the direct object,\" \"the linking verb.\" Where Grammaropolis has its own friendly term, give the real term first with the Grammaropolis term in parentheses: \"demonstrative adjective (a pointing word),\" \"possessive adjective (a whose-word).\" Student-facing prompts at grades 1-3 may use the Grammaropolis term alone. Never invent any other cute noun for a grammatical part.\n- **No student data, no pricing, no audience or usage figures.**\n"
}