Worked Example to Problem Solving Transition Designer Agent Skill

Design the transition from worked examples to independent problem-solving using expertise-reversal principles.

Context cost
6.2k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 24.9 kBtext throughout, nothing executable
Licence
not declarednone named by its author
Last change
—v1.0
Servers it uses
Noneruns standalone

What it does

Design the transition from worked examples to independent problem-solving using expertise-reversal principles. Use when students follow examples but cannot solve problems alone.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

cognitive-loadexpertise-reversalfadingkalyugarenklscaffoldingtransitionworked-examples

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md24.9 kB · preview
--- # AGENT SKILLS STANDARD FIELDS (v2) name: worked-example-to-problem-solving-transition-designer disable-model-invocation: false user-invocable: true effort: medium # EXISTING FIELDS skill_id: "ai-learning-science/worked-example-to-problem-solving-transition-designer" skill_name: "Worked Example to Problem Solving Transition Designer" domain: "ai-learning-science" version: "1.0" evidence_strength: "strong" evidence_sources: - "Kalyuga et al. (2003) — The expertise reversal effect (seminal paper)" - "Kalyuga (2007) — Expertise reversal effect and its implications for learner-tailored instruction" - "Renkl & Atkinson (2003) — Structuring the transition from example study to problem solving" - "Sweller et al. (2011) — Cognitive load theory (chapter on expertise reversal)" - "Van Merriënboer & Kirschner (2018) — Ten steps to complex learning (4C/ID model)" input_schema: required: - field: "skill_being_taught" type: "string" - field: "current_student_state" type: "string" optional: - field: "student_level" type: "string" - field: "subject_area" type: "string" - field: "number_of_practice_problems" type: "integer" - field: "time_available" type: "string" - field: "assessment_format" type: "string" output_schema: type: "object" fields: - field: "transition_sequence" type: "object" - field: "expertise_reversal_checkpoints" type: "array" - field: "fading_schedule" type: "object" - field: "independent_practice_design" type: "object" chains_well_with: - "digital-worked-example-sequence" - "adaptive-hint-sequence-designer" - "cognitive-tutoring-architecture-designer" - "productive-failure-desirable-difficulty-designer" teacher_time: "5 minutes" tags: ["expertise-reversal", "Kalyuga", "fading", "worked-examples", "Renkl", "transition", "scaffolding", "cognitive-load"] ---
70# Worked Example to Problem Solving Transition Designer
71
72## What This Skill Does
73
74Designs the transition sequence from studying worked examples to solving problems independently — the critical phase where scaffolding is gradually removed and students take over the cognitive work. This addresses one of the most important findings in cognitive load theory: the expertise reversal effect (Kalyuga et al., 2003). When students are novices, worked examples are highly effective — they reduce extraneous cognitive load and allow students to build schemas. But as students develop competence, the same worked examples become REDUNDANT and actually HARM learning — the scaffolding that helped novices now prevents more advanced students from engaging in the active processing that drives further learning. The optimal instruction is not fixed but ADAPTIVE: it should shift from worked examples to problem solving as the student's expertise grows. Renkl & Atkinson (2003) developed the "fading" approach: rather than an abrupt switch from examples to problems, gradually remove steps from the worked examples so students progressively take over more of the work. This skill designs the complete fading sequence, including the triggers for when to fade (based on student performance), the order of fading (which steps to remove first), and the design of the independent practice phase that follows.
75
76## Evidence Foundation
77
78Kalyuga et al. (2003) demonstrated the expertise reversal effect through a series of experiments showing that instructional techniques highly effective for novices become ineffective or harmful for more advanced learners. In the context of worked examples: novices who studied worked examples significantly outperformed novices who solved problems (the worked example effect), but as students gained expertise, this advantage reversed — more advanced students learned more from problem solving than from studying examples. The explanation is cognitive load theory: for novices, worked examples reduce the extraneous load of means-ends analysis (trying to figure out what to do), freeing cognitive resources for schema building. For advanced students, the worked example creates REDUNDANCY — the student already has a schema and the example is now unnecessary information that competes with their existing knowledge for processing resources. Kalyuga (2007) extended this work, arguing that learner-tailored instruction must continuously assess the learner's expertise level and adjust the instructional format accordingly. The practical implication: there is no single "best" instructional approach — the best approach depends on where the learner is RIGHT NOW. Renkl & Atkinson (2003) proposed fading as the solution to the example-to-problem transition. Rather than a sharp switch from "study examples" to "solve problems," they designed a gradual transition: first, full worked examples; then, examples with one step removed (the student completes that step); then, examples with two steps removed; and so on until the student is solving complete problems. They found that fading produced better learning than either fixed worked examples or fixed problem solving, because it continuously calibrated the cognitive demand to the student's growing expertise. Sweller et al. (2011) integrated the expertise reversal effect into the broader cognitive load theory framework, arguing that all instructional design must consider the INTERACTION between the learner's current knowledge and the instructional format. A technique that is optimal at one stage of learning may be counterproductive at another. Van Merriënboer & Kirschner (2018) developed the 4C/ID model for complex learning, which systematically designs the transition from heavily scaffolded task performance to independent performance through a sequence of task classes with decreasing support.
79
80## Input Schema
81
82The teacher must provide:
83- **Skill being taught:** What students need to do independently. *e.g. "Solving quadratic equations by factorisation — finding factors, setting each factor to zero, solving for both roots" / "Writing a balanced argument essay — introduction with thesis, supporting paragraphs with evidence, counterargument paragraph, conclusion with evaluated position" / "Calculating the mean, median, and mode from a frequency table and interpreting which average is most appropriate"*
84- **Current student state:** Where students are now. *e.g. "Students have seen two teacher-led worked examples. They can follow the steps when watching but haven't attempted any problems independently yet" / "Students can write persuasive essays (one-sided argument) but have never structured a balanced argument" / "Students can calculate mean from raw data but haven't worked with frequency tables"*
85
86Optional (injected by context engine if available):
87- **Student level:** Year group and proficiency
88- **Subject area:** The curriculum subject
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md3,791 words
Files1
Licencenot declared
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈820
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
5,405
on trigger
The instruction body, read only when the skill fires.
3.1%
of a 200k window
Ten skills this size would take about 31% of the window before you open a file.
050k100k150k200k context window

6.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 24.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md24.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Worked Example to Problem Solving Transition Designer · 6.2k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/worked-example-to-problem-solving-transition-desi/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/worked-example-to-problem-solving-transition-desi" ] && { [ ! -e .claude/skills/worked-example-to-problem-solving-transition-desi ] || { mv .claude/skills/worked-example-to-problem-solving-transition-desi "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/worked-example-to-problem-solving-transition-desi" .claude/skills/ && echo "Installed .claude/skills/worked-example-to-problem-solving-transition-desi"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add garethmanning/worked-example-to-problem-solving-transition-desi

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/worked-example-to-problem-solving-transition-desi/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/worked-example-to-problem-solving-transition-desi/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/worked-example-to-problem-solving-transition-desi" ] && { [ ! -e ~/.claude/skills/worked-example-to-problem-solving-transition-desi ] || { mv ~/.claude/skills/worked-example-to-problem-solving-transition-desi "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/worked-example-to-problem-solving-transition-desi" ~/.claude/skills/ && echo "Installed ~/.claude/skills/worked-example-to-problem-solving-transition-desi" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/worked-example-to-problem-solving-transition-desi/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as worked-example-to-problem-solving-transition-designer in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, worked-example-to-problem-solving-transition-desi.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version1.0
Publishedno release date on file
PriceFree
Referencegarethmanning/worked-example-to-problem-solving-transition-desi

Versions

v1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v1.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill