Deep Research Skill
Conduct rigorous, multi-part research on a complex topic producing a report grounded entirely in confirmed sources. No design assumptions before research is complete. All claims backed by source links.
Skill Files
This skill is split across files — read the relevant ones before proceeding:
| File |
Purpose |
security.md |
Full template and agent prompts for security research mode |
techtrend.md |
Full template and agent prompts for tech trend / ecosystem research mode |
law-policy.md |
Full template and agent prompts for law, policy, regulatory, and compliance research mode |
report-template.html |
HTML report template — use when user requests an HTML output |
Step 1: Detect Mode
Determine research mode from the query before reading any template:
| Mode |
Trigger keywords |
Template to read |
security |
security, threat, CVE, attack, defense, vulnerability, exploit, risk, malware |
Read security.md |
techtrend |
trend, forecast, ecosystem, landscape, technology, hardware, market, adoption |
Read techtrend.md |
law-policy |
law, policy, regulation, compliance, legal requirement, statutory, retention, audit trail, recordkeeping, regulator, licensee, service provider, data residency, data protection, privacy, telecom law, cybersecurity law |
Read law-policy.md |
| Ambiguous |
None clearly applies, or multiple modes are plausible |
Ask: "Is this a security analysis, technology trend/ecosystem research, or law/policy compliance research?" |
Step 2: Read the Template
After detecting mode, read the appropriate template file in full before writing the research plan or launching agents. The template files contain:
- The 5-part structure for that mode
- Per-part research questions and source guidance
- Agent prompt scaffolding
- Lessons learned specific to that mode
Step 3: Execute
Follow the execution steps in the template. The core workflow is the same for all modes:
- Write
RESEARCH_PLAN.md in a new {topic}_{YYYYMM}/ folder
- Launch 5 parallel background agents (one per part)
- Acknowledge each agent as it completes with a key findings summary
- After all 5 complete: read all raw files, compile
RESEARCH_REPORT.md
- If HTML output requested: use
report-template.html as the base
Universal Rules (apply to all modes)
Source quality
- Specs/products: Official vendor docs, press releases, spec sheets
- CVEs/security: NVD, MITRE, vendor advisories, Black Hat/DEF CON/USENIX papers
- Academic: arXiv, NeurIPS/ICLR/CVPR/ACL proceedings, OpenReview
- Market data: Gartner, IDC, Forrester, MarketsandMarkets, Crunchbase
- Regulatory: EUR-Lex, NIST, CISA, Federal Register, national AI laws
- Law/policy: official gazettes, government legal portals, regulator websites, ministry publications, court/tribunal decisions, official consultation papers
- Benchmarks: MLCommons/MLPerf, HuggingFace leaderboards, official vendor disclosures
- Do NOT cite: Wikipedia, unattributed blogs, secondary summaries
Agent instructions (every agent must)
- Fetch and READ actual URLs — do not rely on training data alone
- Note publication dates — distinguish confirmed vs. announced vs. speculative
- Save raw output to
{folder}/raw_research/XX_topic.md
- Target 2,000+ words with real data, tables, and source URLs
File structure
{topic}_{YYYYMM}/
├── RESEARCH_PLAN.md
├── RESEARCH_REPORT.md
├── report.html # optional, if HTML requested
└── raw_research/
├── 01_*.md
├── 02_*.md
├── 03_*.md
├── 04_*.md
└── 05_*.md
Common errors to avoid
- Wrong platform ID: Fetch the actual product website before writing the plan
- Shallow agents: Anchor every agent with 3–5 specific URLs to fetch first
- Premature design (security mode): Do not write Part 4 before Parts 1–3 are reviewed
- Fixed dimensions (techtrend mode): Parts 2–4 are defined per-topic in the plan, not preset
- Legal status confusion (law-policy mode): never mix binding law, proposed rules, regulator guidance, unofficial translations, and vendor summaries without labeling them
- Blocked sources: Chinese sources behind auth walls — search for equivalent open-web sources
- Context length: Raw research files can be 5,000–7,000 words each — read them carefully
Example Invocations
# Security (auto-detected)
/deepresearch security for personal AI endpoint agents including OpenClaw and Claude Code
/deepresearch supply chain attacks on npm packages
/deepresearch quantum-safe cryptography for financial services
# Tech trend (auto-detected)
/deepresearch endpoint LLM ecosystem — hardware, models, runtimes, applications
/deepresearch autonomous vehicle software stack trends and 2030 forecast
/deepresearch edge AI chip market landscape
# Law/policy (auto-detected)
/deepresearch data residency laws for financial SaaS in Singapore, Indonesia, and Malaysia
/deepresearch firewall log retention compliance requirements in Thailand and Turkiye
/deepresearch EU AI Act obligations for enterprise AI coding assistants
# With HTML output
/deepresearch endpoint LLM ecosystem output: html
1---2name: deepresearch3description: Conduct structured deep research on any topic — security threat analysis, technology trend mapping, ecosystem analysis, market forecasts, or law/policy compliance research. Produces a multi-part report grounded in confirmed sources with no premature design assumptions. Use when asked to "deepresearch", "research deeply", or produce a comprehensive multi-part research report. Auto-detects whether the topic calls for security-focused, tech-trend-focused, or law/policy-focused structure.4---56# Deep Research Skill78Conduct rigorous, multi-part research on a complex topic producing a report grounded entirely in confirmed sources. No design assumptions before research is complete. All claims backed by source links.910## Skill Files1112This skill is split across files — read the relevant ones before proceeding:1314| File | Purpose |15|------|---------|16| `security.md` | Full template and agent prompts for security research mode |17| `techtrend.md` | Full template and agent prompts for tech trend / ecosystem research mode |18| `law-policy.md` | Full template and agent prompts for law, policy, regulatory, and compliance research mode |19| `report-template.html` | HTML report template — use when user requests an HTML output |2021---2223## Step 1: Detect Mode2425Determine research mode from the query **before reading any template**:2627| Mode | Trigger keywords | Template to read |28|------|-----------------|-----------------|29| `security` | security, threat, CVE, attack, defense, vulnerability, exploit, risk, malware | Read `security.md` |30| `techtrend` | trend, forecast, ecosystem, landscape, technology, hardware, market, adoption | Read `techtrend.md` |31| `law-policy` | law, policy, regulation, compliance, legal requirement, statutory, retention, audit trail, recordkeeping, regulator, licensee, service provider, data residency, data protection, privacy, telecom law, cybersecurity law | Read `law-policy.md` |32| Ambiguous | None clearly applies, or multiple modes are plausible | Ask: "Is this a security analysis, technology trend/ecosystem research, or law/policy compliance research?" |3334---3536## Step 2: Read the Template3738After detecting mode, **read the appropriate template file** in full before writing the research plan or launching agents. The template files contain:39- The 5-part structure for that mode40- Per-part research questions and source guidance41- Agent prompt scaffolding42- Lessons learned specific to that mode4344---4546## Step 3: Execute4748Follow the execution steps in the template. The core workflow is the same for all modes:49501. Write `RESEARCH_PLAN.md` in a new `{topic}_{YYYYMM}/` folder512. Launch 5 parallel background agents (one per part)523. Acknowledge each agent as it completes with a key findings summary534. After all 5 complete: read all raw files, compile `RESEARCH_REPORT.md`545. If HTML output requested: use `report-template.html` as the base5556---5758## Universal Rules (apply to all modes)5960### Source quality61- **Specs/products**: Official vendor docs, press releases, spec sheets62- **CVEs/security**: NVD, MITRE, vendor advisories, Black Hat/DEF CON/USENIX papers63- **Academic**: arXiv, NeurIPS/ICLR/CVPR/ACL proceedings, OpenReview64- **Market data**: Gartner, IDC, Forrester, MarketsandMarkets, Crunchbase65- **Regulatory**: EUR-Lex, NIST, CISA, Federal Register, national AI laws66- **Law/policy**: official gazettes, government legal portals, regulator websites, ministry publications, court/tribunal decisions, official consultation papers67- **Benchmarks**: MLCommons/MLPerf, HuggingFace leaderboards, official vendor disclosures68- **Do NOT cite**: Wikipedia, unattributed blogs, secondary summaries6970### Agent instructions (every agent must)711. Fetch and READ actual URLs — do not rely on training data alone722. Note publication dates — distinguish confirmed vs. announced vs. speculative733. Save raw output to `{folder}/raw_research/XX_topic.md`744. Target 2,000+ words with real data, tables, and source URLs7576### File structure77```78{topic}_{YYYYMM}/79├── RESEARCH_PLAN.md80├── RESEARCH_REPORT.md81├── report.html # optional, if HTML requested82└── raw_research/83 ├── 01_*.md84 ├── 02_*.md85 ├── 03_*.md86 ├── 04_*.md87 └── 05_*.md88```8990### Common errors to avoid911. **Wrong platform ID**: Fetch the actual product website before writing the plan922. **Shallow agents**: Anchor every agent with 3–5 specific URLs to fetch first933. **Premature design** (security mode): Do not write Part 4 before Parts 1–3 are reviewed944. **Fixed dimensions** (techtrend mode): Parts 2–4 are defined per-topic in the plan, not preset955. **Legal status confusion** (law-policy mode): never mix binding law, proposed rules, regulator guidance, unofficial translations, and vendor summaries without labeling them966. **Blocked sources**: Chinese sources behind auth walls — search for equivalent open-web sources977. **Context length**: Raw research files can be 5,000–7,000 words each — read them carefully9899---100101## Example Invocations102103```104# Security (auto-detected)105/deepresearch security for personal AI endpoint agents including OpenClaw and Claude Code106/deepresearch supply chain attacks on npm packages107/deepresearch quantum-safe cryptography for financial services108109# Tech trend (auto-detected)110/deepresearch endpoint LLM ecosystem — hardware, models, runtimes, applications111/deepresearch autonomous vehicle software stack trends and 2030 forecast112/deepresearch edge AI chip market landscape113114# Law/policy (auto-detected)115/deepresearch data residency laws for financial SaaS in Singapore, Indonesia, and Malaysia116/deepresearch firewall log retention compliance requirements in Thailand and Turkiye117/deepresearch EU AI Act obligations for enterprise AI coding assistants118119# With HTML output120/deepresearch endpoint LLM ecosystem output: html121```