Agent skill

Ambiguity Resolver

by mohitagw15856 in mohitagw15856/pm-claude-skills

Structure vague opportunities and unclear briefs into actionable one-page problem statements.

MITAuto-check passedBackend & APIs

Install Ambiguity Resolver

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill ambiguity-resolver -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills ambiguity-resolver --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ambiguity-resolver .claude/skills/ambiguity-resolver && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ambiguity-resolver
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
538 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Structure vague opportunities and unclear briefs into actionable one-page problem statements.

  • Works in 3 steps: Reframe → Scope → Action
  • Asked to clarify a vague brief
  • SKILL.md covers Required Inputs, Three-Stage Process, Output Structure and Example (Partial), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ambiguity Resolver is an agent skill from mohitagw15856/pm-claude-skills. Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering GraphQL. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to clarify a vague brief
  • Frame an undefined problem
  • Make sense of an unclear opportunity
  • The user says we need to figure out what to do about X

Example prompts

  • “we need to figure out what to do about X”
  • “ve been asked to look into Y”
  • “/ambiguity-resolver”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Reframe
  2. Scope
  3. Action

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ambiguity Resolver loads about 1.1k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 538 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 538 words, ~1,070 tokens.

Download SKILL.mdSave it as .claude/skills/ambiguity-resolver/SKILL.md (or your agent's skills folder).
name
ambiguity-resolver
description
Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

Ambiguity Resolver Skill

Turn vague briefs and half-formed opportunities into structured, actionable problem statements — so you can reply with clarity instead of asking for three more meetings.

Required Inputs

Ask the user for these if not provided:

  • The vague brief or opportunity description (even a single sentence is enough)
  • Who asked for this (stakeholder context shapes the framing)
  • Known constraints (timeline, budget, team size — if any are known)

Three-Stage Process

Stage 1: Reframe
  • Restate the vague input as 3-5 explicit questions that need answering
  • Identify the unstated assumptions hidden in the brief
  • Surface the real decision this feeds into (what will someone do differently once this is resolved?)
Stage 2: Scope
  • Define what is explicitly IN scope
  • Define what is explicitly OUT of scope (equally important)
  • Identify the deadline pressure: is this urgent/important, important/not urgent, or unclear?
  • Name who owns the final decision and who needs to be consulted
Stage 3: Action
  • Define the minimum viable research: 2-3 activities maximum that would give enough signal to move forward with confidence
  • Time estimate for each activity
  • What each activity would tell you (and what it wouldn't)
  • Proposed check-in point: when to regroup before committing to more

Validate — Confirm every reframed question maps to at least one research activity. Verify scope boundaries are specific enough to say "no" to something concrete.

Output Structure

Problem Brief: [Opportunity Area]

Restated as questions:

  1. [Question 1]
  2. [Question 2]
  3. [Question 3]

Unstated assumptions we should surface:

  • [Assumption 1]
  • [Assumption 2]

In scope: [Clear boundary] Out of scope: [Clear boundary] Decision owner: [Name/role] Timeline: [Real deadline if known, or "unclear — recommend setting one"]

Minimum viable research:

ActivityTime requiredWhat it tells usWhat it won't tell us
[activity][time][insight][limitation]

Proposed check-in: After [activity], regroup to decide whether to proceed or pivot.

Show full SKILL.md (239 more words)Show less

Example (Partial)

Input: "We need to figure out what to do about our enterprise customers."

Restated as questions:

  1. Are enterprise customers churning, underperforming on expansion, or both?
  2. Is this a product gap, a support/service gap, or a pricing/packaging issue?
  3. What does "do something" look like — a new initiative, a policy change, or a resource shift?

In scope: Enterprise accounts ($50K+ ARR) showing declining health scores in the last two quarters Out of scope: SMB segment, new enterprise acquisition strategy

Anti-Patterns

  • Do not reframe the brief into questions that are still too broad to research — each reframed question must be answerable by a specific activity
  • Do not list a research activity without stating what it would tell you and what it would NOT tell you
  • Do not leave the decision owner as "leadership" or "the team" — name a specific person or role
  • Do not omit an explicit out-of-scope boundary — without it, scope will expand organically and the brief becomes meaningless

Quality Checks

  • Every reframed question is specific enough to research (not "how do we improve things?")
  • Scope boundaries name something concrete that is excluded
  • Research activities are achievable within the stated timeline
  • Decision owner is identified (not "leadership" — a specific person or role)

Example Trigger Phrases

  • "Clarify a vague brief."
  • "Frame an undefined problem."
  • "Make sense of an unclear opportunity."
  • "We need to figure out what to do about X."
  • "I've been asked to look into Y."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ambiguity-resolver of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Ambiguity Resolver next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ambiguity Resolver compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ambiguity Resolver this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT
GraphQL Operations with CodegenChrisWiles/claude-code-showcase6.1k3 repos~1.5kAutomated safety check: PassNone
Supabasecurvenote/curvenote1705 repos~2.2kAutomated safety check: PassCustom licence
API Design Principlesjh941213/my-cc-harness12518 repos~3.4kAutomated safety check: PassNone

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed
  • GraphQL Operations with Codegen

    ChrisWiles/claude-code-showcase

    Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.

    6.1k GitHub starsUsed in 3 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    170 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • API Design Principles

    jh941213/my-cc-harness

    REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.

    125 GitHub starsUsed in 18 repos~3.4k tokens
    Backend & APIsAuto-check passed
  • API And Interface Design

    dzhalaevd/Donatello

    Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 8 repos~2.6k tokens
    Backend & APIsAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Ambiguity Resolver

What does Ambiguity Resolver do?

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Ambiguity Resolver is an agent skill from mohitagw15856/pm-claude-skills. Structure vague opportunities and unclear briefs into actionable one-page problem statements.

When should I use Ambiguity Resolver?

Ambiguity Resolver fits situations like: asked to clarify a vague brief; frame an undefined problem; make sense of an unclear opportunity; the user says we need to figure out what to do about X.

How do I install Ambiguity Resolver in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill ambiguity-resolver -a claude-code`. Or copy the skill folder (skills/ambiguity-resolver in mohitagw15856/pm-claude-skills) into .claude/skills/ambiguity-resolver in your project. Claude Code loads it when a task matches its description.

How do I install Ambiguity Resolver in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill ambiguity-resolver -a codex`. Or copy the skill folder (skills/ambiguity-resolver in mohitagw15856/pm-claude-skills) into .agents/skills/ambiguity-resolver in your project. Codex loads it when a task matches its description.

Can I use Ambiguity Resolver in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill ambiguity-resolver -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ambiguity-resolver, .gemini/skills/ambiguity-resolver, .github/skills/ambiguity-resolver and .opencode/skills/ambiguity-resolver in your project.

What does Ambiguity Resolver need to run?

SKILL.md names no scripts, command-line tools or credentials: Ambiguity Resolver is instructions for the agent only.

Does Ambiguity Resolver access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ambiguity Resolver safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ambiguity Resolver use?

Ambiguity Resolver is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ambiguity Resolver use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ambiguity Resolver?

Skills that share tags, products or a category with Ambiguity Resolver: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars) and Supabase (curvenote/curvenote, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ambiguity Resolver?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.