plugins/consultant/skills/research/SKILL.md
Launch multiple AI agents in parallel for comprehensive research coverage
npx skillsauth add nicknisi/claude-plugins researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Launch multiple agents simultaneously for comprehensive research coverage.
/consultant:research quick What are the best testing frameworks for React?
/consultant:research standard How do modern authentication systems work?
/consultant:research extensive Deep dive into microservices architecture patterns
/consultant:research What is the current state of WebAssembly? (defaults to standard)
| Intensity | Agents | Best For | | ------------- | -------------- | ----------------------------- | | quick | 5 (1 of each) | Simple queries, fast answers | | standard | 15 (3 of each) | Comprehensive coverage | | extensive | 40 (8 of each) | Deep-dive, exhaustive reports |
perplexity-researcher: Citations, current dataclaude-researcher: Built-in WebSearch, detailed analysiscodex-researcher: GPT-5 with high reasoninggemini-researcher: Multi-perspective synthesisgrok-researcher: Alternative LLM perspectiveParse $ARGUMENTS to extract:
quick, standard, or extensive (default: standard)Launch agents using multiple Task tool calls in ONE message.
IMPORTANT: All agents MUST be launched in a single message with multiple parallel Task tool calls.
After agents complete, synthesize results:
tools
Generate a /goal command to execute an ideation project's specs autonomously. Reads the contract, builds a goal prompt with phase ordering and spec paths, copies it to clipboard, and prints it. The user pastes the /goal command to start autonomous execution. Use when the user says 'goal', 'run as goal', 'get goal prompt', 'goal prompt', or wants to execute specs via /goal instead of /ideation:autopilot.
development
Go up a layer of abstraction and map the surrounding architecture. Use when the user is unfamiliar with an area of code, asks "how does this fit in", "what calls this", "give me the big picture", "where am I", "map this out", "I'm lost", "explain this area", or needs to understand how a file, module, or function connects to the rest of the system. Also use when the user says /zoom-out or "zoom out" mid-conversation — even without a specific file reference, orient them based on whatever code is currently in context.
development
Build a throwaway prototype to answer a design question before committing to real implementation. Generates either a runnable terminal app (for state machines, data models, business logic) or several radically different UI variations on one route (for visual/layout decisions). Use when the user wants to prototype, spike, POC, sanity-check a data model, mock up a UI, explore design options, or says "prototype this", "spike this out", "let me play with it", "try a few designs", "sketch this in code", "I want to try something before building it for real", "quick and dirty version", or "validate this approach" — even if they don't use the word "prototype."
development
Comprehensive, codebase-wide quality sweep that dispatches parallel subagents to find and fix structural issues. Covers deduplication, type consolidation, dead code removal, circular dependencies, weak types, defensive try/catch, deprecated paths, and AI slop. Primary support for JS/TS projects (knip, madge, TypeScript types); other languages get grep-based analysis. Use when the user asks to "deep clean the whole repo", "run a full codebase audit", "nuclear cleanup", "deslop everything", or "sweep the entire codebase for quality issues". Do NOT use for single-file fixes, branch-scoped diffs (use de-slopify instead), or targeted refactors.