question-framing

question-framing is a skill for Claude Code from ai-analyst-lab/ai-analyst-plugin. It costs 108 tokens per session (2,813 once invoked), scanned A, original, MIT.

A structured method for turning a broad analysis request into a goal, decision, metric, and hypothesis, followed by a seven-field analysis plan.

In plain words
What is it for?
It is for framing requests such as investigating changes, exploring a problem, or asking why something happened before analyzing data.
Why use it?
It prevents analysis from starting with unclear questions or data that may not inform a real decision.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ai-analyst-plus plugin — 44 skills, 1 command, 13 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ai-analyst-lab/ai-analyst-plugin/question-framing
Any agent
npx skills add ai-analyst-lab/ai-analyst-plugin --skill question-framing
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-plugin

Made for: Claude Code.

Or install ai-analyst-plus, the plugin that ships this one along with the rest of its 44 skills, 1 command, 13 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for question-framing

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plugin/question-framing.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plugin/question-framing)
Your own site
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plugin/question-framing"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plugin/question-framing.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00108 $0.02813
Opus 5 $0.00054 $0.01406
Sonnet 5 $0.00022 $0.00563
Haiku 4.5 $0.00011 $0.00281

Measured 6d ago against content hash e6a996571806, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

question-framing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ai-analyst-plus/skills/question-framing/SKILL.md · 251 lines

How it starts

The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Question Framing

Purpose

Structure analytical questions using the Question Ladder framework so every analysis starts with a clear decision context, measurable success criteria, and testable hypotheses.

When to Use

Apply this skill when starting any new analysis, when a user asks a vague question ("How are we doing?"), or when an analysis request lacks decision context. Always frame before analyzing.

Instructions

Pre-flight: Load Learnings

Before executing, check .knowledge/learnings/index.md for relevant entries:

  • Read the file. If it doesn't exist or is empty, skip silently.
  • Scan for entries under "Question Framing" and "General" headings (or related categories like "Business Context", "Methodology Notes").
  • If entries exist, incorporate them as constraints or context for this execution.
  • Never block execution if learnings are unavailable.

The Question Ladder

Every analytical question climbs four rungs:

GOAL        → What business outcome are we trying to achieve?
DECISION    → What specific decision will this analysis inform?
METRIC      → What will we measure to inform that decision?
HYPOTHESIS  → What do we expect to find, and why?

The rule: Never start analyzing data until you can state all four rungs. If the requester only gives you a goal ("improve retention"), your first job is to climb the ladder before touching data.

Framing Process

Step 1: Extract the decision Ask: "What will you DO differently based on the answer?"

  • If the answer is "nothing" or "I'm just curious" → this is reporting, not analysis. Offer two paths:
    • Path A: Quick stat/dashboard (if truly no decision)
    • Path B: Clarify decision context first, then frame properly
  • If the answer is a specific action → you have a decision. Proceed to Step 2.

Step 2: Define success criteria Ask: "How will you know the analysis answered your question?"

  • The answer should be specific: "If conversion rate dropped >10% in segment X, we'll prioritize a fix"
  • Not vague: "We'll understand our users better"
  • Success criteria should include specific thresholds, conditions, or decision rules

Read the full file on GitHub · 251 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 251 lines · 108 tokens per session scan A e6a996571806

Subscribe to this mod's changes

question-framing is a skill published in the GitHub repository ai-analyst-lab/ai-analyst-plugin (32 stars, last pushed 10d ago), licensed MIT. It adds 108 tokens to every session and 2,813 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens