gnosis

Plugin gnosis in nicholasglazer/gnosis-mcp. Commands read from the repo's manifest — 28 days ago.

Skills (8)

• context

  Load usage-weighted context from Gnosis MCP. Surfaces most-accessed docs for session startup or topic primers.

• eval

  Measure retrieval quality — Hit@5, MRR, Precision@5 on a fixed fixture set, or Hit@5/MRR/nDCG@10 on your own corpus via the real-corpus benchmark. Regression tracking against a saved baseline, plain-English interpretation, and tuning pointers when numbers look off. Use after every ingest or config c

• ingest

  Populate the gnosis-mcp knowledge base — from local files, git history, or a crawled website. Handles the full matrix of flags (--force, --prune, --wipe, --embed, --include-crawled) in one place.

• manage

  CRUD operations on the knowledge base — add, delete, update metadata. For bulk ingest / re-ingest / prune, use /gnosis:ingest instead. Requires GNOSIS_MCP_WRITABLE=true.

• search

  Search the gnosis-mcp knowledge base. Keyword (default), hybrid semantic+keyword (--semantic), or git commit history (--git). Includes sanity checks and a reranker warning.

• setup

  First-time setup wizard for Gnosis MCP. Install, init the database, ingest a docs folder, wire your editor — in that order.

• status

  Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.

• tune

  Find the chunk-size and retrieval config that maximizes quality on YOUR corpus. Sweeps chunk sizes, runs a golden-query set, reports nDCG / MRR / Hit@5. Use after first ingest or whenever your corpus changes shape significantly.

Subagents (8)

• README
• context-loader

  Loads the most-accessed docs for a topic into context before work starts. Use at the beginning of a task to prime architectural knowledge.

• corpus-sync

  Runs bulk corpus operations through the gnosis-mcp CLI — ingest, re-ingest, prune, git-history indexing, web crawl, re-embed. Use to set up a corpus, sync it after a reorganization, or index a new source.

• deployment-check

  Verifies a deployed gnosis-mcp service — /health, POST /v1/embed, bearer auth, Docker/systemd config, and the SessionStart hook. Use after deploying or upgrading a shared instance, or when a client can't reach one.

• doc-explorer

  Read-only doc navigator — searches the corpus, follows the link graph, and corroborates against source. Use to find docs, explain architecture, or gather context before implementing.

• doc-keeper

  Repairs docs already in the corpus — single-file upsert/delete, metadata and staleness fixes, and edits driven by a drift report. Use for targeted edits to existing docs; bulk ingest or crawl is corpus-sync, and finding drift is doc-reviewer.

• doc-reviewer

  Finds where docs no longer match the code, with file:line evidence, and reports it — never edits. Use before a release or after a refactor to catch doc drift.

• retrieval-eval

  Measures retrieval quality and attributes a regression to chunk size, embedder, or reranker. Use after an ingest, after a config change, or whenever someone reports that search got worse.

MCP servers (1)

• gnosis

  runs: gnosis-mcp serve

Hooks (1)

• SessionStart

  gnosis-mcp check 2>/dev/null || echo 'Gnosis MCP: database unreachable — check GNOSIS_MCP_DATABASE_URL' >&2

Similar plugins