Frame Check

Check whether the stated problem is the right problem before work commits to it. Walks a problem statement back down to what was actually observed, names where the inference leapt, and returns competing frames plus the cheapest observation that would tell them apart. Use when the user asks "is this the right problem", "frame check", "what if the real problem is something else", "are we sure that's the cause", "reframe this", or questions a diagnosis. Also use proactively at the moments where solving the wrong problem is most likely and most expensive: a bug that keeps coming back after being f

49 stars 10 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add petekp/claude-code-setup --skill frame-check
Manual install
git clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/frame-check ~/.claude/skills/frame-check

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frame check

Most failed work is not a wrong answer. It is a right answer to the wrong
question. Kimball named this the error of the third kind in 1957 and Mitroff
built a practice on it. The work is rigorous, the execution is clean, and it is
aimed at something that was never the problem.

Catch it before the work commits.

## What you are looking for

A problem statement arrives sounding like an observation. "Onboarding is too
slow." "Users are confused." "It's a race condition." None of those are
observations. Someone watched something, selected part of it, decided what it
meant, and concluded — and the sentence you received is the last link with the
chain removed. Your job is to put the chain back and ask what else the bottom of
it supports.

Two different failures produce a wrong problem, and they need different tools.

**The conclusion outran the evidence.** What was observed supports several
readings, and one got picked without anyone noticing a choice was made. Argyris's
ladder of inference is the tool here: walk back down to what a camera would have
recorded.

**The evidence is sound and the goal is wrong.** The diagnosis holds up and is
aimed at an objective nobody has examined. Climbing down the ladder will never
find this, because the goal never entered as evidence. Argyris's double-loop
learning is the tool: ask which governing goal makes this count as a problem at
all.

Check the first. Check the second before you finish.
Read the full skill on GitHub

Details

Skill name
frame-check
Path
skills/frame-check/SKILL.md
License
MIT
Repo updated
26 October 2026

FAQ

What does the Frame Check skill do?

Check whether the stated problem is the right problem before work commits to it. Walks a problem statement back down to what was actually observed, names where the inference leapt, and returns competing frames plus the cheapest observation that would tell them apart. Use when the user asks "is this the right problem", "frame check", "what if the real problem is something else", "are we sure that's the cause", "reframe this", or questions a diagnosis. Also use proactively at the moments where solving the wrong problem is most likely and most expensive: a bug that keeps coming back after being f

How do I install the Frame Check skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill frame-check. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frame Check popular?

It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.

Related skills

Catch Up

49

petekp/claude-code-setup

Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.

AI, LLMs & Agents10

Clean Copy

49

petekp/claude-code-setup

Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.

Writing & Content10

Code Comments

49

petekp/claude-code-setup

Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.

Software Development10

Plain

49

petekp/claude-code-setup

Restate dense text in plain language. Use when the user asks for a simpler explanation or signals confusion.

Other10

Discernment Nudge

49

petekp/claude-code-setup

Suggest a few specific follow-up questions when consequential advice depends on unresolved assumptions. Skip reviews, simple explanations, and requests for brevity.

Other10

Spike

49

petekp/claude-code-setup

Run a disposable experiment to resolve a specific feasibility question. Use for an explicit spike or when inspection cannot resolve an implementation-blocking uncertainty.

Other10

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.