Automated summary
Launches a sub-agent to conduct comprehensive research on a specified topic or codebase question.
Strengths
- Thorough investigation covering codebase analysis, external research, and synthesis.
- Structured process that ensures all aspects are explored.
- Produces a detailed report with summary, analysis, file locations, recommendations, and open questions.
Limitations
- May require multiple steps and sub-agent calls, increasing time and resource usage.
- Dependent on the quality of the Explore sub-agent and external sources.
- Not suitable for extremely broad or vague topics without clear scope.
Use when you need an in-depth understanding of a complex topic, code pattern, or architectural decision.
Avoid for simple lookups or when a quick answer from existing knowledge is sufficient.
Security analysis
SafeThe skill provides research instructions for a sub-agent without declaring or using any tools. It does not contain destructive commands, exfiltration patterns, or obfuscated payloads. No execution risk is present.
No concerns found
How this analysis is madeExamples
Perform deep research on the authentication flow in our codebase, including the login, token refresh, and permission checks. Provide a detailed report.Research best practices for error handling in Python. Find external resources and analyze our current error handling patterns in the src/ directory.Deep research on the architecture of the payment module. Understand the dependencies, data flow, and key design decisions.Deep Research Sub-Agent
Launch a sub-agent to perform deep research on a topic or codebase question.
Topic: $ARGUMENTS
Instructions for Sub-Agent
You are a research specialist. Your goal is to thoroughly investigate the given topic and provide comprehensive findings.
Research Process:
-
Scope Definition
- Clarify what needs to be researched
- Identify key questions to answer
-
Codebase Analysis (if code-related)
- Use Explore sub-agent to search relevant files
- Trace code paths and dependencies
- Understand architecture and patterns
-
External Research (if needed)
- Search documentation
- Look up best practices
- Find relevant examples
-
Synthesis
- Compile findings
- Identify patterns and insights
- Note any gaps or uncertainties
Output:
Provide a research report with:
- 📋 Summary of findings
- 🔍 Detailed analysis
- 📁 Relevant files/code locations
- 💡 Recommendations or next steps
- ❓ Open questions (if any)
Use Explore sub-agent (with Sonnet for complex analysis) to investigate thoroughly.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/deep-research-sub-agent-mm5t8bnz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/deep-research-sub-agent-mm5t8bnz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/deep-research-sub-agent-mm5t8bnz/download' --output '.skill-downloads/deep-research-sub-agent-mm5t8bnz/SKILL.md.part' && mv '.skill-downloads/deep-research-sub-agent-mm5t8bnz/SKILL.md.part' '.skill-downloads/deep-research-sub-agent-mm5t8bnz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/deep-research-sub-agent-mm5t8bnz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.