Research Intelligence

Overview

This skill turns a Hermes agent into a careful public-source researcher. It is optimized for comparing tools, vendors, repositories, products, papers, market signals, community pain, and public claims.

The operating rule is simple: collect enough evidence for the decision, not enough links to look busy. Facts, weak signals, hypotheses, and interpretation must be kept separate when the answer affects money, risk, implementation, reputation, or public claims.

When to Use

Use for:

• tool, repository, model, vendor, or product comparison;
• public GitHub/project traction checks;
• official docs/changelog/release research;
• community pain and adoption scouting;
• public OSINT-style due diligence on companies, products, or public claims;
• research briefs for implementation, purchase, positioning, or watch/reject decisions;
• recurring watchlist design, but only when the user explicitly asks for monitoring.