gbrain-query

Escalates gbrain queries through search, recall, and think layers with citation rules.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill gbrain-query-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gbrain-query
Source: https://github.com/tapway/shogun-os/tree/main/skills/gbrain/query
Command: npx skills add https://github.com/tapway/shogun-os --skill gbrain-query-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often waste expensive LLM synthesis calls on simple lookups or skip the knowledge base entirely, producing uncited or stale answers. This Skill defines a mandatory escalation ladder so every brain query starts with fast keyword search and only escalates to heavier tools when needed. ## Core Features & Use Cases - Three-layer escalation ladder: Start with mcp_gbrain_search, escalate to hybrid semantic mcp_gbrain_query, then mcp_gbrain_recall for entity timelines, and finally mcp_gbrain_think for multi-hop synthesis. - Freshness and citation rules: Flags pages older than 90 days on time-sensitive topics and requires slug-plus-date citations like [[people/foo]] in every answer. - Entity-specific lookups: Provides lookup patterns for people, companies, projects, and concepts stored in the brain. - Use Case: When asked "What's the status of the Acme deal?", the agent runs a keyword search first, finds deals/acme-q3 with a high score, and answers with a cited source instead of burning a costly synthesis call. ## Quick Start Ask the agent a question about any entity or topic stored in the brain and it will follow the search-to-think escalation ladder with cited sources.

Frequently Asked Questions about gbrain-query

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

FAQPage Schema
How do I query a gbrain knowledge base efficiently?

Start with mcp_gbrain_search for fast keyword lookup and only escalate if scores fall below 0.3. Move to mcp_gbrain_query for hybrid semantic search, then mcp_gbrain_recall for entity timelines, reserving mcp_gbrain_think for complex multi-source synthesis.

When should I use gbrain think versus search?

Use mcp_gbrain_think only when a question requires synthesis across multiple sources, conflict resolution, or gap analysis. Simple fact lookups and entity status checks should use search or recall, since think carries heavy LLM synthesis cost.

How do I check if a gbrain page is stale?

Flag any page updated more than 90 days ago when the topic is time-sensitive. Use mcp_gbrain_get_versions with the page slug to check for recent edits before declaring content stale.

When should I not query the brain at all?

Skip brain queries for pure operational tasks like cron jobs, docker commands, or file operations, and when the answer already exists in the current conversation. The brain is for knowledge retrieval, not executing actions.

How do I look up a person or company in gbrain?

Use the entity slug convention: people/<slug> for people, companies/<slug> for companies, and projects/<slug> for projects. Fetch the page, then check its timeline and links for related facts.