wiki-query

Retrieves and synthesizes documentation, architecture decisions, and runbooks from a Markdown wiki repository.

3|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/zoraxl/team-brain --skill wiki-query-zoraxl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-query
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/wiki-query
Command: npx skills add https://github.com/zoraxl/team-brain --skill wiki-query-zoraxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of team knowledge by providing a unified, context-aware interface to query documentation, architecture decisions, and operational runbooks across the entire repository.

Core Features & Use Cases

  • Contextual Retrieval: Automatically routes queries to the correct namespace zone, platform substrate, or general workflow documentation.
  • Lifecycle Awareness: Distinguishes between stable, source-backed knowledge and speculative or unresolved items found in the inbox.
  • Use Case: When a developer needs to understand the architectural rationale behind a specific service or check if a proposed change conflicts with existing ADRs, this skill synthesizes the relevant wiki pages and decision logs into a concise answer.

Quick Start

Use the wiki-query skill to explain the current architectural decisions and open questions regarding the platform namespace.

Frequently Asked Questions about wiki-query

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

FAQPage Schema
How do I query architectural decisions and technical documentation across fragmented wiki repositories?

Querying architectural decisions and technical documentation is done by routing searches across defined namespace zones to synthesize Markdown-based knowledge bases and decision logs into concise, source-backed answers.

Can I retrieve operational runbooks and ADRs directly from a local file system?

Retrieving operational runbooks and ADRs requires integration with local file system search tools to index and parse the structured Markdown-based knowledge repository.

Does wiki-query work with Markdown-based knowledge bases to find engineering workflows?

Yes, wiki-query works with Markdown-based knowledge bases by parsing defined namespace zones to provide accurate answers regarding product concepts and engineering workflows.

How does lifecycle awareness handle unresolved items or speculative documentation in the inbox?

Lifecycle awareness distinguishes between stable, source-backed knowledge and speculative or unresolved items found in the inbox, ensuring you retrieve authoritative and finalized architectural decisions.

What's the best way to check if a proposed architectural change conflicts with existing ADRs?

The best way to check for architectural conflicts is to synthesize relevant wiki pages and decision logs, which compares your proposed change against existing stable knowledge across the platform namespace.

Why does wiki-query require namespace zones for knowledge management searches?

Namespace zones are required for knowledge management searches to automatically route queries to the correct platform substrate or general workflow documentation, preventing irrelevant results from overlapping contexts.