zoo-init

Initialize .zoo customization files and verify Bureau MCP access.

5|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/andreyvit/zoo --skill zoo-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoo-init
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-init
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to quickly research a repository and generate real project-specific Zoo customization files under .zoo, then verify access to Bureau MCP to enable smooth automation.

Core Features & Use Cases

  • Research a repository to identify root agents and docs (AGENTS.md, CLAUDE.md, README*, docs/, _ai/).
  • Initialize and populate a minimal .zoo directory with project-specific instruction files without overwriting existing ones.
  • Verify Bureau MCP access and report status to ensure automation can proceed.

Quick Start

Research the target repository to bootstrap a .zoo setup and verify Bureau MCP access.

Frequently Asked Questions about zoo-init

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

FAQPage Schema
How do I initialize Zoo customization files for a new repository?

To initialize Zoo customization, you research the repository to locate root docs like AGENTS.md, CLAUDE.md, or README*, create missing .zoo directories, and populate only new project-specific instruction files.

What's the best way to set up Zoo workflows in an existing project?

Setting up Zoo workflows involves auditing existing repos to identify root agents and docs, generating minimal .zoo customization files without overwriting existing ones, and validating Bureau MCP accessibility.

How do I verify Bureau MCP access before starting automation workflows?

Verifying Bureau MCP access requires validating its accessibility using mcp__bureau__current_task, which reports status to ensure automation can proceed smoothly within your repository setup.

Can I use Zoo initialization without overwriting existing .zoo instruction files?

Yes, Zoo initialization populates only new project-specific instruction files under the .zoo directory, ensuring existing files remain intact while creating missing configuration needed for automation.

Why does Bureau MCP verification fail during repository initialization?

Bureau MCP verification can fail if accessibility is not properly validated using mcp__bureau__current_task; the initialization process reports status to identify whether automation can proceed or requires connection fixes.

Do I need root documentation files like AGENTS.md to initialize Zoo workflows?

Zoo initialization researches your repository to identify root docs like AGENTS.md, CLAUDE.md, README*, docs/, or _ai/ to generate project-specific customization files, but missing docs can be handled during setup.