Agent skill

technical-research

Systematic technical research methodology for evaluating technologies, libraries, and approaches. Use when researching new technologies, comparing alternatives, or making technical decisions.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill technical-research-datorresb-vibecoding-starter --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/analysis/technical-research-datorresb-vibecoding-starter/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Technical Research Skill ## Core Principle **Research systematically to make evidence-based decisions.** Good technical research: - **Starts with clear questions** — Know what you're trying to decide - **Evaluates systematically** — Consistent criteria across options - **Documents findings** — Share knowledge with team - **Leads to action** — Research informs decisions --- ## Research Process ``` ┌────────────────────────────────────────────────────┐ │ RESEARCH PROCESS │ └────────────────────────────────────────────────────┘ 1. Define Question ↓ 2. Establish Criteria ↓ 3. Find Candidates ↓ 4. Evaluate Systematically ↓ 5. Hands-On Verification ↓ 6. Document & Decide ``` --- ## Step 1: Define the Research Question ### Start with "Why" ❌ **Vague:** "Research state management libraries" ✅ **Clear:** "Which state management library best fits our React app with complex async workflows?" ### Good Research Questions ✅ "Should we migrate from REST to GraphQL for our mobile API?" ✅ "Which message queue (RabbitMQ, Kafka, AWS SQS) handles our 10M events/day use case best?" ✅ "Can we replace our custom auth with Auth0 without breaking existing integrations?" ### Bad Research Questions ❌ "What

What's inside
Steps it walks through
  1. Core Principle
  2. Research Process
  3. Step 1: Define the Research Question
  4. Start with "Why"
  5. Good Research Questions
  6. Bad Research Questions
  7. Step 2: Establish Evaluation Criteria
  8. Categories of Criteria
  9. Prioritize Criteria
  10. Step 3: Find Candidates
  11. Sources
  12. Narrowing Down
  13. Step 4: Evaluate Systematically
  14. Use a Scoring Matrix
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the technical-research skill do?

Systematic technical research methodology for evaluating technologies, libraries, and approaches. Use when researching new technologies, comparing alternatives, or making technical decisions.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill technical-research-datorresb-vibecoding-starter --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.

Keep going