search

Searches indexed gnosis-mcp content with keyword, hybrid semantic+keyword, and git history modes.

27|9|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill search-nicholasglazer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search
Source: https://github.com/nicholasglazer/gnosis-mcp/tree/main/skills/search
Command: npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill search-nicholasglazer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly locate relevant information across the gnosis-mcp knowledge base by returning ranked, highlighted results instead of raw files.

Core Features & Use Cases

  • Keyword (default) search for fast results across docs.
  • Hybrid semantic+keyword search to handle paraphrase queries.
  • Git history search to explore changes behind code evolution.
  • Use Case: When debugging a feature, search for related API docs and commit notes to understand implementation details.

Quick Start

Ask me to run a search for a query using the default keyword mode, or specify --semantic or --git to switch modes.

Frequently Asked Questions about search

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

FAQPage Schema
How do I search local development docs and API references?

Search local development docs by querying the gnosis-mcp index to retrieve ranked and highlighted results. It supports keyword, hybrid semantic, and git history modes to find API references and commit notes.

Can I find commit history and code evolution details using git search?

Yes, git history search explores changes behind code evolution. Query the gnosis-mcp index with --git mode to retrieve commit notes and implementation details grounded with file paths and content previews.

What is hybrid semantic search and when do I need it for documentation?

Hybrid semantic search combines semantic and keyword matching to handle paraphrase queries. Use it when debugging features and default keyword search fails to locate related API docs or dev documentation.

Does local docs search work without external dependencies?

Yes, local docs search queries the internal gnosis-mcp knowledge base directly. It operates without external dependencies, ranking results by score and truncating content to configurable previews.

What is the best way to search API references when debugging a feature?

The best way is using hybrid semantic search to handle paraphrased queries across the gnosis-mcp index. It returns ranked results with file paths, titles, categories, and truncated content for in-context grounding.