question-resolver
Systematically resolve questions - determine if answerable, gather evidence
Profile →npx skills add majiayu000/claude-skill-registry --skill question-resolver --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill: question-resolver ## What I do I manage the process of finding answers to technical and domain-specific questions. I ensure that every question is classified, systematically researched using appropriate tools, and documented once resolved. ## When to use me - When faced with an unknown API, library, or codebase pattern - To resolve ambiguity in user requests or requirements - During research spikes to understand a new technology - To track "known unknowns" that need resolution before proceeding ## Core principles 1. **Classify first** — Is it answerable now (documentation), through research (spikes/data), or unanswerable (requires stakeholder input)? 2. **Structured investigation** — Use a methodical approach: hypothesise, search, verify. 3. **Gather evidence** — Rely on documentation, code, or experimental results rather than hearsay. 4. **Document the "why"** — Once resolved, record the answer and the evidence that supports it. ## Patterns & examples **Question Log Template:** | Question | Type (Doc/Spike/Stake) | Priority | Resolution Status | Link to Evidence | | :--- | :--- | :--- | :--- | :--- | | "Does library X support IPv6 natively?" | Doc | High | Resolved | [Lin
- What I do
- When to use me
- Core principles
- Patterns & examples
- Anti-patterns to avoid
- KB Reference
- Related skills
What does the question-resolver skill do?
Systematically resolve questions - determine if answerable, gather evidence
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill question-resolver --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.