Research

This is a Hermes-native research workflow skill.

Why This Exists

research exists to make Hermes a careful research engine: it routes research demands to source-backed evidence gathering - from live web citations to studied reference implementations - verifies contested claims, and distills decision-grounding output so planning starts from evidence instead of guesses.

Do Not Use When

• The user asks for a full plan-to-PR delivery cycle; use ultrawork (its delivery_boundary capability) or a planning workflow after research instead.
• The request is purely local repo inspection with no external, current, citation, or source-comparison need.
• The study target is this repository itself rather than external references; use codebase-onboarding.
• The user needs coding execution, review, CI, or merge evidence rather than research synthesis.
• The requested output is a typed candidate list or acquisition status without factual synthesis; use source-finder.
• The user needs a market, customer, or pricing decision brief with evidence-versus-inference treatment; use research-brief.
• The user asks for recurring monitoring, a source inbox, or Scout/Analyst/Briefer operations; use research-department.
• One cited retrieval round settles the question and no reference implementation needs reading; use web-research.