open-tag-adminlisted

Admin/control console for an Open Tag Slack tag-in workflow backed by MFS. Use to set up a new Open Tag bot from scratch, check what is currently running (backend, permitted MFS scopes, Slack channel), change settings, add or remove data sources, switch the CLI agent backend (claude -p / codex exec), invite or move the bot in Slack, run preflight checks, and troubleshoot thread context, retrieval, or task execution.
zilliztech/mfs · ★ 65 · AI & Automation · score 85

Install: claude install-skill zilliztech/mfs

# Open Tag (admin) This skill is the **control console** for an Open Tag deployment. Use it for the first-time setup and for ongoing operation alike: inspect the live bot, change the backend or permitted scopes, add a new data source, move the bot to another Slack channel, or debug a run. Keep the architecture generic: - **Brain**: the selected CLI agent backend — `claude -p` (Claude Code) or `codex exec` (Codex). - **Memory**: MFS-indexed, operator-authorized context such as Slack history, repositories, docs, issues, databases, or object stores. - **Tools**: MFS connectors for external read/search plus any explicit tools the backend is allowed to use in the workspace. The user-facing flow is: 1. Configure MFS sources and allowed scopes. 2. Configure a Slack app with Socket Mode and invite it to a sandbox channel. 3. Start the Open Tag bridge. 4. Move to Slack and tag the bot in a thread. 5. Let the bridge invoke the selected backend with thread context and scoped MFS helper scripts for permitted external context. This skill does not call a model API directly. Model access, tool access, and write permissions come from the selected CLI agent backend. ## Prerequisites Open Tag is a thin layer on top of a **running MFS server with at least one indexed source**. Confirm these before any Slack work: 1. **MFS server installed and running.** `uv tool install mfs-server`, then `mfs-server run` (binds `127.0.0.1:13619`). Check with `curl -s 127.0.0.1:13619/heal