Install
$ agentstack add skill-skillmedev-educators-toolkit-differentiated-instruction ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Differentiated Instruction
Differentiation is not creating separate lessons for every student. It is designing one lesson with intentional entry points, flexible pathways, and multiple ways to demonstrate mastery - same objective for all, different paths to it. The costly failure it prevents is quiet tracking: struggling students fed only low-complexity work are being denied grade-level learning while the paperwork says they were "supported."
Operating procedure
Step 1: Gather inputs
Collect before modifying anything; label unknowns as guesses to verify with a formative check:
- The original lesson or unit, its learning objective, and the core task as written.
- The readiness spread, from recent formative assessment data - not historical placement or last year's labels. If no data newer than three weeks exists, run a short formative probe first; differentiating on stale data re-creates the ability groups it is supposed to replace.
- Known learning needs (IEP/504 accommodations, language support) and rough group sizes per readiness band.
- What the teacher can actually manage: number of simultaneous versions, para/aide availability, time to prepare.
Step 2: Protect the core task
Identify the core task every student will do, at the full learning objective. This is the anchor; everything else is scaffold or extension. If a proposed modification changes what is being learned rather than how it is accessed, reject it - that is dilution, not differentiation.
Step 3: Choose the differentiation type - readiness first
- Readiness differentiation adjusts complexity: vocabulary support, sentence frames, worked examples, or reduced problem sets for students who need more time; added constraints, abstraction, or cross-disciplinary connections for students ready for more. Default here first - it has the highest instructional return.
- Interest differentiation offers choice of topic or application context while holding the skill constant. Use it to buy engagement once readiness is handled.
- Learning profile differentiation varies representation and response mode: visual organizers, oral response, physical manipulation. Use it as a layer, not the primary strategy.
Step 4: Build three tiers
Tiered assignments address the same essential concept at different complexity. Design exactly three: approaching grade level, at grade level, above grade level. Each tier shares the essential question and varies only text complexity, number of steps, degree of abstraction, or amount of scaffolding.
If/then rules for tier design:
- If a tier requires a different essential question, it is a different lesson - redesign.
- If the "above" tier is just more problems, it is punishment, not extension - add abstraction or constraints instead.
- If the "approaching" tier removes the cognitively demanding part, it strips the objective - scaffold the demand, do not delete it.
Never present tiers to students as ranked; frame them as different versions, not easy and hard.
Step 5: Plan flexible grouping
- Group by readiness for skill-specific instruction; use mixed-readiness groups for collaborative problem-solving and discussion.
- Never use permanent ability groups. Regroup on formative data every two to three weeks at most.
- Ensure every student experiences both peer-teaching and peer-learning roles across the year.
Step 6: Attach a fade plan to every scaffold
Scaffolds are temporary by design. For each support (sentence frames, graphic organizers, worked examples), write two lines: the removal signal (what student evidence shows readiness - e.g., two consecutive independent successes) and the removal step (frame → word bank → nothing). A support with no fade plan is a crutch; if a scaffold is still in place after six weeks with no fade progress, escalate it as an intervention question rather than leaving it as a permanent fixture.
Worked artifact: one task, three tiers
Objective: analyze how an author uses evidence to support a claim (grade-level informational text).
| Tier | Text & task | Scaffold / extension | Fade signal |
|------|-------------|----------------------|-------------|
| Approaching | Same article, chunked into 3 sections with margin questions. Identify the claim and 2 pieces of evidence; explain one using a sentence frame: "The author supports ___ by ___, which matters because ___." | Frames + pre-taught vocabulary (5 terms) | Frame removed after 2 independent successes; word bank stays one more cycle |
| At grade level | Full article. Identify claim and 3 pieces of evidence; rank them by strength and justify the ranking in a paragraph. | Annotation checklist only | Checklist optional next unit |
| Above | Full article + a second article with a competing claim. Evaluate which author argues better and write a rebuttal paragraph to the weaker one. | None; constraint added (rebuttal must concede one valid point) | n/a - extension, not scaffold |
Every tier analyzes evidence (the objective is intact); only chunking, scaffolds, and abstraction vary.
Deliverable
Produce a differentiation plan as annotated additions to the original lesson: each modification labeled with type (readiness/interest/profile), target group, and strategy; the three-tier task table; the grouping plan with its regrouping trigger; and a fade plan per scaffold. Include a one-row-per-modification summary table for quick reference during the lesson, written in plain descriptors a substitute or paraprofessional can follow without jargon.
Do NOT
- Do not lower the objective for struggling learners - scaffold access to grade-level work; dilution is denial of learning.
- Do not build tiers that are visibly ranked or labeled easy/hard - students decode labels instantly and internalize them.
- Do not group on historical placement - use formative data less than three weeks old, and regroup on it.
- Do not create supports without fade plans - a permanent scaffold is a crutch that caps independence.
- Do not make "more problems" the extension - volume is not rigor; add abstraction or constraints.
- Do not differentiate every element of every lesson - pick the modifications the teacher can actually run; an unmanageable plan differentiates nothing.
Quality bar
- The core task and objective are identical across tiers; only access and depth vary.
- Exactly three tiers, sharing one essential question, framed as versions rather than levels.
- Every modification is labeled (type, target group, strategy) and readable by a paraprofessional.
- Every scaffold has a removal signal and removal step; grouping has a regrouping cadence of two to three weeks tied to formative data.
- The plan fits the teacher's stated capacity - no more simultaneous versions than they can manage.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: SkillMedev
- Source: SkillMedev/educators-toolkit
- License: MIT
- Homepage: https://skillme.dev/pack/educators-toolkit
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.