research-intelligence
Use when a Hermes agent must perform public-source research, source scouting, evidence grading, competitor/tool comparison, community-signal analysis, or decision-ready brief writing without private data or credentials.
Aleksei Ulianov / Sprut_AI · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlekseiUL/hermes-researcher-agent --skill research-intelligence技能说明
name: research-intelligence description: Use when a Hermes agent must perform public-source research, source scouting, evidence grading, competitor/tool comparison, community-signal analysis, or decision-ready brief writing without private data or credentials. version: 1.4.0 author: Aleksei Ulianov / Sprut_AI license: MIT metadata: hermes: tags: [research, public-source, evidence, osint-public, source-scouting, decision-briefs] related_skills: [youtube-research-pack]
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.
Do not use for:
- private-account scraping;
- bypassing login walls, paywalls, CAPTCHAs, or access controls;
- collecting secrets, credentials, private exports, or personal data;
- legal/medical/financial conclusions without qualified review;
- public posting, registration, payment, joining, following, liking, DMing, or emailing without explicit approval.
Core Research Loop
- Frame the decision. Name the user decision: adopt, buy, compare, reject, watch, implement, contact, investigate, or hand off.
- Choose the mode. Use
references/research-modes.mdto selectquick_fact,deep_research,repo_tool,community_pain,live_visual, ormonitoring_design. - Build the source ladder. Pick source classes before searching.
- Ingest documents when needed. For public PDFs, DOCX, PPTX, spreadsheets, HTML, EPUB, or inspected trusted document bundles, create a Markdown analysis copy with
markitdown-document-ingestionbefore summarizing. - Collect dated facts. Include timestamps for volatile data like stars, downloads, prices, package versions, and community metrics.
- Group source lineages. Copies, syndications, mirrors, and posts repeating one announcement count as one evidence lineage until independent reporting or data is shown.
- Triangulate important claims. Decision-relevant claims need primary or structured evidence plus another independent lineage when safely available.
- Seek a counterexample. Check failure terms, negative cases, limitations, and evidence that could change the decision.
- Classify signal strength. Use fact / claim / weak signal / hypothesis / interpretation.
- Browser-check the shortlist. Use a real browser, DOM extraction, or vision for dynamic/social/visual pages when live state matters.
- Run the evidence gate. Fix gaps or label limitations before final answer.
- Return the next move. A good brief ends with a practical action.
Mode Router
Choose the smallest sufficient research mode before collecting sources. A one-fact check must not grow into a deep report, while a consequential or disputed decision must not be answered from snippets. The full mode contract and stop rules live in references/research-modes.md.
Source Lineage and Counterexamples
Source count is not evidence count. Treat these as one lineage unless they add independently collected facts:
- articles copying the same press release;
- mirrors and syndicated posts;
- social posts linking the same announcement;
- multiple pages citing one benchmark without new measurements.
For every decision-relevant claim:
- identify the primary or structured source;
- identify another independent lineage when safely available;
- look for a concrete counterexample or record where you searched and found none;
- lower confidence when access gaps prevent that check.
Use tools/evidence_lineage_check.py with a research-run/v1 JSON artifact when a deep result must be repeatable or independently reviewed.
python3 tools/evidence_lineage_check.py examples/research-run-source-lineage.json --json
Source Ladder
Use the highest-value source classes first:
- Primary sources: official docs, repositories, changelogs, release notes, pricing pages, standards, papers, product pages, government/regulator pages.
- Structured public data and documents: GitHub API, npm/PyPI metadata, Docker tags, package registries, RSS/Atom, public JSON endpoints, datasets, PDFs, DOCX/PPTX/XLSX, CSVs, and inspected trusted document bundles converted to Markdown when useful.
- Community ground truth: Hacker News, Reddit, GitHub issues/discussions, forums, Stack Exchange, public Discord/Telegram mirrors only when accessible without login.
- Search pivots: exact phrases, domain searches, local-language terms, author names, repo names, company IDs, package names, error strings, quoted claims.
- Browser verification: real page state, dates, author identity, comments, visible metrics, UI, login wall, blocked state, screenshots, current context.
Safe Source-Reach Stack
Default source reach is zero-secret and read-only. Use public layers first and label degraded access instead of reaching for cookies.
Allowed by default:
- Hermes web search/extract for ordinary pages, docs, feeds, and public APIs.
- Browser verification for live page state, visible metrics, comments, UI, visual context, and blocked/login-wall evidence.
- Jina Reader URL mode for readable public pages.
yt-dlpmetadata and pu