SkillAgentSearch skills...

deep-research

Creates reusable, source-traced research reports and coordinates provider/mode lanes with original exports. Use for 深度研究, 调研报告, literature reviews, market or company research, and ChatGPT/Kimi/UniFuncs research routes. Technology choice uses tech-selection; competitor code uses competitors-analysis.

Install / Use

npx skills add daymade/claude-code-skills --skill deep-research

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Our assessment of deep-research

deep-research scores 93/100 on our quality scale, 247th of 947 AI & Machine Learning skills we index (top 27%).

Its SKILL.md is 32 KB long, well organised into 49 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so deep-research is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

deep-research compared with similar skills

All 4 of these similar skills score higher than deep-research; compare them before choosing.

SkillScoreStarsUpdatedFormat
deep-research (this skill)by daymade931.4k53d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install deep-research?
Run npx skills add daymade/claude-code-skills --skill deep-research. The install tabs above show the steps for each supported agent.
Which AI agents does deep-research work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is deep-research safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is deep-research still maintained?
The repository was last updated about 2 months ago, so deep-research is actively maintained.

name: deep-research description: >- Creates reusable, source-traced research reports and coordinates provider/mode lanes with original exports. Use for 深度研究, 调研报告, literature reviews, market or company research, and ChatGPT/Kimi/UniFuncs research routes. Technology choice uses tech-selection; competitor code uses competitors-analysis.

Deep Research

Create high-fidelity research reports with strict format control, evidence mapping, source governance, and multi-pass synthesis.

Architecture: Lead Agent + Subagents

Lead Agent (coordinator — minimizes raw search context)
  |
  P0: Environment + source policy setup
  |
  P1: Question and claim map (decision questions, evidence routes, stop rules)
  |
  Dispatch ──→ Subagent A ──→ writes task-a.md ──┐
           ──→ Subagent B ──→ writes task-b.md ──┤ (parallel)
           ──→ Subagent C ──→ writes task-c.md ──┘
  |                                               |
  |     research-notes/  <────────────────────────┘
  |
  P2: Build evidence packets + citation registry
  P3: Evidence-mapped outline with counter-evidence and unknowns
  P4: Draft from evidence packets; reopen decisive originals
  P5: Counter-review (claims, confidence, alternatives)
  P6: Verify every load-bearing claim and exact fact
  P7: Polish → final report with confidence markers

Context discipline: Keep raw search-result noise in task workspaces. Pass evidence packets to the lead agent, including locators and short source excerpts. Notes are routing aids, not authorities: the lead agent must open the original source for every load-bearing claim, conflicting claim, and exact figure/date/quotation used in the report.

Run and asset contract — every invocation

Before external retrieval, read research-asset-contract.md. Create or resume a durable project study for single-route and multi-route research alike. Search its explicit prior-study catalog, open relevant earlier originals and record reuse/adapt/reject decisions. Draft the decision questions and provider × actual-mode lanes in study.json. Write one exact dispatch_context with the user-supplied seed URL, named entities, and verified codes or other identifiers needed for the query. Include that string in every lane prompt; research_assets.py start rejects an omission. Capture the user's named seed article or document as an original before external dispatch, and follow the provider handoff when a provider cannot read its URL. A model workspace may not see the user's link or local files just because the coordinator does. Then run provider_runs.py plan. Keep every user-requested mode in the plan; a route that adds no value, is unavailable or lacks paid authorization gets a reasoned deferred event. A report assembled from direct web search and internal subagents still needs a direct-source lane and the same archive.

During research, retain the unedited provider outputs, every opened original and every provider-surfaced source URL with status and provenance. Bind report claims to approved original sources; model reports only locate candidate evidence. Before calling a report complete, run provider_runs.py validate, research_assets.py check, and register the study for later discovery. An answer with citations but no study/source/claim record does not satisfy this Skill. The local scripts record and check files; they make no provider calls and do not authorize paid work.

Before sending a Work/Agent task that may choose its own data plugins, inspect the relevant plugin catalog for per-call credits or charges. A signed-in account and a request to use a data source do not set an unlimited spend ceiling. If an autonomous task can invoke metered plugins without a per-call pause and this task has no explicit spend authorization for them, defer that lane or use a route where the exact calls can be approved first. Even with a budget, a prompt is not a technical charge limit: use a controllable route when the autonomous task cannot enforce it. State authorized limits in the provider prompt for traceability, then read the raw tool log after execution; if a charge occurs despite the boundary, record the observed usage and tell the user. Do not make another paid call to fill a coverage gap.

Mode Selection

Determine the research mode before starting:

| Dimension | Options | |-----------|---------| | Topic Mode | Enterprise Research (company/corporation) OR General Research (industry/policy/tech) | | Depth Mode | Standard (multiple decision questions or contested evidence) OR Lightweight (one bounded question with a small evidence surface) | | Provider Mode | An explicit single-route or provider × mode plan. Preserve every user-requested or project-accepted mode as selected or reasonedly deferred; choose additional independent routes when they can materially test the decision |

  • Enterprise Research Mode: Question-led company research with optional analysis frameworks selected only when they help answer the decision
  • General Research Mode: Standard P0-P7 research pipeline with source governance
  • Depth Selection: Choose from the number and consequence of unresolved questions, not prompt length, task count, or a target word count
  • Provider Selection: Read the user's established workflow when they say “our way” or invoke a named research routine. Extra model reports are useful when they add a distinct evidence route, structured tool access, or a meaningful challenge. Check each provider's availability, privacy boundary and paid authorization; do not silently reduce a requested mode set to a direct-source report. Never run every available route by default or hardcode a vendor roster.

Source Governance (V6)

Source Accessibility Classification

Classify every source by accessibility:

| Accessibility | Definition | Examples | Usage Rule | |--------------|------------|----------|------------| | public | Available to any external researcher without authentication | Public websites, news articles, WHOIS (without privacy), academic papers | ✅ Always allowed | | semi-public | Requires registration or limited access | LinkedIn profiles, Crunchbase basic, industry reports (free tier) | ✅ Allowed with disclosure | | exclusive-user-provided | User's paid subscriptions, private APIs, proprietary databases | Crunchbase Pro, PitchBook, private data feeds, internal databases | ✅ ALLOWED for third-party research | | authorized-first-party | User-authorized records about the user's own organization, transactions, or work | Contracts, invoices, CRM records, meeting transcripts | ✅ May establish internal business facts; label provenance |

First-party boundary: User-authorized records may establish what the organization did, agreed, paid, delivered, or observed. They do not count as independent external validation of market standing, customer sentiment, regulatory compliance, or third-party claims. Never relabel an internal record as an external finding.

✅ EXCLUSIVE INFORMATION ADVANTAGE: You SHOULD:

  • Use user's Crunchbase Pro to research competitors
  • Use user's proprietary databases for market research
  • Use user's private APIs for investment analysis
  • Leverage any exclusive source user provides for third-party research

Source Type Labels

Every source MUST also be tagged with:

| Label | Definition | Examples | |-------|------------|----------| | official | Primary source, official documentation | Company SEC filings, government reports, official blog | | academic | Peer-reviewed research | Journal articles, conference papers, dissertations | | secondary-industry | Professional analysis | Industry reports, analyst coverage, trade publications | | journalism | News reporting | Reputable media outlets, investigative journalism | | community | User-generated content | Forums, reviews, social media, Q&A sites | | other | Uncategorized or mixed | Aggregators, unverified sources |

Coverage diagnostics: Track source counts, domains, source-type mix, and concentration to reveal thin coverage. Never pass or fail research from these totals alone. Gate on whether each decision question and load-bearing claim has fit-for-purpose evidence, whether counter-evidence was sought, and whether remaining unknowns are explicit.

AS_OF Date Policy

Set AS_OF date explicitly at P0. For all time-sensitive claims:

  • Include source publication date with every citation
  • Downgrade confidence if source is older than relevant horizon
  • Define a freshness horizon per claim class and flag material outside it; a universal age cutoff is only a diagnostic

P0: Environment & Policy Setup

Check capabilities before starting:

| Check | Requirement | Impact if Missing | |-------|-------------|-------------------| | Required evidence channel available | Required | Narrow scope or stop with the affected questions marked unknown | | Original-source retrieval available | Required for load-bearing claims | Do not promote summaries/snippets to final evidence | | Subagent dispatch | Preferred | Degrade to sequential | | Filesystem writable | Required for completion | In-memory notes may support partial investigation; report the archival gap and leave the study incomplete |

Set policy variables:

  • AS_OF: Today's date (YYYY-MM-DD) - mandatory for timed topics
  • MODE: Standard (default) or Lightweight, justified by the question map
  • SOURCE_TYPE_POLICY: Enforce official/academic/secondary/journalism/community/other labels
  • COUNTER_REVIEW_PLAN: What evidence would overturn each provisional conclusion

Before setting provider mode, run the research asset catalog search. An earlier model summary is a lead; reopen its source and check freshness before reuse.

Report: [P0 complete] Subagent: {yes/no}. Mode: {standard/lightweight}. AS_OF: {YYYY-MM-DD}.

When researching a specific company, use the specialized workflow to route evidence by question. Treat the six dimensions as a coverage map, not a mandatory report outline.

Enterprise Workflow Overview

Enterprise Research Progress:
- [ ] E1: Intake — confirm company entity, research depth, format contract
- [ ] E2: Question-led evidence collection across relevant dimensions
  - [ ] D1: Company fundamentals (entity, founding, funding, ownership)
  - [ ] D2: Business & products (segments, products, revenue structure)
  - [ ] D3: Competitive position (industry rank, competitors, barriers)
  - [ ] D4: Financial & operations (3-year financials, efficiency metrics)
  - [ ] D5: Recent developments (6-month events, strategic signals)
  - [ ] D6: Internal/proprietary sources (or note limitation)
- [ ] E3: Optional analysis framework selected for the decision (or none)
- [ ] E4: Claim/evidence/unknown checks at each stage transition
- [ ] E5: Draft in the user's requested structure
- [ ] E6: Multi-pass drafting + UNION merge (same as general Step 6-7)
- [ ] E7: Present draft for human review and iterate

P1: Research Task Board

For every study, use the portable provider-run contract: one question map, exact prompts, and a distinct lane_id per provider × actual mode, including a direct original-source route when used. Run provider_runs.py plan before dispatch. When two or more provider/mode lanes are selected, load parallel-provider-ops.md before fan-out and coordinate the available provider, browser/app, retrieval and verification Skills with independent agents. Assign one owner per control surface and serialize that owner's UI actions. Do not implement provider calls inside this Skill or assume a fixed vendor roster. Submit long asynchronous jobs early and collect each original result unde

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryAI
Updated1mo ago
Forks219

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
deep-research — Universal Skill: Install & Safety Check | SkillAgent