---
name: business-os
description: Builder employee · Install and maintain the file system AI employees navigate. Builds one canonical BUSINESS-MAP.md world model; department folders with neutral DEPARTMENT.md sources and generated AGENTS.md adapters that both Claude and Codex can use; client records; shared system records for CRM, email, Drive, Notion, and other tools; a normalized client-system relationship ledger with backlinks instead of duplicated tool setup; live-data routing with verified IDs; safe migration, tidy, and routing verification. USE WHEN user says "set up my business OS", "organize my workspace", "map my clients", "connect my CRM", "connect my data sources", "make this work in Claude and Codex", "make this workspace work in both Claude and Codex without duplicating the business map", "AGENTS.md", "CLAUDE.md", "my AI can't find anything", or "where does my live data live". Do NOT use to diagnose business processes or draw opportunity maps; use business-x-ray for that.
user-invocable: false
---

# business-os — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="business-os", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.