intelligence/hermes-search

Retrieves ranked, deduplicated results with provenance across vaults, GitHub MCP repositories, and the web.

6|2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill intelligence-hermes-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intelligence/hermes-search
Source: https://github.com/frankxai/Starlight-Intelligence-System/tree/main/skills/intelligence/hermes-search
Command: npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill intelligence-hermes-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Search addresses the challenge of locating and validating information scattered across vaults, repositories, and the web by returning provenance-rich results and surfacing potential inconsistencies.

Core Features & Use Cases

  • Cross-source retrieval with full provenance across vaults, repos, and the web.
  • Deduplication and ranking by relevance, recency, and credibility.
  • Contradiction detection with explicit signaling and source-cited results.
  • Read-only operation that never writes to vaults or external systems.
  • MCP-integrated cross-repo search and multi-agent collaboration.

Quick Start

Provide a ranked set of provenance-backed results for a user query across vaults, repos, and the web.

Frequently Asked Questions about intelligence/hermes-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search across multiple vaults and repositories with source provenance?

Cross-vault and cross-repo search with provenance is performed by routing queries to vaults, GitHub MCP, and web sources in parallel, then returning ranked results with explicit source citations for every item retrieved.

What's the best way to detect contradictions when retrieving information from multiple sources?

Contradiction detection during multi-source retrieval identifies conflicting information across vaults, repos, and the web, explicitly surfacing contradictions with source citations without resolving them, ensuring users see conflicting data points.

Can I search across GitHub repositories and vaults without modifying any data?

Cross-repo and cross-vault search operates in read-only mode, never writing to vaults or external systems, so users can safely retrieve and deduplicate ranked results with full provenance across all connected sources.

How does deduplication work when the same information appears in different vaults and web sources?

Deduplication during cross-source retrieval removes duplicate results by comparing items fetched from vaults, repos, and the web, then ranks the remaining unique results by relevance, recency, and credibility with provenance intact.

Does cross-vault search work with GitHub MCP for multi-agent collaboration?

Cross-vault search integrates with GitHub MCP for cross-repo retrieval and supports multi-agent collaboration, routing queries to correct sources and executing parallel searches across vaults, repositories, and optional web research.

When should I not use a read-only cross-source search tool?

Read-only cross-source search is not suitable when you need to write, update, or resolve contradictions in your vaults or repositories, as it strictly retrieves, deduplicates, and surfaces conflicting information without modifying source data.