basic-queries

Identify and contextualize codebase symbols via MCP queries for structural analysis.

1|Updated May 29, 2026

Search Tags:#navigation #find #code-analysis #symbols #descendants #symbol-info #ancestors

Ready to run

npx skills add https://github.com/aimasteracc/mycelium --skill basic-queries

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: basic-queries
Source: https://github.com/aimasteracc/mycelium/tree/main/skills/basic-queries
Command: npx skills add https://github.com/aimasteracc/mycelium --skill basic-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and understand code structure by querying symbols, kinds, and containment to empower AI-driven analysis of large codebases.

Core Features & Use Cases

Symbol discovery: locate symbols by name, kind, or path across modules and files.
Context retrieval: fetch symbol metadata, file location, and parent-child relationships.
Graph navigation: traverse ancestors, descendants, and siblings to reveal structure.
Quick-start scenarios: bootstrap explorations in new projects and establish a symbol-first workflow.

Quick Start

Run a quick lookup for a symbol like login to retrieve its kind and location.

Frequently Asked Questions about basic-queries

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

FAQPage Schema

How do I find symbols and navigate code structure across multiple files?▼

To find symbols across multiple files, you can query by name, kind, or path. This approach retrieves symbol metadata and file locations, enabling you to navigate ancestor and descendant relationships for structural context.

Can I retrieve parent-child relationships for symbols in a multi-language project?▼

Yes, you can retrieve parent-child relationships for symbols in a multi-language project. The queries traverse ancestors, descendants, and siblings to reveal containment structure across files and modules.

What is the best way to bootstrap code exploration in a new project?▼

The best way to bootstrap code exploration in a new project is to perform a symbol-first lookup. Querying a symbol like login retrieves its kind and location, establishing a baseline for deeper structural analysis.

Does symbol navigation require specific capabilities to traverse modules?▼

Symbol navigation requires stable MCP capabilities such as search_symbol, get_ancestors, and get_descendants. These tools use consistent path notation like src/lib.rs>login to traverse modules accurately.

How do I get symbol metadata and source spans for code analysis?▼

You get symbol metadata and source spans by using capabilities like get_symbol_info and get_source_span. This retrieves the exact file location and node kind to support detailed code analysis.

What are the limitations of using symbol queries for codebase insight?▼

Symbol queries for codebase insight are limited to structural and containment traversal. They require consistent path notation and stable MCP capabilities, meaning they focus on inventory rather than runtime behavior analysis.