Skip to content

staruhub/ClaudeSkills / skills/Geek-skills-deep-research

deep-research

Verified

Use this skill when the user wants an evidence-based research memo, literature review, market/policy/technical landscape, or a multi-source decision brief with citations, trade-offs, and a clear conclusion. Best for tasks that need synthesis across multiple external sources, iterative follow-up research, or a reusable written artifact. Do not use for quick factual lookups, single-source summaries, simple Q&A, summarizing one document the user already provided, plan-only requests where the user explicitly defers the actual research, or when the user wants a short answer with no need for cited evidence (a short but evidence-backed conclusion is still a brief memo, which this skill covers). Chinese trigger examples: "帮我调研", "深度研究", "综述报告", "技术选型分析", "竞品研究", "政策分析".

references/tension-discovery.md

View on GitHub
# Tension Discovery V8

Use this only when the topic is likely to hide a misleading default narrative.

## Good fits
- hype-heavy technologies
- procurement / strategy / policy choices
- topics with strong online consensus but weak operational evidence
- topics where benefits are over-advertised or costs are under-discussed

## Not a good fit
- neutral descriptive explainers
- routine overviews with little controversy
- narrow tasks where the user simply wants current facts

## Three useful probes

1. **Concept confusion**
   - Is one label hiding multiple mechanisms?
   - Example: “AI agent” could mean chat assistant, workflow bot, or autonomous operator.

2. **Assumption check**
   - What is everyone casually assuming is true?
   - What evidence would actually be needed to support that assumption?

3. **Effect vs mechanism**
   - People say it works. Do they know *why* it works?
   - Could the reported effect be real while the claimed cause is wrong?

## Output
Write a short `tension-scan.md` with 1-3 candidate tensions.
Each tension should be testable, not theatrical.

Bad: “Everything people believe about X is wrong.”
Good: “The main benefit of X may come more from Y than from the commonly cited Z.”
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall