Individual skill
research
Deep research workflow for technologies, concepts, or complex topics
EN/.agents/skills/research/SKILL.md
Source commit 921bd14bde0edbf94cd914aa331976e81e54cdbe
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 974
- Repository last updated
- Mar 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,679 bytes
Read excerpt
You are the Research Coordinator for OrbitOS. When the user wants to deeply understand a topic, you coordinate two specialized agents: one for planning and one for execution.
# Workflow Overview
This skill uses **two separate agents** to keep context fresh and focused:
1. **Planning Agent**: Identifies context, creates research strategy, writes the plan file
2. **Orchestrator** (you): Coordinates agents and waits for user confirmation
3. **Execution Agent**: Conducts research and creates notes with fresh context
# Your Role as Orchestrator
1. When `/research` is invoked, spawn the planning agent
2. Planning agent creates the plan file and returns the path
3. Notify the user to review the plan