lesson-planning
Skill1 starsChanged 7 months agoMITView on GitHub
Create detailed lesson plans with learning objectives, activities, assessments, materials, and differentiation strategies. Trigger with "create a lesson plan", "plan a lesson on", "design a class about", "teaching plan for", or when the user needs structured instructional plans for any subject, grade level, or learning environment.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- incident-responseSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Create detailed, standards-aligned lesson plans with clear learning objectives, engaging activities, formative assessments, required …
- Distinctive: line 40
Ask about class duration and available class periods.
- Distinctive: line 43
Ask about available resources: technology access, lab equipment, manipulatives.
- Distinctive: line 50
Start each objective with "Students will be able to..." (SWBAT).
- Distinctive: line 51
Use observable, measurable verbs aligned to the cognitive level:
- Distinctive: line 56
Ensure objectives are assessable within the class period.
- Distinctive: line 69
Use multiple representations: visual, verbal, kinesthetic.
- Distinctive: line 70
Check for understanding every 3-5 minutes with quick formative checks (thumbs up/down, whiteboard responses).
- Distinctive: line 151
Action: Write objectives about explaining the photosynthesis process and identifying inputs/outputs, design a hands-on lab activity with …
- Distinctive: line 157
Action: Use manipulatives (fraction tiles) for concrete understanding, provide tiered practice problems at three difficulty levels, include …
- Distinctive: line 163
Every activity must connect to a learning objective — cut anything that is fun but purposeless.
- Distinctive: line 166
Write the exit ticket before designing the lesson — it clarifies what mastery looks like.
- Distinctive: line 167
If the user teaches multiple sections, note where adjustments may be needed between periods.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lesson Planning
Create detailed, standards-aligned lesson plans with clear learning objectives, engaging activities, formative assessments, required materials, and differentiation strategies for diverse learners.
Workflow
Step 1: Define the Learning Context
Gather the instructional parameters before planning:
- Confirm the topic, subject area, and grade level.
- Ask about class duration and available class periods.
- Identify relevant standards (Common Core, NGSS, state standards) if applicable.
- Determine class size and any known student needs (ELL, IEP, gifted).
- Ask about available resources: technology access, lab equipment, manipulatives.
- Identify where this lesson falls in the unit sequence (intro, mid-unit, review).
Step 2: Write Learning Objectives
Craft measurable objectives using Bloom's Taxonomy:
- Start each objective with "Students will be able to..." (SWBAT).
- Use observable, measurable verbs aligned to the cognitive level:
- Remember/Understand: define, describe, explain, summarize.
- Apply/Analyze: solve, demonstrate, compare, categorize.
- Evaluate/Create: argue, design, construct, critique.
- Limit to 2-3 objectives per lesson for focus and achievability.
- Ensure objectives are assessable within the class period.
Step 3: Design the Lesson Structure
Build the lesson flow with time allocations:
Opening / Hook (5-10 min)
- Activating prior knowledge: KWL chart, think-pair-share, or warm-up problem.
- Engagement hook: compelling question, real-world connection, surprising fact, or brief video.
- State the learning objective in student-friendly language.
Direct Instruction (10-15 min)
- Present new content through explicit teaching, modeling, or guided discovery.
- Use multiple representations: visual, verbal, kinesthetic.
- Check for understanding every 3-5 minutes with quick formative checks (thumbs up/down, whiteboard responses).
- Limit lecture to 10 minutes max — intersperse with interaction.
Guided Practice (10-15 min)
- Students practice with teacher support: worked examples together, partner work, structured problems.
- Circulate and provide targeted feedback.
- Address common misconceptions as they surface.
Independent Practice (10-15 min)
- Students apply the skill independently or in small groups.
- Provide tiered tasks for differentiation (see Step 4).
- Monitor and note which students need reteaching.
Closing / Exit Ticket (5 min)
- Students summarize learning or answer an exit ticket question aligned to the objective.
- Preview the next lesson to build continuity.
Step 4: Plan Differentiation
Address diverse learner needs:
- Struggling learners: Provide scaffolds (graphic organizers, sentence starters, manipulatives), reduce complexity while maintaining the objective, allow extended time.
- English Language Learners: Include visual supports, word banks with definitions, partner with bilingual peers, allow native language processing.
- Advanced learners: Offer extension problems, open-ended challenges, or peer teaching roles.
- IEP/504 accommodations: Note specific modifications required (preferential seating, extended time, modified assessments).
Step 5: Prepare Assessment and Materials
Finalize assessment and logistics:
- Formative assessment: At least 2 checks during the lesson (questioning, observation, whiteboard responses) plus the exit ticket.
- Materials list: Everything needed, including quantities and preparation notes.
- Technology requirements: Devices, apps, websites, login procedures.
- Backup plan: Activity that works without technology in case of technical issues.
Output Format
# Lesson Plan: [Topic]
**Subject**: [Subject] | **Grade**: [Grade Level] | **Duration**: [Minutes] min
**Standards**: [Standard codes and descriptions]
## Learning Objectives
1. SWBAT [measurable objective 1]
2. SWBAT [measurable objective 2]
## Materials Needed
- [Material 1]
- [Material 2]
## Lesson Sequence
| Time | Phase | Activity | Notes |
|------|-------|----------|-------|
| 0-5 min | Opening | [Hook activity] | [Engagement strategy] |
| 5-20 min | Instruction | [Teaching method] | [CFU checkpoints] |
| 20-35 min | Practice | [Student activity] | [Differentiation notes] |
| 35-45 min | Independent | [Application task] | [Monitoring plan] |
| 45-50 min | Closing | [Exit ticket] | [Collection method] |
## Differentiation
- **Below grade level**: [Scaffolds and supports]
- **ELL**: [Language supports]
- **Above grade level**: [Extensions]
- **Accommodations**: [IEP/504 modifications]
## Assessment
- **Formative**: [During-lesson checks]
- **Exit ticket**: [Question aligned to objective]
- **Success criteria**: [What mastery looks like]
## Reflection (post-lesson)
- What worked well?
- What needs adjustment?
- Which students need follow-up?Examples
User: "Create a lesson plan on photosynthesis for 7th grade science" Action: Write objectives about explaining the photosynthesis process and identifying inputs/outputs, design a hands-on lab activity with leaf disc experiments, include differentiation for ELL students with labeled diagrams.
User: "Plan a 90-minute block for teaching persuasive writing to 10th graders" Action: Structure as mini-lesson on persuasive techniques, model analysis of a mentor text, guided practice writing thesis statements, independent drafting with a peer review component, exit ticket on identifying claim vs. opinion.
User: "I need a math lesson on fractions for a mixed-ability 4th grade class" Action: Use manipulatives (fraction tiles) for concrete understanding, provide tiered practice problems at three difficulty levels, include visual models for ELL students, extend with real-world fraction problems for advanced learners.
Best Practices
- Backwards-design: start with what students should know/do, then design activities to get there.
- The hook should create a genuine need-to-know, not just an attention-getter.
- Every activity must connect to a learning objective — cut anything that is fun but purposeless.
- Build in transition time between activities; plan for 80% of the class period, not 100%.
- Include at least one opportunity for every student to respond (not just hand-raisers).
- Write the exit ticket before designing the lesson — it clarifies what mastery looks like.
- If the user teaches multiple sections, note where adjustments may be needed between periods.
- Suggest a post-lesson reflection prompt so the teacher can refine the plan after delivery.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

