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.
npx skills add uthumany/uthy-legacy-os --skill problem-framinggit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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.
[](https://agentmods.dev/skills/uthumany/uthy-legacy-os/problem-framing)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/problem-framing"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/problem-framing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/problem-framing"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/problem-framing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.01116 |
| Opus 5 | $0.00015 | $0.00558 |
| Sonnet 5 | $0.00006 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
problem-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Framing
Overview
The way you frame a problem determines the range of solutions you can see. A narrow frame leads to narrow solutions. This skill teaches techniques to reframe problems — expanding the solution space, getting teams unstuck, and finding breakthrough approaches.
When to Use
- The team is arguing about solutions but hasn't agreed on the problem
- All obvious solutions have been tried and failed
- Stakeholders are blocking each other with different frames
- You want to find innovative approaches, not just incremental improvements
- Don't use for: well-understood execution problems where reframing adds noise
Instructions
1. Surface the Current Frame
Ask: "What's the problem we're trying to solve?" Have each stakeholder answer independently. Compare the frames:
- Narrow frame: "We need a better onboarding screen"
- Broader frame: "Users don't reach the 'aha moment' quickly enough"
- Widest frame: "Our activation rate is 30%, below the 60% benchmark"
The narrower the frame, the more it prescribes a solution. Surface this.
2. Apply Reframing Techniques
Technique 1: The Five Whys Ask "why" five times to expand the frame:
- "Users aren't completing onboarding" → "Why?"
- "They don't understand the value" → "Why?"
- "They skip the tutorial because it's too long" → "Why?"
- "They're busy and want immediate value" → "Why?"
- "They haven't committed to the product yet" → Real frame: "We're asking for time investment before demonstrating value"
Technique 2: Flip the Frame Turn the problem around:
- From: "How do we get users to complete onboarding?"
- To: "How do we deliver value before onboarding is complete?"
- To: "How do we eliminate the need for onboarding?"
Technique 3: Change the Subject
- From: "How can we make our search better?"
- To: "How can users find what they need without searching?"
- To: "How can the information come to them?"
Technique 4: Expand the Constraints
- What if we had unlimited budget? → frees from resource thinking
- What if we had zero budget? → forces creativity
- What if we had to solve it in one week? → forces prioritization
- What if users had to pay $100/month? → forces value thinking
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.
- 9d ago First seen · 112 lines · 31 tokens per session scan A fa1ae88750a7
problem-framing is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 1,116 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…