Business x ray
Builder employee · Operational Business X-Ray: map, diagnose, and optimize how the business runs through progressive visual analysis. Creates Business Maps, Bow-Tie Funnels, Process Swimlanes, a System Connection Map, and a future-state Operating System Map of connected AI Employees and tools. ALWAYS USE for 'business x-ray', 'x-ray my business', 'map my business', 'diagnose my business', 'audit my business', 'find the bottlenecks', 'where am I the bottleneck', 'map my operations', 'where does my business break without me', 'score my business assets', 'leverage score', or a visual operational diagnosis. Folder/file scaffolding routes to business-os; an explicitly requested free intro AI-readiness map routes to ai-employee-map; post-diagnosis build guidance routes to roadmap.From its SKILL.md
npx -y skills add the2hourclo/aieb-thin-plugin --skill business-x-rayAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.5 KB, as published. Nobody here has run it
business-x-ray — MCP loader
This file is only a loader. The full instructions for this skill — its SKILL.md and every workflow, reference, template, and example — live on the AI Employee Builder MCP server and are fetched at runtime through the get_skill tool on the aieb MCP server, after your license is checked. Nothing of value is stored in this file.
Follow these rules exactly.
1. Load the real instructions first
Call the aieb MCP get_skill tool with:
skill_id:business-x-raypath:SKILL.md
Then follow exactly what it returns. That returned SKILL.md is the real router — it names every workflow, reference, and example path you will need.
Before concluding the connector is missing, search properly. The tool's full name varies by surface (Claude Code: mcp__aieb__get_skill; Cowork/Desktop: mcp__plugin_ai-employee-builder_aieb__get_skill; Codex may expose another prefix) — match ANY tool ending in get_skill, never an exact name. On hosts with lazy MCP loading, run a tool search for "get_skill" before deciding it's absent.
If a get_skill tool truly does NOT exist on any server after searching, the connector is missing on this machine. Stop and tell the user the fix for THEIR surface, then wait:
Claude Code: The AI Employee Builder connector isn't set up yet — run /setup-aieb, open the secure link it gives you, then /reload-plugins. Never paste a license key into chat.
Claude Desktop / Cowork: Make sure the AI Employee Builder plugin is installed (Customize → Personal plugins — if it's missing, add the marketplace
the2hourclo/aieb-thin-pluginand install it), then run /setup-aieb here in chat. It gives you a secure page where you enter the key; the plugin saves only an opaque device token. Never paste the key into chat. Still nothing after that? Say "check my setup" and I'll walk you through it.Codex: Install or update
ai-employee-builder@aieb-thin-plugin, start a fresh Codex thread, then say "set up AIEB". The setup skill opens the same secure activation page and stores only an opaque device token. Never paste a license key into chat.
Do not guess at or reconstruct the skill's content in the meantime.
2. Every file path is an MCP path — never read it from disk
The returned instructions are written as if the files sit on local disk (e.g. "read references/foo.md", "load workflows/bar.md"). They are not local. Whenever the instructions tell you to read, load, open, or see any file path inside this skill, fetch it with get_skill using that exact path instead:
- "read
references/foo.md" →get_skill(skill_id="business-x-ray", path="references/foo.md") - "load
workflows/bar.md" →get_skill(skill_id="business-x-ray", path="workflows/bar.md")
Do not use the Read tool for these paths. A "file not found" on disk is expected — it just means you must fetch the path from the MCP.
3. Scripts
If an instruction says to run a script, fetch its text with get_skill (same skill_id, the script's path), write it to a local working file, then execute it.
4. Locked skill (upgrade message)
If get_skill returns a 🔒 message saying this skill is part of a higher plan, that is a NORMAL answer, not an error: relay the message and the upgrade link to the user warmly, then stop. The existing device connection unlocks it after they upgrade — nothing to reinstall and no key belongs in chat. Do not retry, and never reconstruct the skill's content yourself.
5. No license / errors
If get_skill returns a license or entitlement error, stop. Tell the user plainly that their license must be active, and share the renewal link the server returns. Never invent, guess, or reconstruct the skill's content.
Now do step 1.