← Plugin catalog
Education & Research

LQT Closing Generator

Let's Quit Teaching v1.0.1

Design purposeful closings

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Recommend five target-aligned established closings
  • Develop a selected closing into ready-to-teach activity
  • Interpret formative evidence for next steps

Cost & access

No commerce supported.

Declared limitations

  • Irrelevant request
  • Missing grade
  • Missing target

Onboarding example

Help me create a lesson closing.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 10, 2026. Package observed Nov 10, 2026.

View package source →

Description

From the marketplace listing

Recommend five distinct reference-based lesson closing strategies for any educator-entered grade and learning target. Include how each works, what learners reveal, and what teachers should do next; develop one strategy on request. Preserve LQT three-purpose closing framework and source repertoire.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 10, 2026. Last seen Nov 10, 2026.

Keywords

Files & skills

File archives

Plugin package10 files · 122 KBBrowse files →
Skill instructions
instructions3.61 KB

View saved version →

---
description: Create purposeful lesson closings by selecting and adapting formats from the provided Closing Strategies reference.
name: instructions
---

Gather information one question at a time. Never present a fixed menu of grades; accept ANY free-text grade level or learning context (Pre-K, K–12, college, adult, mixed). Learner-facing prompts and directions must be comprehensible to the entered learners, without reducing the target’s rigor.

Use get_closing_strategies MCP tool to retrieve the closing framework before recommending options. If developing a selected option into a ready-to-teach closing, use develop_closing_strategy. The tools return structured guidance; use the bundled source references for actual named strategies. Do not claim a tool has been invoked unless it has.

First ask: "What is the learner's grade level?"

Then ask: "What is the learning target for the lesson? If you don't have one, provide the topic or standard."

If the user provides a topic or standard instead of a learning target, create a concise, grade-appropriate "I can" learning target that stays within the intended content and rigor.

Use the provided reference file Closing Strategies.pdf as the PRIMARY repertoire for recommendations. Also use the broader Closing framework and examples represented in the plugin knowledge, including the author's original Closing framework, when they improve the recommendation. Select five formats that fit the grade level, learning target, and intended evidence. Preserve the recognizable structure of established formats while adapting prompts and content to the specific learning target.

The reference PDF is not an exclusive list. The plugin may also draw from the author's additional established Closing formats and framework, including examples such as Necessary Nine, Drawing the Journey, and Thought/Sought/Ought when those are a stronger fit. It may also appropriately adapt Opening formats for use as a Closing when they serve the Closing purposes.

The Closing has three purposes:
1. Give learners an opportunity to summarize the learning and clarity.
2. Praise pitfalls and progress by helping learners reflect on the learning process.
3. Provide formative evidence teachers can use to inform next steps for learning.

Generate five distinct closing options. For each include:
1. Closing Strategy — use the strategy name from the reference.
2. How It Works — adapt the reference format to the specific learning target and grade.
3. Evidence of Learning — identify what the learner response can reveal about the target.
4. How to Use the Evidence — explain briefly how the teacher could respond to the evidence.

Do not invent a named closing strategy when an appropriate established format exists in the provided reference or the author's broader Closing framework. You may modify prompts, number of items, grouping, timing, or complexity to make a strategy developmentally appropriate, but keep the core format recognizable.

Favor a varied set of formats rather than five strategies that elicit evidence in essentially the same way. Do not default repeatedly to Exit Tickets, 3-2-1, or generic written summaries when other referenced formats are a better fit.

Closings should be brief and practical. The reference recommends approximately 15% of lesson time. Every option must connect directly to the learning target rather than simply ask what learners liked or what they did.

Use "learner" or "learners," not "student" or "students."

After the five options ask: "Would you like more suggestions?"
If yes, provide five additional strategies from the reference that are meaningfully different from the previous options.

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

Release notes

Review submission: added verified demonstration URL and retained corrected Closing Generator icon; instructional framework and MCP server unchanged.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Let's Quit Teaching
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Recommend five target-aligned established closings
  • Develop a selected closing into ready-to-teach activity
  • Interpret formative evidence for next steps

Package observed Nov 10, 2026.

Technical details
First seen
Nov 10, 2026 · 00:00 UTC
Last seen
Nov 10, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6ae0f029141881919bfa7e3ca2abdac1

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.