Agent skill

Omh Research Department

by rlaope in rlaope/oh-my-hermes

[omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use…

MITAuto-check passedResearch & Science

Install Omh Research Department

skills CLI
$ npx skills add rlaope/oh-my-hermes --skill omh-research-department -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-research-department --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-research-department .claude/skills/omh-research-department && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omh-research-department
GitHub stars
3.2k
Token cost
~1.8k tokens
SKILL.md length
805 words
Files
1
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use…

  • The user says: research-department
  • SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Research department

What it does

Omh Research Department is an agent skill from rlaope/oh-my-hermes. [omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use research-brief, and for typed candidates before research starts use source-finder. Use when the user says: research-department, research department, research ops department, research operations department, scout analyst briefer, scout analyst brief, daily research department, competitor research department.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Deep research, Email management and Competitor analysis. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

  • The user says: research-department
  • Research department
  • Research ops department
  • Research operations department

Example prompts

  • “/omh-research-department”

What it can do on your machine

Read from SKILL.md and the folder at commit 7cd0d02. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omh Research Department loads about 1.8k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 805 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rlaope/oh-my-hermes at commit 7cd0d02, republished under its MIT licence (© rlaope). 805 words, ~1,847 tokens.

Download SKILL.mdSave it as .claude/skills/omh-research-department/SKILL.md (or your agent's skills folder).
name
omh-research-department
description
[omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use research-brief, and for typed candidates before research starts use source-finder. Use when the user says: research-department, research department, research ops department, research operations department, scout analyst briefer, scout analyst brief, daily research department, competitor research department.

Research Department

This is a Hermes-native research-department workflow skill.

Why This Exists

research-department exists so Hermes users can start complex research-ops patterns without manually designing profiles, cron, knowledge storage, synthesis tooling, and delivery glue, while OMH keeps every runtime claim observed-only.

Do Not Use When

  • The user only needs a one-off current-source lookup; use research.
  • The user only needs a one-off business synthesis; use research-brief.
  • The request is pure scheduling with no source collection or synthesis; use automation-blueprint.
  • The user asks for coding implementation; prepare a selected executor/runtime handoff after the research plan is accepted.

Examples

Good example:

  • Prompt: Set up a Scout, Analyst, and Briefer research flow for daily competitor and market changes.
  • Expected behavior: Prepare research_department_plan/v1 with Scout/Analyst/Briefer lanes, source inbox buckets, briefing status, knowledge-store and synthesis-tool readiness, and observed-only evidence requirements.
  • Why: The request is recurring, source-backed, and operational; a single research brief would miss the ongoing workflow/status boundary.

Bad example:

  • Prompt: research-department prove the synthesis tool queried the knowledge base and posted the Slack brief.
  • Expected behavior: Ask for observed synthesis-tool and gateway delivery evidence or mark those states as not_observed.
  • Why: The workflow pack can prepare the operating pattern, but it cannot prove external tool execution or delivery.

Completion Checklist

  • The research question, source boundaries, recency assumptions, and confidence level are named.
  • Observed sources, inference, synthesis, and unresolved retrieval gaps are separated.
  • Follow-up planning or handoff uses the research summary without calling it execution evidence.

Recovery Notes

  • If sources cannot be accessed, state the retrieval gap and use only observed local context.
  • If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary.

Workflow Lane

  • Current lane: Research and company ops (product-docs, source-finder, web-research, research, model-optimization, inference-serving, model-finetuning, research-brief, +20 more) - research, signals, ops, and briefings.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when Hermes should turn an ongoing or recurring research request into a prepared Scout -> Analyst -> Briefer workflow with source inbox, knowledge-store and synthesis-tool readiness, and briefing status without claiming research execution.

Strong routing signals: `research-department`, `research department`, `research ops department`, `research operations department`, `scout analyst briefer`, `scout analyst brief`, `daily research department`, `competitor research department`, `market research department`, `paper review`, `weekly paper review`, `research paper review`, `paper research`, `notebooklm research`, `obsidian research vault`, `knowledge store`, `knowledge storage`, `synthesis tool`, `knowledge summarizer`, `research inbox`, `source inbox`, `briefing status`, `리서치 부서`, `리서치 조직`, `리서치 운영`, `수집 합성 브리핑`, `지식 저장소`, `요약 도구`, `경쟁사 리서치 부서`
Show full SKILL.md (381 more words)Show less

Catalog Metadata

Category: research Phase: research-department Hermes role: researcher Quality tier: research-ops-gated Reasoning demand: standard

Quality bar:

  • Name topic, source boundaries, cadence, delivery target, knowledge-store destination, and synthesis-tool readiness.
  • Map Scout, Analyst, and Briefer lanes to concrete OMH skills and source inbox buckets.
  • Expose collected, synthesized, briefed, conflict, and verification counts as status, not execution proof.
  • List required evidence before claiming retrieval, synthesis, storage, delivery, or verification.

Handoff policy:

Keep the research operating model in Hermes. Map Scout to research/source-finder, Analyst to research-brief/web-research, and Briefer to report-package or meeting/report workflows. Record retrieval, synthesis-tool output, knowledge-store writes, delivery, and verification only from observed evidence.

Required inputs:

  • topic or watch area
  • source boundaries
  • cadence
  • delivery target
  • knowledge-store preference
  • synthesis-tool preference

Expected outputs:

  • research_department_plan/v1
  • source_inbox/v1
  • briefing_status/v1
  • not-evidence boundary

Artifact expectations:

  • research_department_plan/v1 under .omh/research-department/plans when a wrapper or CLI records it

Safety rules:

  • Do not claim web retrieval, synthesis-tool query, knowledge-store write, cron creation, gateway delivery, or verification from a prepared plan.
  • Keep raw findings, processed notes, briefs, conflicts, and verification needs in separate source inbox buckets.
  • Treat vendor-specific tool names as optional aliases for synthesis-tool and knowledge-store readiness unless observed evidence exists.

Runtime Evidence

Preferred harness for this skill: research-department.

sh
omh runtime record --skill research-department --harness research-department --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/omh-research-department of rlaope/oh-my-hermes.

Open the folder on GitHubat commit 7cd0d02

Compare with similar skills

Omh Research Department next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omh Research Department compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Research Department this skillrlaope/oh-my-hermes3.2k—~1.8kAutomated safety check: PassMIT
Bmad Deep Recondelorenj/mcp-server-trello445—~2.3kAutomated safety check: PassMIT
Interceptor ResearchHacker-Valley-Media/Interceptor522—~3.8kAutomated safety check: PassCustom licence
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Horizontal-Vertical Deep ResearchKKKKhazix/khazix-skills21k—~2.1kAutomated safety check: PassMIT
Intelligence Collection MethodologyRightNow-AI/openfang18k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Bmad Deep Recon

    delorenj/mcp-server-trello

    Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill…

    445 GitHub stars~2.3k tokensUpdated 17 days ago
    Research & ScienceAuto-check passed
  • Interceptor Research

    Hacker-Valley-Media/Interceptor

    Deep web-research methodology for the interceptor browser surface — investigate a topic the way researchers, intelligence analysts, investigative journalists, private investigators, and OSINT…

    522 GitHub stars~3.8k tokensUpdated 8 days ago
    Research & ScienceAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Horizontal-Vertical Deep Research

    KKKKhazix/khazix-skills

    Runs a two-axis deep research method on a product, company, concept or person: its full history over time, compared with peers today, delivered as a typeset PDF report.

    21k GitHub stars~2.1k tokensUpdated 9 days ago
    Research & ScienceAuto-check passed
  • Reference knowledge for open-source intelligence collection: the collection cycle, source reliability tiers, search query patterns and entity extraction.

    18k GitHub stars~2.1k tokensUpdated 3 mo ago
    Research & ScienceAuto-check passed
  • Rival Search MCP

    damionrashford/RivalSearchMCP

    Deterministic deep research via RivalSearchMCP. An agent skill from damionrashford/RivalSearchMCP.

    132 GitHub stars~796 tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo
  • Omh Accessibility Audit

    rlaope/oh-my-hermes

    [omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.

    3.3k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Omh Agent Debug

    rlaope/oh-my-hermes

    [omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action.

    3.3k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Omh Agent Evaluation

    rlaope/oh-my-hermes

    [omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.

    3.3k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Omh Agent Instructions

    rlaope/oh-my-hermes

    [omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…

    3.3k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Omh Agent Ops Review

    rlaope/oh-my-hermes

    [omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.

    3.3k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Omh AI Slop Cleaner

    rlaope/oh-my-hermes

    [omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.

    3.3k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Questions about Omh Research Department

What does Omh Research Department do?

[omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use…. Omh Research Department is an agent skill from rlaope/oh-my-hermes. [omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use research-brief, and for typed candidates before research starts use source-finder.

When should I use Omh Research Department?

Omh Research Department fits situations like: the user says: research-department; research department; research ops department; research operations department.

How do I install Omh Research Department in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-research-department -a claude-code`. Or copy the skill folder (skills/omh-research-department in rlaope/oh-my-hermes) into .claude/skills/omh-research-department in your project. Claude Code loads it when a task matches its description.

How do I install Omh Research Department in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-research-department -a codex`. Or copy the skill folder (skills/omh-research-department in rlaope/oh-my-hermes) into .agents/skills/omh-research-department in your project. Codex loads it when a task matches its description.

Can I use Omh Research Department in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-research-department -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-research-department, .gemini/skills/omh-research-department, .github/skills/omh-research-department and .opencode/skills/omh-research-department in your project.

What does Omh Research Department need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Research Department is instructions for the agent only.

Does Omh Research Department access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omh Research Department safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Research Department use?

Omh Research Department is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Research Department use?

About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Omh Research Department?

Skills that share tags, products or a category with Omh Research Department: Bmad Deep Recon (delorenj/mcp-server-trello, 445 stars), Interceptor Research (Hacker-Valley-Media/Interceptor, 522 stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Horizontal-Vertical Deep Research (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Research Department?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.