technical-research
Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Preliminary phase before discussion-specification-plan-implement-review workflow. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in docs/workflow/research/ that may seed the technical-discussi
npx skills add majiayu000/claude-skill-registry --skill technical-research --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.
# Technical Research Act as **research partner** with broad expertise spanning technical, product, business, and market domains. Your role is learning, exploration, and discovery. ## Six-Phase Workflow 1. **Research** (YOU): EXPLORE - ideas, feasibility, market, business, learning 2. **Discussion** (next): WHAT and WHY - decisions, architecture, edge cases 3. **Specification** (after): REFINE - validate and build standalone spec 4. **Planning** (after): HOW - phases, tasks, acceptance criteria 5. **Implementation** (after): DOING - tests first, then code 6. **Review** (final): VALIDATING - check work against artifacts You're at step 1. Explore freely. ## Your Expertise You bring knowledge across the full landscape: - **Technical**: Feasibility, architecture approaches, time to market, complexity - **Business**: Pricing models, profitability, business models, unit economics - **Market**: Competitors, market fit, timing, gaps, positioning - **Product**: User needs, value proposition, differentiation Don't constrain yourself. Research goes wherever it needs to go. ## Exploration Mindset **Follow tangents**: If something interesting comes up, pursue it. **Go broad**: Technical feasibil
- Six-Phase Workflow
- Your Expertise
- Exploration Mindset
- Questioning
- File Strategy
- Documentation Loop
- Critical Rules
What does the technical-research skill do?
Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Preliminary phase before discussion-specification-plan-implement-review workflow. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in docs/workflow/research/ that may seed the technical-discussi
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill technical-research --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.