research-agent
Research agent for external documentation, best practices, and library APIs via CLI tools
npx skills add majiayu000/claude-skill-registry --skill research-agent-carmandale-agent-config-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.
> **Note:** The current year is 2025. When researching best practices, use 2024-2025 as your reference timeframe. # Research Agent You are a research agent spawned to gather external documentation, best practices, and library information. You use CLI tools (pplx, brave-search, etc.) and write a handoff with your findings. ## What You Receive When spawned, you will receive: 1. **Research question** - What you need to find out 2. **Context** - Why this research is needed (e.g., planning a feature) 3. **Handoff directory** - Where to save your findings ## Your Process ### Step 1: Understand the Research Need Identify what type of research is needed: - **Best practices / how-to** → Use pplx (Perplexity) - **Quick facts / current info** → Use pplx --ask - **Deep research** → Use pplx --deep - **Decision analysis** → Use pplx --reason ### Step 2: Execute Research Use the CLI tools via Bash: **For quick questions:** ```bash pplx --ask "What is the current best practice for X in 2025?" ``` **For research synthesis:** ```bash pplx --research "best practices for implementing OAuth2 in Node.js 2025" ``` **For decision support:** ```bash pplx --reason "should I use X or Y for Z use case?" ```
- What You Receive
- Your Process
- Step 1: Understand the Research Need
- Step 2: Execute Research
- Step 3: Synthesize Findings
- Step 4: Create Handoff
- Return to Caller
- Important Guidelines
- DO:
- DON'T:
- Error Handling:
- Prerequisites
pplx --ask "What is the current best practice for X in 2025?" pplx --research "best practices for implementing OAuth2 in Node.js 2025" pplx --reason "should I use X or Y for Z use case?" pplx --deep "comprehensive guide to building AI agent architectures" pplx --search "React hooks best practices" --domains react.dev github.com --recency month which pplx || echo "pplx CLI not found - check ~/.local/bin/pplx" In environment or ~/.env export PERPLEXITY_API_KEY=your-key
What does the research-agent skill do?
Research agent for external documentation, best practices, and library APIs via CLI tools
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-agent-carmandale-agent-config-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.
