Brain Search

Semantic search over the INITE Brain knowledge graph via the search_knowledge MCP tool. Use when the user wants to find facts, entities, or evidence about people/companies/objects in their tenant, especially when the question is fuzzy or natural-language. Supports bitemporal "as of" queries.

43 stars 5 forksSecurity Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add inite-ai/inite-brain-service

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add inite-ai/inite-brain-service --skill brain-search
Manual install
git clone --depth 1 https://github.com/inite-ai/inite-brain-service.git /tmp/inite-brain-service
mkdir -p ~/.claude/skills
cp -r /tmp/inite-brain-service/plugins/inite-brain/skills/brain-search ~/.claude/skills/brain-search

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# brain-search

Search the company's bitemporal knowledge graph for entities and their facts. Brain's `search_knowledge` MCP tool runs a hybrid pipeline (vector + BM25 + listwise LLM rerank) over per-tenant data and returns ranked entities each with their matched facts.

## When to use

- "Who complained about X?", "find customers in Berlin", "what do we know about Acme Corp?"
- "What was Alice's tier in April?" — historical / as-of queries
- Anything where the user is asking the brain to **recall information**, not record a new fact

Do **not** use for:
- Recording new facts → use `record_fact` instead
- Walking one entity's full history → use `brain-recall` (it combines profile + timeline + connections)
- You already know WHICH entities the question is about → use **`graph_retrieve`** (resolves the named entities, walks their 1-hop neighbourhood, returns facts across seeds ∪ neighbours — "who runs engineering at Acme" lives on a neighbour, not on Acme itself; it soft-fails to empty so you can fall back to `search_knowledge`)
- Questions that combine evidence across multiple entities or sessions → use **`search_multi_hop`** (it runs a planner-LLM and chains sub-queries; the running entity set is anchored across hops so compute stays bounded)
Read the full skill on GitHub

Details

Skill name
brain-search
Path
plugins/inite-brain/skills/brain-search/SKILL.md
License
AGPL-3.0
Repo updated
18 November 2026

FAQ

What does the Brain Search skill do?

Semantic search over the INITE Brain knowledge graph via the search_knowledge MCP tool. Use when the user wants to find facts, entities, or evidence about people/companies/objects in their tenant, especially when the question is fuzzy or natural-language. Supports bitemporal "as of" queries.

How do I install the Brain Search skill?

Claude Code plugin: /plugin marketplace add inite-ai/inite-brain-service. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Brain Search popular?

It lives in inite-ai/inite-brain-service, which has 43 GitHub stars and 5 forks.

Related skills

Brain Bitemporal

43

inite-ai/inite-brain-service

How to query the INITE Brain knowledge graph across time — the asOf parameter, validFrom/validUntil semantics, reading retracted facts, and the memory_diff "what changed between two cursors" surface. Use when the user's question has a temporal dimension ("on X date", "before Y", "what's new since last conversation").

Productivity & Notes

Brain Conflict

43

inite-ai/inite-brain-service

How to detect and resolve conflicting beliefs in the INITE Brain knowledge graph — the COMPETING fact status, get_competing_facts, detect_contradiction preflight, and the human-in-the-loop adjudication workflow. Use when the timeline shows two facts disagreeing on the same predicate, or when an agent needs to decide what to record without making the disagreement worse.

Productivity & Notes

Brain MCP Setup

43

inite-ai/inite-brain-service

Walk a developer through connecting a fresh MCP client (Claude Desktop, Cursor, Goose v2, Aider, Continue.dev, n8n, or a raw @modelcontextprotocol/sdk client) to the INITE Brain service. Covers obtaining an API key, the per-tenant URL shape, config snippets per client, the scope matrix for the full tool surface (up to 32 built-in tools + 2 resources), and the smoke test. Use when the user says "add brain MCP", "connect brain to Claude", "set up brain for Cursor", or names any MCP-capable client.

AI, LLMs & Agents

Code Security

38

sam-dumont/claude-skills

Automatically triggered when running security scans, auditing code for vulnerabilities, checking dependencies for CVEs, reviewing code for security issues, or hardening Python applications. Applies when discussing: security audit, vulnerability scan, bandit, pip-audit, dependency vulnerabilities, OWASP, injection, path traversal, secrets detection, insecure deserialization, auth bypass, or "is this code secure?". Also triggers on: "run security checks", "find vulnerabilities", "security review", "check for CVEs", "audit dependencies", "security lint", "pen test this code", "harden this applica

Security

Security Review

32

joneqian/claude-skills-suite

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

Security

Fedramp

33

scytale-labs/GRC-Claude-Skills

Use when the user asks about FedRAMP — the US government cloud authorization program, impact levels (Low/Moderate/High/LI-SaaS), NIST SP 800-53 control baselines, the System Security Plan (SSP), 3PAO assessment, JAB vs Agency authorization paths, the FedRAMP Marketplace, the ATO (Authority to Operate), or continuous monitoring obligations. For cloud service providers selling to US federal agencies.

Security14

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.