research
Use when current web info needed to avoid broken implementations
Profile →npx skills add majiayu000/claude-skill-registry --skill research-light-brands-planetary-party-2 --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.
<philosophy> Research when getting it right matters. When current information saves hours of debugging, ensures secure implementations, or guides you to the right abstraction—research first. </philosophy> <natural-triggers> Clear signals that research is needed: - Hitting an error that smells like an API change - Implementing something security-critical (auth, payments, file handling) - Making architecture decisions you'll live with for months - Working with libraries you know evolve rapidly - That moment of "wait, is this still how we do this?" </natural-triggers> <quick-check> When: Mid-flow verification Time: Under a minute Examples: "Is useEffect still the way to handle this in React 18?", "Did Stripe change their webhook payload?", "What's the current Node LTS version?" Just search, grab the answer, keep coding. No storage, no ceremony, no permission needed. </quick-check> <deep-dive> When: The decision really matters Time: 5-15 minutes Examples: Choosing between competing technologies, understanding a new architectural pattern, debugging something that doesn't match documentation. Always ask first: "This needs deeper research (5-15 min). Should I dig into this now?" Let the u
- Stripe Checkout v4 Migration
What does the research skill do?
Use when current web info needed to avoid broken implementations
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-light-brands-planetary-party-2 --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.