peek — whole-system codebase comprehension

peek keeps a deep, hierarchical map of a repository (file → folder → whole system) and runs a multi-agent research engine over it. For questions that span many files or whole subsystems, asking peek is faster and more accurate than rebuilding that structure yourself with grep and read — peek has already onboarded to the codebase, so it reasons from comprehension instead of from zero.

This skill works in any MCP-capable agent (Claude Code, Cursor, Codex, Copilot, Windsurf, Gemini, …). Use it to route the right questions to peek, then act on its answer with your own tools.

When to use peek

Delegate to peek when the question is about how the system fits together: