メニュー
Manager direct-to-MCP fast path for simple ERP data queries. Bypasses Workers entirely — calls honeybadge-nebula-mcp generate_query + validate_and_execute, then forwards results to user via contract 002.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Dispatch ERP queries to Workers. Handles task creation, MinIO sync, state registration, and Matrix room dispatch.
Use when handling any natural language question about ERP data (suppliers, POs, invoices, payments, items, receipts, etc.)
Use when the user asks about fraud detection, three-way matching anomalies, duplicate invoices, unusual payment patterns, or supplier concentration risk
Use when the user asks for analysis that requires decomposing a complex question into multiple queries (trend analysis, comparisons, aggregation across entities)
SOC 職業分類に基づく
| name | fast-query |
| description | Manager direct-to-MCP fast path for simple ERP data queries. Bypasses Workers entirely — calls honeybadge-nebula-mcp generate_query + validate_and_execute, then forwards results to user via contract 002. |
| assign_when | User asks a simple ERP data lookup (查询/搜索/列出/查找/多少/哪个/统计/报告) without complex multi-entity join indicators (关联/匹配/核对/三单). |
Bypasses the Worker pool entirely. The Manager calls the NebulaGraph MCP server directly via mcporter, gets the result, and forwards it to the user via forward-to-user.sh (contract 002).
Use the router script to determine if this skill applies:
ROUTE=$(bash /opt/honeybadge/config/manager/agent/skills/fast-query/router.sh "$USER_QUESTION")
If ROUTE is fast-query, execute:
bash /opt/honeybadge/config/manager/agent/skills/fast-query/fast-query.sh \
--question "$USER_QUESTION" \
--user-id "$USER_ID" \
--task-id "$TASK_ID" \
--forward-to-user-id "$FORWARD_USER_ID"
After fast-query.sh returns FORWARD_OK, STOP. The result has already been delivered to the user via contract 002. Do NOT call message or replyMessage — that sends a duplicate and corrupts the UI.
These route to graph-worker or analytics-worker via erp-query-dispatch instead.