Agent skill · Security

researching

Use when requirements are fuzzy, multiple technical approaches exist, or change affects architecture, API, data, or security

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill researching --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/researching/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

# Researching Skill Use when the how is unclear; output is a chosen approach with evidence. **Prerequisites:** If what/why is unclear, use **discovering** skill first. ## Quick Reference | Track | When | Output | | -------------- | ---------------------------- | ------------------------------------ | | Fast (default) | Standard decisions | Brief: problem, decision, risks | | Full | API/security/multi-subsystem | Research brief + optional design doc | ## When to Use - Requirements are fuzzy or incomplete - Multiple plausible approaches exist (spike, proof of concept needed) - Change affects architecture, API, data, or security Skip if: obvious bug, trivial change, pattern already exists. ## Fast vs Full Track ``` Is it high-risk? ├── No → Fast Track (default) └── Yes → Full Track ├── Changes public API ├── Security/data implications ├── Team disagreement └── Touches multiple subsystems ``` ## Core Rule **Evidence before opinions.** Never recommend anything until facts are gathered: what already exists in code, which constraints are real, what decisions were made before. If evidence is missing — label it as assumption and lower confidence. ## Quick Rules - One question at a time whil

What's inside
Steps it walks through
  1. Quick Reference
  2. When to Use
  3. Fast vs Full Track
  4. Core Rule
  5. Quick Rules
  6. When to Ask vs Act
  7. Workflow
  8. Fast Track (default)
  9. Full Track
  10. Stop Conditions
  11. Best Practices
  12. Common Mistakes
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the researching skill do?

Use when requirements are fuzzy, multiple technical approaches exist, or change affects architecture, API, data, or security

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill researching --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