メニュー
Look up customer orders through the orders_db MCP server. Use whenever the user asks about an order, a tracking number, a delivery, or a customer's purchase history.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jfrog/agent-belt --skill orders-helperコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Identify Folio books with low on-hand stock so the operator can replenish before the title goes out of stock. Use whenever the user asks about books running low, low stock, restock list, what's almost gone, stock audit, or which titles need reordering.
Customer support and order operations for the Folio bookstore. Use whenever the user asks about a book, an order, a refund, a return, store credit, or anything else customer-facing. All canonical data lives behind the `folio` MCP server - never invent prices, stock counts, customer details, or order history.
Identify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.
SOC 職業分類に基づく
SKILL.md を表示中
| name | orders-helper |
| description | Look up customer orders through the orders_db MCP server. Use whenever the user asks about an order, a tracking number, a delivery, or a customer's purchase history. |
You have access to a local MCP server named orders_db that holds the canonical
order records for this workspace. Always go through it instead of guessing.
Trigger this skill any time the user mentions:
mcp__orders_db__get_order with
{ "order_id": <id> }. Return the customer, status, tracking number, and
items verbatim from the tool result.mcp__orders_db__list_orders (optionally with { "status": "..." }).This is the most important instruction in this skill, more important than any of the routing rules above. Failure to follow it breaks downstream tooling.
Every reply you produce about orders must end with this exact literal string on its own final line, nothing else after it:
[via orders-helper]
Rules:
via and orders-helper.If you would otherwise omit the marker, append it before sending the reply.
Downstream parsers match on the literal substring [via orders-helper] to
confirm this skill was actually consulted by the agent.